The HTML TF should consider if there are any other implications for assistive technology. However, since the concept of "focus" is irrelevant when the user cannot interact with the document, the UA would not need to support any of the focus-related DOM APIs. It is expected that most static non-interactive presentation user agents will also opt to lack scripting support.Ī non-interactive but dynamic presentation UA would still execute scripts, allowing forms to be dynamically submitted, and so forth. Typical examples of non-interactive presentation user agents are printers (static UAs) and overhead displays (dynamic UAs). User agents that process HTML and XHTML documents purely to render non-interactive versions of them must comply to the same conformance criteria as Web browsers, except that they are exempt from requirements regarding user interaction. James Craig Section 2.2.1, Conformance Classes: Non-interactive presentation user agents Looks fine however I'd like to highlight - Other Applicable Specifications - which without some form of accessibility semantics built into the additional spec description could be a problem in the future.
31.2 Miscellaneous Comments on Specification (or applying Principle 3, Understandable). 31.1 User understandable rendering of Element Names and Roles. 27.2.1 Drag and drop on systems that have pointing devices. 27.1 Comments from NV Access (Mick Curran). 26.3.2 Moving the caret with the keyboard. 26.1.3 Spelling and grammar in designMode. 25.1.4 Emulating non-keyboard operations. 25.1.3.4.3 User choice between navigating and activating. 25.1.3.4.2 Distinguishing activation from navigation shortcuts. 25.1.3.4.1 Navigation shortcuts without visible links. 25.1.3.3.4 Allowing non-character keys as shortcuts. 25.1.3.3.3 Enabling unmodified keys as shortcuts. 25.1.3.3 Maximizing potential keyboard shortcuts. 25.1.3.2.2 Retrieving machine-friendly keybindings. 25.1.3.2.1 Retrieving user-friendly keybindings. 25.1.3.1.4 Disabling unmodified keys as shortcuts. 25.1.3.1.3 Negotiation between host and content. 25.1.3.1.2 Negotiation with nested hosts. 25.1.3.1.1 Negotiation between host and embedded object. 25.1.3.1 Negotiating shortcut keybindings. 25.1.2.5 Facilitate navigating related pages. 25.1.2.3 Preventing validation from trapping focus. 25.1.2.2 Navigation to and through non-editable content. 
25.1.2.1 Sequential navigation to all elements that take focus or input.25.1.1.5.2 Three solutions for conflicts.25.1.1.2 Mission, Goals, and Principles.25.1 UAWG Keyboard Use Cases and Recommendations.23.1 Comments from NV Access (Mick Curran).
19.2.2 Command element and images should support different resolutions. 19.2.1 Facilitate grouping of menu items. 3.1.1 First table - Strong native semantics and default implied ARIA semantics. 1.2.8 2.8.2.3 HTMLFormControlsCollection. 1.2.4 Section 2.2.1, Conformance Classes: Authoring tools and markup generators. 1.2.3 Section 2.2.1, Conformance Classes: Conformance Checkers. 1.2.2 Section 2.2.1, Conformance Classes: Visual user agents that support the suggested default rendering. 
1.2.1 Section 2.2.1, Conformance Classes: Non-interactive presentation user agents.
0 kommentar(er)
