Propose CSS selector like *:role('heading') once we have Element.computedRole() in a draft

[michael-n-cooper]

This issue was originally raised in the APA tracker as ISSUE-589. Migrating to CSS A11Y.

[patrickhlauke]

is Element.computedRole() implemented in the wild anywhere/still actively being considered by browsers? and/or what is its relationship to phase 4 of the Accessibility Object Model https://github.com/WICG/aom /cc @cookiecrook

[cookiecrook]

This tracker can probably be closed for the time being since computedRole is more likely to be implemented in either a WebDriver interface or AOM. The role selector ended up being much more challenging (because it causes a style recalc) than originally anticipated. IOW, we could implement a simple "default role for tag" or "first recognized role attr token" selector, but to get the real thing, you'd need to spin up too much backing code in the rendering engines, which could dramatically slow page rendering. There may be a way to address this in the future, but there is no need to keep this open in the meantime.

[bkardell]

@cookiecrook is this effectively just bad pre-existing code paths implied by how it's plugging in currently that it is hard to avoid or is there a legit reason that getting the computed role would need something WRT the rendering engine?

[MichielBijl]

Related posts:

• Reflecting on Roles by Brian
• Cascading Semantic Stylehooks by Michiel