Details
-
Type:
Sub-task
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.8
-
Component/s: Accessibility
-
Labels:None
-
Affected Branches:MOODLE_18_STABLE
-
Fixed Branches:MOODLE_18_STABLE, MOODLE_19_STABLE
Description
When a "frozen" (i.e. disabled) input element is displayed with QuickForm, it is not displayed as usual but with an extra disabled="disabled" attibute, as seems logical. This has two drawbacks that I can think of:
1. Loses uniform appearance with the rest of the GUI, and may even confuse some users.
2. Is probably less accessible to screen readers, who probably handle the disabled checkbox correctly but simply see text in the current case.
I propose changing this behavior for the check box and any other element where it is seen. We could do this by further subclassing from HTML QuickForm (for easy maintenance) or hacking QuickForm itself a bit (if upgrading it is going to be very rare).
Issue Links
| This issue has been marked as being related by: | ||||
| MDL-13983 | in a html quick if a radio button is disabled you get '( )' or '(x)' rather than just disabling the button |
|
|
|
Hi Jon,
You've had a long wait - sorry!
I totally agree, for screen readers the existing text " [x] " would read "left bracket X right bracket", which is meaningless.
The following is read by JAWS as "Checkbox checked unavailable" - which makes more sense.
<input type="checkbox" disabled="disabled" checked="checked" />
The attached patch is a start, BUT as noted in
MDL-11134it is important to associate a <label> with the control, which I haven't worked out for disabled elements in Quick Forms - please DO NOT commit yet.Please can Jamie or someone help?
Many thanks
Nick
MDL-11134it is important to associate a <label> with the control, which I haven't worked out for disabled elements in Quick Forms - please DO NOT commit yet. Please can Jamie or someone help? Many thanks Nick