Moodle

Add information to help screen readers deal with Cloze questions

Details

  • Type: Sub-task Sub-task
  • Status: Reopened Reopened
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 1.7, 2.0.3
  • Fix Version/s: DEV backlog
  • Component/s: Accessibility, Quiz
  • Labels:
  • Affected Branches:
    MOODLE_17_STABLE, MOODLE_20_STABLE

Description

Quiz: 'fill in the gap' questions are difficult for screenreaders when the gap is in the middle of a sentence because in 'forms mode' it may not read beyond the gap. There is no technical solution to this so screenreader users may need guidance and support on how best to deal with this type of question.

Suggestion 1): Insert an icon with alt text before the question to explain things: (enter missing word)

Suggestion 2): Add documentation/help so that question creators know about the issue:

NO: She details a number of [field] procedure calls...
YES: She details a number of X procedure calls [field]

Issue Links

This issue has been marked as being related by:
MDL-14054 CLONE -Cloze format not displaying the correct answers Trivial Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Nick Freear added a comment -

Hi Martin, congratulations on the 1.7 release!

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.

Show
Nick Freear added a comment - Hi Martin, congratulations on the 1.7 release! 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.
Hide
Permalink
Yu Zhang added a comment -

fixed using both label and image before question

Show
Yu Zhang added a comment - fixed using both label and image before question
Hide
Permalink
Nick Freear added a comment -

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>
<legend> <img alt="Enter missing word" /> – Is this phrase useful?!

<label for="resp9_1">
Question with embedded
<input id="resp9_1" type="text" />
form control.
</label>
...
</fieldset>

TODO: needs more testing with a screen reader, example JAWS! (A technical solution MAY be possible.)
Thanks Nick

Show
Nick Freear added a comment - 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> <legend> <img alt="Enter missing word" /> – Is this phrase useful?! <label for="resp9_1"> Question with embedded <input id="resp9_1" type="text" /> form control. </label> ... </fieldset> TODO: needs more testing with a screen reader, example JAWS! (A technical solution MAY be possible.) Thanks Nick
Hide
Permalink
Michael Penney added a comment -

Is there a timeline or expected version that this will be fixed in?

Show
Michael Penney added a comment - Is there a timeline or expected version that this will be fixed in?
Hide
Permalink
Tim Hunt added a comment -

Michael, I think the problem is that we don't know what the right fix for this is. We first need an accessibility expert who understands the Cloze question to tell us what to do, then writing the code is probably quite easy.

Show
Tim Hunt added a comment - Michael, I think the problem is that we don't know what the right fix for this is. We first need an accessibility expert who understands the Cloze question to tell us what to do, then writing the code is probably quite easy.
Hide
Permalink
Pierre Pichet added a comment -

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.

Show
Pierre Pichet added a comment - 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.
Hide
Permalink
Tim Hunt added a comment -

It should not be necessary to have two display modes. We should look for a way to make the existing interface accessible.

Show
Tim Hunt added a comment - It should not be necessary to have two display modes. We should look for a way to make the existing interface accessible.
Hide
Permalink
Pierre Pichet added a comment -

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.
i.e MDL-13419 and MDL-3274.

Show
Pierre Pichet added a comment - 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. i.e MDL-13419 and MDL-3274.
Hide
Permalink
Tim Hunt added a comment -

I don't have time to work on this before 2.1.

Show
Tim Hunt added a comment - I don't have time to work on this before 2.1.

People

Vote (0)
Watch (3)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.