Closed
Bug 1162159
Opened 10 years ago
Closed 8 years ago
[accessibility][gaia-progress] Make sure gaia-progress is accessible to screen reader.
Categories
(Firefox OS Graveyard :: Gaia::Components, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: yzen, Unassigned)
References
Details
(Keywords: access)
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.
Comment 1•10 years ago
|
||
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.
Flags: needinfo?(yzenevich)
| Reporter | ||
Comment 2•10 years ago
|
||
(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)
Comment 3•10 years ago
|
||
I'm referring to the progress bar web component that is already in use by the system browser when loading web pages [1]. 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
Flags: needinfo?(mhenretty)
Comment 4•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•