A11y: show computed label

[argyleink]

[hchiam]

From what I've recently learned, different screen readers announce different things, and computing the accessible name ourselves could get complicated. In the future, the Accessibility Object Model (AOM) would help expose a consistent API, but it looks like the AOM isn't ready yet (still behind a flag for Chrome). That said, there are basic generalities. Or maybe we could find something in how the Accessibility panel in Chrome already shows the computed name for inspiration:

[argyleink]

Nice, different readers do announce different things, so maybe this issue is a "wont fix" because it's better to surface all the labels and information (like the a11y tip does already) so the user of visbug can see the totality of potential label information instead of our attempt at a computed value.

thoughts on keeping things as is and closing this issue? thanks for investigating!

[hchiam]

i think we can leave this open and watch the aom repo for changes: https://github.com/WICG/aom/blob/gh-pages/caniuse.md