Open Bug 1809479 Opened 3 years ago Updated 7 months ago

role="meter" and meter element should be exposed via IA2_ROLE_LEVEL_BAR; not ROLE_SYSTEM_PROGRESSBAR

Categories

(Core :: Disability Access APIs, enhancement)

Firefox 104
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: spectranaut, Unassigned, Mentored)

References

(Blocks 1 open bug)

Details

(Keywords: good-first-bug)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0

Steps to reproduce:

<div role="meter"></div>
Specification: https://www.w3.org/TR/core-aam-1.2/#role-map-meter

Currently, in firefox, meter is mapped to MSAA role: ROLE_SYSTEM_PROGRESSBAR https://searchfox.org/mozilla-central/source/accessible/base/RoleMap.h#1873

This hasn't been update on chrome yet, intentionally: https://bugs.chromium.org/p/chromium/issues/detail?id=944542

Component: Untriaged → Disability Access APIs
Product: Firefox → Core

We haven't changed the mapping yet for the same reason as Chrome.

Blocks: aria
Severity: -- → S4
See Also: → 1895408

Hi Jamie, should we adjust the AAMs to use ROLE_SYSTEM_PROGRESSBAR instead? Or do you think it's worth the effort to ask both NVDA and JAWS to update first, wait a couple of years, and then change our mappings?

I'm not sure if NVDA and JAWS have even been asked yet. It's hard to justify sinking time into this because it doesn't seem like anyone cares in the wild. If JAWS hasn't been asked yet, it'll still be a few years before this can be changed.

If someone has the cycles, I guess it makes sense to at least ask JAWS and NVDA whether they'll support the new role. But without real world use cases where this is actually a problem, that'll probably be a hard sell given other priorities, though it's a fairly easy change to make.

Type: defect → enhancement

Valerie mentioned these are likely good first bugs, so I'm marking them as such. Please feel free to correct if that's not accurate.

Keywords: good-first-bug
Mentor: jteh

If anyone is willing to work on this, please be aware that we are still pondering whether we actually want to change the mapping (see above comments).

You need to log in before you can comment on or make changes to this bug.