- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Dec 2014 00:27:25 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27294 --- Comment #21 from Alice Boxhall <aboxhall@chromium.org> --- (In reply to steve faulkner from comment #14) > (In reply to Philip Jägenstedt from comment #11) > > What should computedRole do that would require spinning up additional > > accessibility code? Isn't it simply the first recognized token in the role > > attribute, or the default role of the element failing that? > > > > Is falling back to the default role of the element important? That detail > > increases the amount of testing required by a lot, as it brings in > > https://html.spec.whatwg.org/#wai-aria and any other vocabulary-specific > > mapping tables. > > wondering whether getComputedrole will return ARIA abstract of elements > accessibility API mapping? If so what is done in cases where there is no > ARIA equivalent (of which there are many). I think it should, yes. In the case where there is no ARIA equivalent, I think it makes sense to return null. > Also currently role mappings are only represented in acc APIs as ARIA role > values , when the ARIA role value is used by the APIs because their is not > an acc API equivalent, most landmark roles, for example. True, but knowing the computed ARIA role in other cases means that we can reason about what native accessibility API role will be chosen, if necessary, as there is a standard mapping. The ARIA role set gives us a consistent cross-platform API. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 19 December 2014 00:27:27 UTC