3.4.3 Implicit Nesting and Headings
<input type=search> and role=search
ARIA and default values for HTML elements
ARIA and HTML5
ARIA best practices doc
ARIA Intro and Primer
aria-controls on role=progressbar
aria-invalid and aria-required on role=option
aria-level author requirments
aria-level authoring requirements
aria-level on region and subroles
aria-owns
aria-owns is complex
aria-setsize
Associating a tabpanel element with its associated tab
code typo http://www.w3.org/TR/wai-aria-practices/
Comment on WAI-ARIA Role
- Neil Soiffer (Thursday, 28 February)
- Richard Schwerdtfeger (Tuesday, 26 February)
- Richard Schwerdtfeger (Tuesday, 26 February)
- Richard Schwerdtfeger (Tuesday, 26 February)
- Richard Schwerdtfeger (Tuesday, 26 February)
- Richard Schwerdtfeger (Tuesday, 26 February)
- Aaron M Leventhal (Monday, 25 February)
- Neil Soiffer (Monday, 25 February)
- Aaron M Leventhal (Monday, 25 February)
- Richard Schwerdtfeger (Sunday, 24 February)
- T.V Raman (Friday, 22 February)
- Neil Soiffer (Thursday, 21 February)
- Jon Gunderson (Thursday, 21 February)
- Michael A Squillace (Thursday, 21 February)
- Neil Soiffer (Thursday, 21 February)
Comments about the Document Conformance section
Conformance requirements for relevant
contentinfo is redundant with HTML5 <footer>
datatype conformance and processing requirements are very vague
Describedby IDREF or IDREFS?
Document conformance: Integrating ARIA into HTML5
Does the aria spec use RFC 2119 terminology?
Encouraging feedback from the community [was Re: HTML 5 integration issues ]
HTML 5 integration issues
HTML <select> vs. role=combobox
Inferrable roles inside grid
Informative must requirement to use roles
Insufficient processing requirements for roles
Managed state not defined
must requirement at odds with general principles
Need to create custom widgets
Non-<table> grids and treegrids
Non-use of native roles in examples
note and navigation are redundant with HTML5 <aside> and <nav>
note and navigation are redundant with HTML5 <aside> and <nav> and other emails,
On whitespace trimming
pressed vs. checked
Processing requirement for parsing numbers
Processing requirements for secondary and seealso missing
proposed ARIA role for math [DRAFT 1]
- Neil Soiffer (Saturday, 15 March)
- Simon Pieters (Thursday, 13 March)
- Neil Soiffer (Thursday, 13 March)
- Simon Pieters (Wednesday, 12 March)
- Neil Soiffer (Tuesday, 11 March)
- Simon Pieters (Thursday, 6 March)
- Aaron M Leventhal (Thursday, 6 March)
- Simon Pieters (Thursday, 6 March)
- Aaron M Leventhal (Wednesday, 5 March)
- Simon Pieters (Wednesday, 5 March)
- Gregory J. Rosmaita (Monday, 3 March)
- Gregory J. Rosmaita (Wednesday, 27 February)
Real sites have a disincentive to use banner as defined
Redundant attributes: irrelevant and aria-hidden
Required Child Elements
role=definition lacks UA processing requirements
role=directory
role=group as child of role=list
role=main seems mostly redundant with HTML5 <article>
row as child of grid
Runnable suggestion of ARIA in HTML5 document conformance integration
Spec is devoid of processing requirements for states and properties
states and properties on role=presentation
Structured HTML Precludes aria-posinset and aria-setsize?
tab and tablist parent-child reqs not reciprocal
Templateid seems dangerous to innovation and competition
Thanks! Re: Runnable suggestion of ARIA in HTML5 document conformance integration
typo in http://www.w3.org/TR/2008/WD-wai-aria-practices-20080204/
Unprefixed attributes in examples
Usefulness of OWL
Valuenow/min/max conformance requirements and defaults
Last message date: Monday, 31 March 2008 19:38:28 UTC