RE: Question #2 on 4.1.1 Parsing - what it covers - ARIA? and How? - and SVG

From: David MacDonald [mailto:david100@sympatico.ca]

Strictly speaking malformed aria would be limited to 1.3.1, or 4.1.2 (or perhaps 1.1.1 on image or input name messups.)
Not what I would want... would love to include in 4.1.1 but it is not specified there. Wai-aria wasn't around yet.



Actually, it was around and under active development from 2004-2008 (where WCAG 2.0 became a Recommendation in late 2008).

WAI-ARIA was the reason for including requirements about roles, states and properties in WCAG 2. The generality of those requirements turns out to be justified now that there are proposals to develop an accessibility API for the Web platform that scripts could invoke directly rather than indirectly via ARIA attributes in the DOM. Thus, it’s good that the requirements don’t refer to ARIA explicitly, since ARIA may not always be the mechanism used.

I think the answer to malformed ARIA has two parts: (1) does it violate WCAG 2 in a given case, and (2) does it violate the ARIA specification?

The larger problem is one of seeing WCAG 2.0 conformance as the definitive test of Web accessibility. There are other specifications in play, however, including ARIA 1.0 (soon to be ARIA 1.1).


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________