ISSUE-35
aria-processing
Need to define processing requirements for aria states and properties when used in html
- State:
- OPEN
- Product:
- HTML 5 spec
- Raised by:
- James Graham
- Opened on:
- 2008-02-18
- Description:
Integration of the aria specification in html requires detailed processing requirements for the states and properties it defines when used in html. It also requires consideration of how aria features interact with html-native features and, where functionality is duplicated, consideration of whether the advantages of having more than one way to achieve the same effect outweighs the cost. aria spec: http://www.w3.org/TR/wai-aria/ Overlap between longdesc and aria-describedby: http://lists.w3.org/Archives/Public/public-html/2008Feb/0273.html
- Related Actions Items:
- No related actions
- Related emails:
- Requesting some issue guidance on ARIA (from shawn@db79.com on 2008-05-22)
- minutes HTML WG weekly 21 Feb (from connolly@w3.org on 2008-03-09)
- Re: ISSUE-35 (aria-processing): Need to define processing requirements for aria states and properties when used in html [HTML 5 spec] (from ian@hixie.ch on 2008-02-21)
- Re: ISSUE-35 (aria-processing): Need to define processing requirements for aria states and properties when used in html [HTML 5 spec] (from jg307@cam.ac.uk on 2008-02-21)
- Re: ISSUE-35 (aria-processing): Need to define processing requirements for aria states and properties when used in html [HTML 5 spec] (from simonp@opera.com on 2008-02-21)
- Re: ISSUE-35 (aria-processing): Need to define processing requirements for aria states and properties when used in html [HTML 5 spec] (from oedipus@hicom.net on 2008-02-21)
- Re: ISSUE-35 (aria-processing): Need to define processing requirements for aria states and properties when used in html [HTML 5 spec] (from mtanalin@yandex.ru on 2008-02-18)
- ISSUE-35 (aria-processing): Need to define processing requirements for aria states and properties when used in html [HTML 5 spec] (from sysbot+tracker@w3.org on 2008-02-18)
Related notes:
2008-02-21 17:18:51: this "issue" represents a fundamental mis-understanding of the point of ARIA markup and the PFWG's attempts to work with the HTML WG -- as stated by Al Gilman in a post to public-html
<q cite="http://lists.w3.org/Archives/Public/public-html/2007Jul/0903.html">
The working group likes the idea of having built in semantics in HTML and in particular would prefer to have common document elements, such as widgets built
in to the markup. This reduces download size and the effort required to make a web page accessible. For these reasons, we would promote the use of such
markup over the ARIA approach. That said, we do believe that HTML 5 will not incorporate document elements for all those included in the ARIA role taxonomy
nor will it include all the states and properties. For these reasons, backward compatability for the ARIA specifications is a must.
</q>
further on in his email, Al Gilman also states:
<q cite="http://lists.w3.org/Archives/Public/public-html/2007Jul/0903.html">
To summarize, our goals for HTML 5 are as follow:
* Support for issues highlighted in Table: 1 of the ARIA Roadmap
* Backward compatability to ARIA, including the role attribute.
* Allow for full interoperability with assistive technologies
* A preference for access to accessibility information via the DOM
* Reduced efforts by authors to support assistive technologies
* Support for the access element or a version of it.
* Maintain equivalent or improved accessibility features of HTML 4.01
</q>
i vote that this is a NON-ISSUE [Gregory Rosmaita]
Display change log.