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

Re: ISSUE-85 anchor-roles partial Change Proposal

From: Steven Faulkner <faulkner.steve@gmail.com>
Date: Wed, 23 Jun 2010 12:00:24 +0100
Message-ID: <AANLkTikwRYVEsSXXzXrlup11ud3PjGLfVwttXH41GP2j@mail.gmail.com>
To: Sam Ruby <rubys@intertwingly.net>
Cc: HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, Janina Sajka <janina@rednote.net>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>
Hi sam,

>This change proposal proposes a number of new values for a/@role, but only
justifies a subset of these.  For example, there is no rationale provided
for <a >role="scrollbar">.  Either the change proposal needs to be updated
with more complete rationale, or scoped back to only permit the new values
for which >rationale has been provided.
 At this time the Accessibility taskforce ARIA mapping subgroup is
finalizing the spec text for a wholesale replacement of what is currently
known as section 3.2.6 Annotations for assistive technology products
(ARIA)<http://dev.w3.org/html5/spec/embedded-content-0.html#annotations-for-assistive-technology-products-aria>
in
the HTML5 spec.

The replacement can be found here:
http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html NOTE
this is still being edited and has NOT been presented to the accessibility
taskforce for further discussion or a consensus decision. It is expected
this will be ready for the taskforce to begin its review thursday 24th june.
The accompanying change proposal will incorporate the changes requested and
supersede the following change proposals:

# Allow the a element to have ARIA role attribute values other than link
http://www.w3.org/html/wg/wiki/ChangeProposals/ARIAonanchor
# Change the title of the WAI-ARIA section of the HTML5 spec and provide
advice about ARIA scope
http://www.w3.org/html/wg/wiki/ChangeProposals/ariasection

The new change proposal will provide a rationale for the changes in
http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html

Note: The new  change proposal will not provide attribute value by atrtibute
value rationales for each cahnge from the current spec text, but a set of
reasons for the overall changes. If rationales are requested at the level of
each individual change to the current spec text, then it should also be
requested that such rationales with the same level of detail be provided for
the current spec text and ANY counter proposal.

regards
Stevef
On 23 June 2010 11:19, Sam Ruby <rubys@intertwingly.net> wrote:

> This change proposal proposes a number of new values for a/@role, but only
> justifies a subset of these.  For example, there is no rationale provided
> for <a role="scrollbar">.  Either the change proposal needs to be updated
> with more complete rationale, or scoped back to only permit the new values
> for which rationale has been provided.
>
> - Sam Ruby
>
>
>
> On Feb 18, 2010, at 8:48 AM, Steven Faulkner wrote:
>
> I see issue 85 is due by 21st feb
>> I have started the proposal, will have it done by the due date.
>> http://www.w3.org/html/wg/wiki/ChangeProposals/ARIAonanchor
>>
>


-- 
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 Wednesday, 23 June 2010 11:01:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:10 GMT