drawSystemFocusRing, drawCustomFocusRing
Minutes: HTML A11Y TF Teleconference, 31 October 2013
HTML-A11Y Task Force Agenda; 31 October at 15:00Z for 60 minutes
Minutes: HTML A11Y TF Teleconference, 24 October 2013
Minutes: HTML A11y Bug triage telecon, 30th October 2013
Agenda: HTML A11y Bug Triage telecon, 30th October 2013
Bug triage - New bugs report
Advice needed on bug processing (cloning bugs to HTML.next)
RE: CfC: to approve the revised HTML A11Y TF work statement and decision procedures
[Bug 10905] clarify how assigning an accesskey to an element affects the elements default role
[Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)
[Bug 10905] clarify how assigning an accesskey to an element affects the elements default role
[Bug 10888] Access Command Requirements for HTML5
[Bug 23616] New: clarify how assigning an accesskey to an element affects the elements default role
[Bug 11140] Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp
[Bug 10888] Access Command Requirements for HTML5
[Bug 11140] Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp
[Bug 23615] New: Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp
[Bug 10994] accessKeyLabel can expose new information about the user and possibly also other origins
[Bug 10994] accessKeyLabel can expose new information about the user and possibly also other origins
[Bug 10888] Access Command Requirements for HTML5
[Bug 23614] New: accessKeyLabel can expose new information about the user and possibly also other origins
[Bug 10888] Access Command Requirements for HTML5
[Bug 10994] accessKeyLabel can expose new information about the user and possibly also other origins
[Bug 10778] use element.accessKeyLabel to generate list of available accesskeys
[Bug 10905] clarify how assigning an accesskey to an element affects the elements default role
[Bug 10777] user agent assignment of modifier keys subset of accesskey processing subset
[Bug 10776] accesskey value token subsets
[Bug 10775] how is user to decide which set of access keys to use?
[Bug 10774] fallback for accesskey insufficiently defined
[Bug 10772] accesskey and an ordered set of unique space-separated tokens
[Bug 11140] Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp
[Bug 10888] Access Command Requirements for HTML5
[Bug 10782] problems with button example for accesskey
[Bug 10780] reference to definition of Action insufficient for definition of accesskey
[Bug 10779] triggering the Action of the command via accesskey
[Bug 23613] New: Access Command Requirements for HTML5
- [Bug 23613] Access Command Requirements for HTML5
- [Bug 23613] Access Command Requirements for HTML5
- [Bug 23613] Access Command Requirements for HTML5
[Bug 10782] problems with button example for accesskey
[Bug 10782] problems with button example for accesskey
[Bug 10782] problems with button example for accesskey
[Bug 10888] Access Command Requirements for HTML5
[Bug 23612] New: problems with button example for accesskey
[Bug 10252] HTML5 hard-binds "Action" to accesskey key-press
[Bug 10905] clarify how assigning an accesskey to an element affects the elements default role
[Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)
[Bug 10888] Access Command Requirements for HTML5
[Bug 23611] New: clarify how assigning an accesskey to an element affects the elements default role
- [Bug 23611] clarify how assigning an accesskey to an element affects the elements default role
- [Bug 23611] clarify how assigning an accesskey to an element affects the elements default role