Moodle

Add a user setting "Optimise interface for screen readers" that the GUI can access

Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.7
  • Fix Version/s: 1.8
  • Component/s: Accessibility
  • Labels:
    None
  • Affected Branches:
    MOODLE_17_STABLE
  • Fixed Branches:
    MOODLE_18_STABLE

Description

The setting could have three values:

No
Yes, detect screen readers (this would check against user agents) DEFAULT
Yes, always (for when detection doesn't work).

Issue Links

This issue blocks:
MDL-7486 Replace '<' and '>' in Jumpto menu with labels such as 'previous section' and 'next section' or similar. Minor Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Yu Zhang added a comment -

Will do this together with the new profile image alt tag field.

Show
Yu Zhang added a comment - Will do this together with the new profile image alt tag field.
Hide
Permalink
Yu Zhang added a comment -

fixed in user/edit.html.

Show
Yu Zhang added a comment - fixed in user/edit.html.
Hide
Permalink
Nick Freear added a comment -

Hi Yu Zhang, I meant to comment before you tackled this one - sorry!

I think there are practical and policy issues with this idea.

Practicality:
"settings ... Yes, detect screen readers" - not generally possible. My HTTP_USER_AGENT string when I run JAWS with IE is "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1)", the same as when I just run IE. The string is the same for the Thunder/ WebIE free software, http://www.screenreader.net/?section=Thunder. The only assistive software I've found which produces a useful UA string is the un-maintained audio-browser, pwWebspeak - "pwWebSpeak 3.0 Non-Visual Browser (32 bit;EN)"

Policy:
There may be data-protection/ confidentiality issues in some countries, though I'm no expert. Also, general user choice, and the institution's policy.

>> Just updated and I get a "Notice: Undefined property: stdClass::$screenreader in ... /user/edit.html on line 287

I would have thought it's better to allow the user/ site to configure AJAX/ Javascript, which you already do - let me know your views!

Cheers

Show
Nick Freear added a comment - Hi Yu Zhang, I meant to comment before you tackled this one - sorry! I think there are practical and policy issues with this idea. Practicality: "settings ... Yes, detect screen readers" - not generally possible. My HTTP_USER_AGENT string when I run JAWS with IE is "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1)", the same as when I just run IE. The string is the same for the Thunder/ WebIE free software, http://www.screenreader.net/?section=Thunder. The only assistive software I've found which produces a useful UA string is the un-maintained audio-browser, pwWebspeak - "pwWebSpeak 3.0 Non-Visual Browser (32 bit;EN)" Policy: There may be data-protection/ confidentiality issues in some countries, though I'm no expert. Also, general user choice, and the institution's policy. >> Just updated and I get a "Notice: Undefined property: stdClass::$screenreader in ... /user/edit.html on line 287 I would have thought it's better to allow the user/ site to configure AJAX/ Javascript, which you already do - let me know your views! Cheers
Hide
Permalink
Yu Zhang added a comment -

Hi Nick,

We realized it's not practical to test for screenreaders reliably, so we reduced this option to 2 simple options: Yes or No.

Whether any users use this option is protected, in the sense that this option is not shown anywhere inside moodle, except when editting user profiles. So the users will have exact control via capability over who have access to this information.

Should have fixed the notice. =)

Cheers,

Yu

Show
Yu Zhang added a comment - Hi Nick, We realized it's not practical to test for screenreaders reliably, so we reduced this option to 2 simple options: Yes or No. Whether any users use this option is protected, in the sense that this option is not shown anywhere inside moodle, except when editting user profiles. So the users will have exact control via capability over who have access to this information. Should have fixed the notice. =) Cheers, Yu

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.5#665-sha1:422aead) | Report a problem
Powered by a free Atlassian JIRA open source license for Moodle. Try JIRA - bug tracking software for your team.