W3C home > Mailing lists > Public > public-html-a11y@w3.org > June 2010

Re: draft of HTML to Platform Accessibility API mapping table

From: Steven Faulkner <faulkner.steve@gmail.com>
Date: Fri, 25 Jun 2010 11:00:33 +0100
Message-ID: <AANLkTinPuMDO-NFwmqZjjsNjwhtRXjmiZefa0Wd4I_sv@mail.gmail.com>
To: David Bolter <david.bolter@gmail.com>
Cc: Cynthia Shelly <cyns@microsoft.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Hi dave,
>To be clear, no one is suggesting the browser will itself automatically add
aria attributes to the DOM right?

the current spec text [
http://dev.w3.org/html5/spec/embedded-content-0.html#annotations-for-assistive-technology-products-aria
] states:

"User agents are required to implement ARIA semantics on all HTML
elements<http://dev.w3.org/html5/spec/infrastructure.html#html-elements>,
as defined in the ARIA specifications. The implicit ARIA semantics defined
below must be recognized by implementations.
[ARIAIMPL]<http://dev.w3.org/html5/spec/references.html#refsARIAIMPL>
"

This has been added without change to the new spec text.

The second sentence though ambiguous, could suggest that the stated implicit
semantics are to be exposed via the DOM.

Can you provide text which clearly states what you think browsers should do?
we can then replace the current text.

Also I know you are v busy but please take the time to review the proposal:
http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html
your review and feedback is valued!

regards
steve

On 25 June 2010 02:21, David Bolter <david.bolter@gmail.com> wrote:

> Hi Cynthia,
>
> Sorry for the delay in proofing this; and I probably don't have the right
> context for this document but I'd like clarification on why ARIA is included
> as a mapping here. As we know, ARIA is quite a different animal than desktop
> accessibility API. I worry that including it among MSAA etc. is going to
> cause confusion to readers. The concept of mapping to ARIA from HTML is
> presumably included for DOM based AT (which don't really exist yet), but DOM
> based AT could do this mapping themselves as they see fit right? I mean if
> the semantics are already there in the HTML element, why map to ARIA? ARIA
> was invented purely to override the HTML semantics for cases where the HTML
> semantics are broken visually (overridden) by DHTML techniques.
>
> To be clear, no one is suggesting the browser will itself automatically add
> aria attributes to the DOM right?
>
> cheers,
> David
>
>
> On 24/06/10 9:58 AM, Cynthia Shelly wrote:
>
>> Here's a draft of the HTML element to Platform Accessibility API mappings.
>>  It would be great if we could discuss that at next week's mapping sub-team
>> meeting.
>>
>>
>>
>
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html
Received on Friday, 25 June 2010 10:01:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:12 GMT