[Bug 12306] "When authors use the canvas element, they must also provide content that, when presented to the user, conveys essentially the same function or purpose as the bitmap canvas." While everyone can probably agree that alternative content is a good idea when f
[Bug 12405] <video> There's a problem with overlaying a sign-language video and using native controls, because the overlaid video overlaps the native controls
[Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc)
[Bug 13416] [editing] Rename or restructure the contenteditable="" section so that the relevance of designMode is also apparent in the table of contents
[Bug 13444] introduction to semantics does not convey their importance to people with disabilities/users of AT, nor the negative impact incorrect or insufficient semantics can have on the user experience
[Bug 13489] 2.2.1 Conformance Classes: Add supporting sentence to paragraph on visual user agents and default rendering to enhance concept that override of default rendering is acceptable for certain user experiences
[Bug 13497] Description for "alternate" should cover cases like the "alternate stylesheet", "alternate icon" and "alternate pingback" fallbacks, not just refer to the current document.
[Bug 13902] Have more details about the format of accessKeyLabel, like by giving examples. We don't want one browser to format it like "Alt+L" and another "alt-l".
[Bug 13960] I am concerned about the way the Article element is used in examples. Doesn't it make sense that Screen Readers will want to use the article element to skip over the HEADER and NAV elements to the main content. Instead of this: <article><heading>...</hea
Accessible Image tag for Visually Impaired Hi, I design tactile graphics for visually impaired individuals. The amount of useful visual information is enormous and the majority of it is not accessible to the visually impaired. In H
ISSUE-2: Should the HTML5 spec define a standard, platform-independent way for content to query the user agent's accessibility settings, and by extension platform settings that are known to the user agent? Are there any equivalents today?