Closed
Bug 1225213
Opened 9 years ago
Closed 6 years ago
[Contacts] Difficult to select a contact with the screen reader
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: julienw, Unassigned)
Details
(Keywords: access)
STR: 1. Enable the screen reader. 2. Open Messages. 3. Open the New Message panel. 4. tap the "+" icon. Notice the focus is on the letters on the right, which can be considered OK. But then when we activate the letter and the view is scrolled, the focus should be moved to the letter header so that we can easily select the contacts that start with this letter. Blocking because this is nearly impossible to use once we have enough contacts.
Comment 1•9 years ago
|
||
Comms triage: Not sure if this part of accessibility is a supported feature in 2.5. Please renominate if you think it is.
blocking-b2g: 2.5? → ---
Comment 3•9 years ago
|
||
I think this issue should be handled in the app itself. When screen reader user activates a character on the right-hand side, we want to call focus on the header (could be done post animation if scroll is done differently). In order for that to work, I think we might also require tabindex=0 attribute on headers, otherwise they might not be focusable by default.
Reporter | ||
Comment 4•9 years ago
|
||
Yura, but is it a blocker for 2.5 in your opinion ?
Comment 5•9 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #4) > Yura, but is it a blocker for 2.5 in your opinion ? I don't think it's a blocker tbh, more of a a11y improvement/polish. I think the right hand side links are hard to discover anyways for the screen reader user and the thing that's missing is the focus jump. Not having that atm does not prevent the user from actually finding the contact, it just makes it less convenient. I would even nominate this as a good first bug?
Comment 7•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•