- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Mon, 18 Feb 2013 21:36:47 +0000
- To: "Edward O'Connor" <eoconnor@apple.com>
- Cc: public-html@w3.org
- Message-ID: <CA+ri+VnoBg+gASf9m3tjspYoPiHDKiiej=qtx8Q=aK3rEpRqqQ@mail.gmail.com>
Hi Ted, >What's a sub role? its a more granular classification of a role. For example in the OSX accessibility API all HTML elements have a role and a subrole property example: the article element: AXRole: "AXGroup", AXSubrole: "AXDocumentArticle" it may well be that it could be defined via ARIA, but that tends to imply a categorization that its only an accessibility feature, when I wanted to explore the uses including, but not limited to accessibility. regards Steve On 18 February 2013 20:30, Edward O'Connor <eoconnor@apple.com> wrote: > Hi Steve, > > You wrote: > > > allow the data attribute [1] to be used to identify element sub roles: > > > > examples: > > > > <h1>heading</h1> > > <p data-p="subheading">subheading</p> > […] > > What's a sub role? > > Are you trying to express WAI-ARIA's super/subclass role relationships? > If so, I think it would be best to raise the need for an aria-subrole="" > attribute with the folks working on WAI-ARIA. > > If that's not what you meant, what do you mean? Wildly guessing based on > the examples in your email, it seems like you're asking for the ability > for an author to imbue elements with author-defined semantics. Authors > can already do this sort of thing with the class="" attribute (e.g. with > Microformats), Microdata, and RDFa. > > > Ted > >
Received on Monday, 18 February 2013 21:37:54 UTC