- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Thu, 21 Jan 2010 12:58:30 -0600
- To: Martin Kliehm <martin.kliehm@namics.com>, Steve Faulkner <sfaulkner@paciellogroup.com>
- Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
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. Best Regards, Laura On Thu, Jan 21, 2010 at 9:38 AM, Martin Kliehm <martin.kliehm@namics.com> wrote: > Hi Laura and TF, > > Laura Carlson wrote: >> >> For your information there is a call for a change proposal to be >> written for the ARIA anchor-roles, which is HTML Issue 85 [1]. Please >> see Maciej's message [2] that is also forwarded below. > > 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? I can > contribute to such a document. > > 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? > > For example, anchors could be tabs containing hyperlinks to fragment > identifiers of tabpanels. List items could be children of tablists, but > themselves they could be ignored (role="presentation") while they contain > anchors that are tabs. Just accept the author's selection. > > Or take flickr: there we have headlines (h1) that can be clicked and edited. > Remember that @role can take multiple values, so it's a heading and a text > input at the same time. > > And if we need a restriction, is the HTML5 spec the right place? After all > ARIA is specified in the ARIA spec. > > Cheers, > Martin > > [3] > http://dev.w3.org/html5/spec/embedded-content-0.html#annotations-for-assistive-technology-products-aria > > > Laura Carlson wrote: >> >> Related References >> >> Change Proposals >> http://www.w3.org/WAI/PF/HTML/wiki/Issues#Change_Proposals >> >> Accessibility Change Proposal Status >> http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status >> >> Best Regards, >> Laura >> >> [1] http://www.w3.org/html/wg/tracker/issues/85 >> [2] http://lists.w3.org/Archives/Public/public-html/2010Jan/1024.html >> >> -- Forwarded message -- >> From: Maciej Stachowiak <mjs@apple.com> >> Date: Wed, Jan 20, 2010 at 9:47 PM >> Subject: ISSUE-85 - anchor-roles - Chairs Solicit Proposals >> To: "public-html@w3.org WG" <public-html@w3.org> >> >> "ARIA roles added to the a element should be conforming in HTML5" >> This issue has been open three months and was crated under the new >> decision policy. Per the decision policy, at this time the chairs >> would like to solicit volunteers to write Change Proposals. >> http://www.w3.org/html/wg/tracker/issues/85 >> http://dev.w3.org/html5/decision-policy/decision-policy.html#escalation >> >> If no Change Proposals are written by February 21, 2010 this issue >> will be closed without prejudice. >> >> Issue status link: >> http://dev.w3.org/html5/status/issue-status.html#ISSUE-085 >> Regards, >> Maciej >> >> -- End forwarded message -- -- Laura L. Carlson
Received on Thursday, 21 January 2010 18:59:03 UTC