|
Reopened - my suggestion of 14/Nov/06 does not work in Internet Explorer, so NOT in screen readers using IE (I did say then it needed testing!). IE needs an explicit "for" association for <label>s, so I propose we TEST something like:
<fieldset> <label for="resp9_1"> TODO: needs more testing with a screen reader, example JAWS! (A technical solution MAY be possible.) Is there a timeline or expected version that this will be fixed in?
The actual Cloze output format does not definitively encounter accessibilty compliance standards in the question display and in the feedback mechanism.
However the in-line actual format is very useful for all language quizzes for example. Could we set an option at the quiz level so that the user can choose between regular display or display for screen readers. Then we could use in Cloze questions for screenreaders the standard display for the short answer, numerical and multichoice. I think that this option should be set at the quiz level so that it does not interfere with the number of attempt mechanism. I prefer a single interface but ... I think it will be difficult to satisfy the accessibilty compliance standards with the in-line display that has been recently modified so that the HTML input element is the smallest possible and put just near the question text so that it can be used to ask for punctuation sign. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sub-task
Reopened
Minor
 |
|
Great to see
MDL-7396- I'll add comments and help where I can.Something I only discovered recently about <label> – <input> can be nested inside, which might help screen readers in this instance, http://www.w3.org/TR/html40/interact/forms.html#h-17.9.1
So in your example, "<label>She details a number of <input /> procedure calls...</label> " may actually be better than, "<label for="field">She details a number of X procedure calls</label> <input id="field" />" - Chetz and I need to test.