Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document

On 18/08/2009 00:52, Leif Halvard Silli wrote:
> But both of you seem to work from the assumption that @role is only and
> solely an accessibility feature.
> If that is the case, then of course Lynx and other text browsers are not
> supposed to be updated to support the @role attribute in any way, and
> would be right to hide the image.
> However, in isn't - or couldn't - that particular IMG element be
> considered having role="button"?
> And, thus, if @role is not only an AT features, then even text browsers
> would be required to support @role. And so Lynx would be required to
> somehow make that link available through some kind of fallback text.

"WAI-ARIA processing by the user agent MUST NOT interfere with the 
normal operation of the built-in features of the host language.

"Scripted changes in the DOM and style rules which change the 
presentation of the content based on selectors sensitive to WAI-ARIA 
markup MUST be considered as part of normal operation. On the other 
hand, the mapping to accessibility APIs MUST be considered, in applying 
this rule, to be above and beyond normal operation. The WAI-ARIA 
processing MAY alter the mapping of the host language features into an 
accessibility API, but the mapping to the API MUST not alter the DOM."

In other words, to conform to the WAI-ARIA draft, Lynx MUST treat:

<img role="button" src="edit.png" alt="Edit">

the same as:

<img src="edit.png" alt="Edit">

except for DOM, CSS, and accessibility API mapping (none of which are 
relevant to Lynx).

Treating "img" as a button would "interfere with the normal operation of 
the built-in features of the host language".

Benjamin Hawkes-Lewis

Received on Tuesday, 18 August 2009 00:07:18 UTC