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

Re: HTML Chairs Solicit Proposals for ISSUE-85 - ARIA anchor-roles

From: Maciej Stachowiak <mjs@apple.com>
Date: Thu, 21 Jan 2010 16:40:04 -0800
Cc: Martin Kliehm <martin.kliehm@namics.com>, Steve Faulkner <sfaulkner@paciellogroup.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-id: <48C6681F-F303-4010-8E94-5BB83FA923BB@apple.com>
To: Laura Carlson <laura.lee.carlson@gmail.com>

On Jan 21, 2010, at 4:36 PM, Laura Carlson wrote:

> On 1/21/10, Maciej Stachowiak <mjs@apple.com> wrote:
>> On Jan 21, 2010, at 10:58 AM, Laura Carlson wrote:
>>> Hi Martin,
>>>> I agree that the current spec draft [3] doesn't make sense and is
>>>> restricting the allowed roles too much. I have some ideas, but I
>>>> remember that Steve has created a matrix of roles in a Google doc,
>>>> didn't he?
>>> Yes, I think it is at:
>>> http://spreadsheets.google.com/ccc?key=0AlVP5_A996c5dG9RSE9GMy1JaVlBQ2dIWDliczJHckE&hl=en
>>> Steve, is this the latest?
>>>> I can contribute to such a document.
>>> That would be great.
>>>> The question to me is: is restriction and overriding with "strong native
>>>> semantics" the right approach?
>>>> Do we need such a table/matrix at all?
>>>> Shouldn't we trust that the author knows what he does?
>>> [snip]
>>>> if we need a restriction, is the HTML5 spec the right place?
>>> All good questions for the task force to contemplate and discuss. I
>>> have a related question that I will send out shortly.
>> The Task Force can certainly consider these broader questions, however, I
>> will note that they are beyond the scope of this particular issue, which is
>> only about roles on the <a> element. It may be easier to deliver a timely
>> Change Proposal by focusing on that specific case instead of the big
>> picture.
> Maciej is right, Martin. ISSUE-35 the big picture Issue for defining
> processing requirements for ARIA states and properties was CLOSED
> January 4, 2010.
> http://www.w3.org/html/wg/tracker/issues/35
> So that leaves us with just one ARIA issue that is OPEN. It is Issue 85.
> http://www.w3.org/html/wg/tracker/issues/85

The Task Force is also free to report other problems with the current spec requirements for ARIA. In fact, I think it would be a useful exercise for the Task Force to go through the current matrix in the spec and file bugs where they disagree.

Received on Friday, 22 January 2010 00:40:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:07 UTC