Although the component has relevant aria attributes, it seems to be completely inaccessible by the screen reader. The progress itself seems to be too small of target as well, and is hard to focus a screen reader on it with explore by touch. Need to make sure that indeterminate progress is supported as well.
Does the current progress bar in the system app have these same accessibility issues? I would like to use the gaia-component here soon since it's a much nicer UX. But I want to make sure I don't regress accessibility in doing so.
(In reply to Michael Henretty [:mhenretty] from comment #1) > Does the current progress bar in the system app have these same > accessibility issues? I would like to use the gaia-component here soon since > it's a much nicer UX. But I want to make sure I don't regress accessibility > in doing so. Hi Michael, could you clarify what you are referring to in particular? Is it something that is used for fxa for example to show progress? or generic progress element?
Flags: needinfo?(yzenevich) → needinfo?(mhenretty)
I'm referring to the progress bar web component that is already in use by the system browser when loading web pages . It is a lot uglier than the gaia-progress component Wilson did, so if we aren't regression accessibility by migrating to it, I want to do so now. 1.) https://github.com/mozilla-b2g/gaia/blob/master/shared/elements/gaia_progress/script.js
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 15 days ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.