Thursday, 28 April 2016
- [Bug 13739] [editing] sections on contenteditable and designmode have insufficient discussion of keyboard accessibility
- [Bug 25858] Consider adding a screen capture example
- [Bug 18450] Consider adding a screen capture example
- [Bug 27913] focusing steps don't contain scrolling an element into view
- [Bug 23611] 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 23616] clarify how assigning an accesskey to an element affects the elements default role
- [Bug 27787] Sequential Navigation Focus Order for Image Maps
Friday, 15 April 2016
- [Bug 10450] Allow lists to be used as menus or tab sets
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)
- [Bug 10919] Allow role="presentation" to override the default role of any element
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13726] defnitions of DL/DT/DD are too vague
Thursday, 14 April 2016
- [Bug 23027] ARIA: select and option should allow role overrides of menu and menuitem
- [Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13738] "Element level Focus APIs" should include addition information regarding accessibility
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13737] the menu element and accessibility
- [Bug 13736] the required attribute and accessibility
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13734] new input element types and accessibility
- Fwd: Agenda: HTML bug triage
Monday, 11 April 2016
- [Bug 23614] accessKeyLabel can expose new information about the user and possibly also other origins
- [Bug 23613] Access Command Requirements for HTML5
- [Bug 10888] Access Command Requirements for HTML5
- [Bug 23612] problems with button example for accesskey
Thursday, 7 April 2016
- [Bug 23470] Incomplete accessibility API exposure rules for svg element
- [Bug 13663] 4.8.2 how does seemless iframe impact a11y api?
- [Bug 13550] type table in 4.10.7 should indicate control type changes based on list attribute
- [Bug 13437] Editorial changes to The Video element (5 of 5)
- [Bug 12591] restrict img from taking @role=presentation whenever img provides link text
- [Bug 12587] AT shouldn't see img@alt="" and img@role=presentation as 100% synonyms
- [Bug 13654] 3.5.1 does unregistering event listeners include AT?
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13733] the area element and alternative text
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13732] canvas accessibility
- [Bug 13731] need simple visual alternatives to indicate that audio is playing to let a deaf user know
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13731] need simple visual alternatives to indicate that audio is playing to let a deaf user know
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13725] enable AT users to have access to contents of the title attribute (tooltip text)
- [Bug 13663] 4.8.2 how does seemless iframe impact a11y api?
- [Bug 13510] discuss setting up accessibilty APIs as part of document parsing
- [Bug 13509] describe what happens in with accessibility APIs when existing document is destroyed
- [Bug 13103] Visual formatting of content inside the pre element isn't available to assistive technologies
- [Bug 12604] Provide accessibility API details for Change Proposal for ISSUE-131
- [Bug 12587] AT shouldn't see img@alt="" and img@role=presentation as 100% synonyms
- [Bug 10249] Canvas requires a content selection method