Maciej,
We can do that but we have to start somewhere. I would like to know if
there is a aversion by HTML to have another set of attributes that start
with a pseudo namespace like aria- to avoid collisions.
I have an action item to work on canvas for the end of the month and we
have started our work here. I will coordinate the names with the CSS
working group and will discuss this on the accessibility task force call
tomorrow.
Rich
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Maciej Stachowiak
<mjs@apple.com>
To
02/03/2010 04:25 Richard
PM Schwerdtfeger/Austin/IBM@IBMUS
cc
Ian Hickson <ian@hixie.ch>,
"public-html@w3.org"
<public-html@w3.org>
Subject
Re: Integration of HTM
On Feb 3, 2010, at 1:53 PM, Richard Schwerdtfeger wrote:
Ian, others,
We are working on canvas accessibility for the shadow DOM and I am
working with the Mozilla team on the shadow DOM approach with some
sample code from Microsoft.
As we discussed, the use of media query of alternative content I am
working to pull over a standard set of attributes from the IMS Access
For All specification. It was suggested that we preface these with an
aria-, however these are not part of the aria specification and
preceding these with an aria- dash would not give credit to the IMS
Access For All effort.
I raised the suggestion that these be preceded with afa- but we
agreed this would require agreement from the working group.
For example, one attribute would be AdaptationType and we would
define an equivalent CSS Media query property for it.
What's the group on using afa- to preamble each attribute name? ...
or should we just include the attributes without the afa-?
As was requested they would not be limited to canvas content
selection and at the moment I see no naming conflicts with existing
HTML 5 attributes.
If the idea is to propose CSS media query properties, then they should be
proposed to the CSS WG. I am not sure why we would need or want any markup
attributes related to specific CSS media query properties, but if we do,
then it's probably best to name and design them after they are defined at
the CSS level because we'd want to align on the name.
Regards,
Maciej