Description: ------------ When a "frozen" (disabled) form element is displayed with QuickForm, it is not displayed as expected with a disabled="disabled" attribute - instead QuickForm tries to give a plain text equivalent. This is a usability and accessibility problem: 1. It loses uniform appearance with the rest of the user interface, and will confuse some users. 2. For non-visual users using screen reader software this text may not be read and in any case will not make sense (More here, http://docs.moodle.org/en/Development:Accessibility_notes#Forms). Applies to, at least: Input, InputCheckbox, InputPassword, InputRadio HTML 4, disabled attribute, http://www.w3.org/TR/html4/interact/forms.html#adef-disabled We use QuickForm in Moodle - for the moment we have fixed it at our level, but really it needs fixing in the QuickForm2 base classes, http://tracker.moodle.org/browse/MDL-8627 (Reported for HTML_QuickForm as Bug # 12063) Expected result: ---------------- Checkbox example: <label for="y">label</label> <input type="checkbox" disabled="disabled" id="y" /> Actual result: -------------- Checkbox example: label [ ], or [x]

We'll probably add a means to customize "frozen" HTML for checkboxes and radios in QF2, however I'd like to clarify a few points first. Freezing elements in QF[2] is primary useful for an additional confirmation step, sending a filled form via email, this sort of thing. Setting an element disabled is more easily achieved by simply doing setAttribute('disabled') So the first question is why Moodle is using freeze() in the first place? Also Moodle seems to still use old QuickForm, we'd like to know what prevents migration to QF2?