- From: Steven Faulkner <faulkner.steve@gmail.com>
- Date: Thu, 8 Jul 2010 11:28:40 +0100
- To: Maciej Stachowiak <mjs@apple.com>
- Cc: Sam Ruby <rubys@intertwingly.net>, 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>
- Message-ID: <AANLkTilqb6QhIA4DmSt8l38IqnLxK11lPGjwQ6rPPcbU@mail.gmail.com>
Hi maciej, I do not plan to pursue this change proposal as it is superseded by the new proposal. regards Steve On 8 July 2010 10:35, Maciej Stachowiak <mjs@apple.com> wrote: > > Hi Steve, > > It's ok to separately pursue the broader set of ARIA changes, but they seem > out of scope for the existing ISSUE-85. I understand that the broader > proposal has now been submitted as a bug report and so will wind its way > through the system. In the meantime, your options are: > > 1) Update the ISSUE-85 change proposal with the required rationale, and > then we can proceed with resolving this specific issue. If you intend to do > that, please do so by July 15th. > > 2) If you do not care to update this Change Proposal, we will consider it > abandoned. At that point, Ian's proposal for issue 85 will be the only one > remaining, so we will issue a call for consensus on it. > > If you definitely do not plan to update your existing Change Proposal > further, it would be much appreciated if you could let us know. > > Regards, > Maciej > > > On Jun 23, 2010, at 4:00 AM, Steven Faulkner wrote: > > 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. > > > > -- 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 Thursday, 8 July 2010 10:29:39 UTC