- From: David Bolter <david.bolter@utoronto.ca>
- Date: Wed, 04 Mar 2009 09:29:10 -0500
- To: "Schnabel, Stefan" <stefan.schnabel@sap.com>
- CC: wai-xtech@w3.org
Hi Stefan, When a user agent is mapping aria roles to platform roles, sometimes there is no good candidate platform role. In these cases we can go with a best-guess match for a platform role, or we can fall back to a role based on native markup. Note in these cases we can still expose events and states to capture the 'live'-ness. Aside: I feel aria is pushing platform accessibility, so we are in the churn right now, and probably for the next few years. cheers, David Schnabel, Stefan wrote: > Allowing and forbidding even only a few selected overrides would be contradicting to ARIA concept. > > Who decides about the overrides? I suspect this will cause 100 times more noise than the "summary" thread .. > > - Stefan > > -----Original Message----- > From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On Behalf Of David Bolter > Sent: Mittwoch, 4. März 2009 03:42 > To: wai-xtech@w3.org > Subject: [aapi] live roles > > Hi, > > There are some 'live' roles like "log" and "marquee". The Mozilla team > is considering these aria roles with respect to platform accessibility > API mapping. One strategy is to not let these particular aria roles > override the native markup mapping. So something like > > <table role="log"> > > would continue to map to whatever role the native/host language element > regularly mapped to (e.g. ROLE_TABLE). > > Thoughts? > > David > >
Received on Wednesday, 4 March 2009 14:29:50 UTC