- From: Al Gilman <Alfred.S.Gilman@IEEE.org>
- Date: Mon, 1 Oct 2007 09:22:22 -0400
- To: "Simon Pieters" <simonp@opera.com>, public-html <public-html@w3.org>, public-xhtml2@w3.org, "wai-xtech@w3.org" <wai-xtech@w3.org>
At 1:47 PM +0200 1 10 2007, Simon Pieters wrote: >On Thu, 27 Sep 2007 18:55:16 +0200, Al Gilman ><Alfred.S.Gilman@ieee.org> wrote: > >>b) this specifically allowed for there to be both an ARIA 'menu' role >>and an XHTML 'navigation' role on the same element. In other words, >>there are use cases for mixing and matching the roles from the two >>vocabularies. Dumping the XHTML role values into the ARIA namespace >>and then limiting to one is not the same functionality. > >I've changed the authoring requirements so that the roles defined in >the XHTML Role Attribute Module aren't allowed to have the wairole: >prefix. > >>Make the specification a little more of a selector-based rule. That >>is to say, define the space of attributes (as now) and the >>'first-found from [limited range of sources, maybe only the ARIA >>roles]' query and then say that values so found are to be processed >>as described here. > >I've changed the algorithm to use the first WAI-ARIA role instead of >just the first role. Good. I think these changes solve the problem I raised. Al > >-- >Simon Pieters >Opera Software
Received on Monday, 1 October 2007 13:22:40 UTC