"may" about form submission contradicts a "must" requirement
'undefined' unclear
[WAI-ARIA] Initial review from an SVG perspective
About menuitemradio and menuitemcheckbox
alerts and focus
Ambiguous "should" in an informative section
ARIA doesn't define number parsing
aria-checked requiredness inconsistent
aria-grabbed and aria-dropeffect relationship to HTML5 Drag&Drop unclear
aria-label & aria-labelledby mutually exclusive?
aria-label vs. HTML title attribute
aria-owns is still complex
aria-required vs. aria-expanded as global states/properties
aria-valuenow index base into list of labels unclear
autoreply
Changing the expected behavior of option
Comment on WAI-ARIA Role
comments on aria-hidden
Comments on WAI-ARIA Role, from a WebApps and SVG Perspective
Conformance classes (Last Call comment on WAI-ARIA)
Contradictory recommended steps and examples
Drop effects seem mutually exclusive
dropeffect a state?
Empty containers not allowed
Feedback on ARIA Spec and Best Practices Guide
Grouping in lists
Implementation of RDF?
Indicate authoring expectations on grid SHOULD violations
Inference from the DOM
Informative 'must' still in ARIA
input type=search vs. role=search
Interaction of role=heading and the HTML5 outline algorithm is undefined
Invitation to review WAI-ARIA before Last Call deadline
Landmarks are redundant with native HTML features
Last Call comments on WAI-ARIA 1.0
Meaning of aria-level on role=rowheader and role=columnheader
Minor notes (Last Call comment on WAI-ARIA)
MMI ARIA comments
Must have at least one child of type vs. can only have children of type
Mutations events and fundamental design of ARIA
Name computation is vague
Normativity of role taxonomy
Parent element for role=option seems wrong
Please avoid calling schemas "implementations"
Please do not define attribute value syntaxes in terms of XSD datatypes
Please remove FPI in sample ARIA DTD
Please specify the meaning of controls, invalid and required on non-widgets
Required children of role=combobox
Role inference in grids still unclear
role="form" missing (closest construct: role="search")
role=article not classified as a landmark
role=math feedback/questions
role=presentation has the aria-expanded state
role=separator allows aria-expanded
Should say that aria-valuemin must be less than or equal to aria-valuemax
SHOULD vs. MUST and abstract roles
Some ARIA Comments
Statement about events very vague
tablist and tabpanel in wrong order
UI Widget and UI element
Use of RFC 2119 Keywords
Use of SHOULD (Last Call comment on WAI-ARIA)
User Agent Accessibility Guidelines Working Group Comments on ARIA Last Call
WAI-ARIA allows meaningless combinations (Last Call comment on WAI-ARIA)
WAI-ARIA comments from EOWG
WAI-ARIA comments from the XHTML WG.
WAI-ARIA Last Call comments
WAI-ARIA still lacks proper processing requirements
WAI-ARIA: 4.3.1. Base Types
WAI-ARIA: 4.4. Definition of Roles
WAI-ARIA: 5.2.4. Value
WAI-ARIA: 6.1.1. Role Attribute
WAI-ARIA: 6.1.2. State and Property Attributes
WAI-ARIA: 6.1.4. Resolving Conflicts with Host Languages
WAI-ARIA: 7.1. Non-interference with the Host Language
WAI-ARIA: 7.2. All WAI-ARIA in DOM
WAI-ARIA: 7.3. Web Application Notification of DOM Changes
WAI-ARIA: abstract roles
WAI-ARIA: General comments
WAI-ARIA: Introduction, Figure 1.0 (editorial)
WAI-ARIA: Name Computation
WAI-ARIA: Parent element
WAI-ARIA: Text Equivalent Computation
WAI-ARIA: wai-aria vs wai-aria-implementation
WCAG WG comments on Accessible Rich Internet Applications (WAI-ARIA) 1.0 - Last Call Working Draft
WCAG WG comments on WAI-ARIA Best Practices
WCAG WG comments on WAI-ARIA Best Practices - WITH ATTACHMENT
WCAG WG comments on WAI-ARIA User Agent Implementation Guide
Why aria-expanded on role=application?
Last message date: Monday, 22 June 2009 08:14:33 UTC