Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 1.8, 1.8.1, 1.8.2, 1.8.3, 1.9
-
Fix Version/s: None
-
Component/s: Accessibility
-
Labels:None
-
Database:Any
-
Affected Branches:MOODLE_18_STABLE, MOODLE_19_STABLE
Description
This option, new in 1.8 was something that we (OU) didn't request or discuss with Moodle.com/org. I've been slow to raise this, but we aren't sure that it is useful, there are specific problems with its use (eg. MDL-7472) and in any case there is no online help explaining the feature to students. Something to discuss.
Thanks Nick
–
Description From Nicholas Freear 2007-07-24 [OU Bug 3650]
"" From: C.Colwell | Sent: 18 July 2007 12:42
To: D.K.Taylor | Cc: A.E.Jelfs
Subject: RE: Profile Opt-in testing info
...
although by having a brief look at it I can see immediately see there are a number of issues:
- there is a 'screenreader' option and the help for it says "In some places the system might use this value to display simpler page layout which works better with screen readers." However, I'm not aware that the (OU)VLE is doing this so this option seems redundant and could set up expectations.
""
— Comment #1 From Nicholas Freear 2007-07-24 16:37:13 —
In ou-moodle (& core?) there are 14 uses of $USER->screenreader flag, including course/lib.php, mod/chat, resource (2), survey, question/type (3), and theme/index.php (3).
TODO: In the medium term we need to analyse whether these are appropriate, and probably implement a solution in core Moodle.
In the short-term (in OU moodle), I've commented out the screenreader form widget in user/editlib.php - committed.
Just updated on Acceptance test server at 16:30.
— Comment #2 From Nicholas Freear 2007-07-24 17:37:13 
[reply] —
Related bug MDL-7497, - file, question/type/multianswer/questiontype.php
- Bug
MDL-7472, Explicitly label radio buttons in Survey
Well, the problem was that we came up with a few places where it was not possible to satisfy both of these with one set of XHTML:
so we made that variable to decide between two alternative interfaces. The idea was to set that variable dynamically as well (based on user agent strings, much like the HTML Editor switch) but I don't think that has been done yet for screenreaders.
It was not meant to be an easy way out - in many cases we made very difficult compromises instead, but sometimes we just had to avoid making the interface really ugly for the majority.
- the interface expectations of the high percentage of users using normal browsers
- accessibility for those using other browsers
so we made that variable to decide between two alternative interfaces. The idea was to set that variable dynamically as well (based on user agent strings, much like the HTML Editor switch) but I don't think that has been done yet for screenreaders. It was not meant to be an easy way out - in many cases we made very difficult compromises instead, but sometimes we just had to avoid making the interface really ugly for the majority.