- From: <bugzilla@jessica.w3.org>
- Date: Sun, 10 Oct 2010 15:50:00 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11004 --- Comment #2 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2010-10-10 15:50:00 UTC --- (In reply to comment #1) These remarks seem fairly off-topic for this bug, which is solely about providing an example rendering. > We also need to ensure a mapping between the actual range value and the > datalist option label. Currently, the list/datalist is seen as more of a > passive visual aid, then an actual concrete mapping. As far as I can tell, the "value" attribute concretely maps the suggestion label to its numeric value. If this is somehow not sufficient, please file a separate bug explaining the problem. > In addition, we would need an ARIA mapping associated with the labeling, in > such a way that actual step values would be available via API with the tick > marks, but the step value AND label being available when a label is specified. The requirement for accessibility mappings in the mappings Note is already logged as Bug 11003. ARIA does not cover all semantics that need to be mapped to accessibility APIs (at the moment, for instance, it doesn't even cover tables). I don't think ARIA has any particularly obvious mapping for range control suggestion labels. Notably the JQuery UI slider doesn't seem to add ARIA annotations to the tick mark labels. If you think there is a good way to map the native semantics to ARIA as it stands, please explain how in dedicated bug. Otherwise, please propose additions to ARIA to PFWG via the public-pfwg-comments mailing list. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 10 October 2010 15:50:02 UTC