Closed
Bug 1030346
Opened 10 years ago
Closed 10 years ago
Improve accessibility for of the contacts app.
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect)
Tracking
(b2g-v2.1 fixed, b2g-v2.2 fixed)
RESOLVED
FIXED
2.1 S4 (12sep)
People
(Reporter: eeejay, Assigned: yzen, Mentored)
References
Details
(Keywords: access, late-l10n, Whiteboard: [b2ga11y p=1])
Attachments
(2 files)
Each one of the fieldsets such as phone/email/address is container in an <li>. We should probably give better accessibility roles to those elements, like groups, maybe event with relevant aria labels.
Reporter | ||
Comment 1•10 years ago
|
||
Re-aligning priorities with 2.1 accessibility goals.
Whiteboard: [b2ga11y p=1]
Assignee | ||
Comment 2•10 years ago
|
||
Hey Jim, this one should be a good one. Basically you need to go through contacts app and see what sections/elements do not sounds semantically correct, for example what Eitan mentioned in Comment 0. If you have any questions mark me with needinfo? Thanks!
Assignee: nobody → ackley
Whiteboard: [b2ga11y p=1] → [b2ga11y p=1][good first bug]
Assignee | ||
Updated•10 years ago
|
Mentor: yzenevich
Assignee | ||
Comment 3•10 years ago
|
||
Hi Jim, do you need any more info or pointers regarding this bug? Thanks!
Flags: needinfo?(ackley)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → yzenevich
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•10 years ago
|
||
Some of the things to address: * get rid of false lists when navigating to phone number field and elsewhere * use correct roles on controls such as checkboxes and listboxes * fix issues around empty label containers
Summary: The screen reader reports a false list when navigating to phone number field → Improve accessibility for of the contacts app.
Whiteboard: [b2ga11y p=1][good first bug] → [b2ga11y p=1]
Assignee | ||
Comment 6•10 years ago
|
||
* Fix issues with dropdowns
Assignee | ||
Comment 7•10 years ago
|
||
Here's a number of a11y improvements. Mostly markup roles and aria attributes. Only a few CSS changes to make the markup consistent with presentation. I split up the PR as well to be easier to read.
Attachment #8479637 -
Flags: review?(francisco)
Comment 8•10 years ago
|
||
Comment on attachment 8479637 [details] [review] Github pull request. Hi Yura, thanks for the fantastic work, unfortunately I've been really busy with feature work and now your PR is not mergeable. Could you rebase and ask me again for r? Thanks
Attachment #8479637 -
Flags: review?(francisco)
Assignee | ||
Comment 9•10 years ago
|
||
Comment on attachment 8479637 [details] [review] Github pull request. Rebased as requested. Should look good now again.
Attachment #8479637 -
Flags: review?(francisco)
Comment 10•10 years ago
|
||
Comment on attachment 8479637 [details] [review] Github pull request. As I'm going on PTO and don't want this to be delayed more, would like Sergi to do a proper review. I did a install, and everything is looking good to me, but will let him to do the final r? Thx
Attachment #8479637 -
Flags: review?(sergi.mansilla)
Attachment #8479637 -
Flags: review?(francisco)
Attachment #8479637 -
Flags: feedback+
Comment 11•10 years ago
|
||
Comment on attachment 8479637 [details] [review] Github pull request. Looking good to me too, r+. Good job!
Attachment #8479637 -
Flags: review?(sergi.mansilla) → review+
Assignee | ||
Comment 12•10 years ago
|
||
Comment on attachment 8479637 [details] [review] Github pull request. This pull request improves overall Contacts app accessibility and makes it virtually all usable by the screen reader. [Bug caused by] (feature/regressing bug #): Improvement not a regression [User impact] if declined: Screen reader user will not be able to fully use some of the contacts app interfaces (switches, listitems, etc). The pull request improves the verbosity of elements spoken as well. [Testing completed]: Tests are passing. Most of the things here are markup and l10n changes. [Risk to taking this patch] (and alternatives if risky): Medium. Some CSS changes. Most of the markup changes only add/remove attributes that should have affect on users that do not use the screen reader. [String changes made]: https://github.com/mozilla-b2g/gaia/pull/23348/files#diff-10
Attachment #8479637 -
Flags: approval-gaia-v2.1?
Assignee | ||
Comment 13•10 years ago
|
||
(In reply to Yura Zenevich [:yzen] from comment #12) > Comment on attachment 8479637 [details] [review] > [Risk to taking this patch] (and alternatives if risky): Medium. Some CSS > changes. Most of the markup changes only add/remove attributes that should *should not* > have affect on users that do not use the screen reader.
Assignee | ||
Comment 14•10 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/77a475a68d3a17ca74cae64bc63e3263b353156a
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 15•10 years ago
|
||
This broke the call info page in the dialer. I'm fixing this in bug 1059087 by accident. In the future, we must be careful to mirror changes in details.html to phone_details.html and email_details.html, at least until bug 1060290 and bug 1060076 are fixed.
Comment 16•10 years ago
|
||
Comment on attachment 8479637 [details] [review] Github pull request. a- since this has already caused regressions on trunk.
Attachment #8479637 -
Flags: approval-gaia-v2.1? → approval-gaia-v2.1-
Updated•10 years ago
|
Assignee | ||
Comment 17•10 years ago
|
||
Comment on attachment 8479637 [details] [review] Github pull request. Asking for re-approval again. The only CSS regression that it caused was fixed in bug 1059087, that is also up for an approval. Fix missing spacing between "Carrier Name" and "Type Label". This pull request improves overall Contacts app accessibility and makes it virtually all usable by the screen reader. [Bug caused by] (feature/regressing bug #): improvement, not a regression [User impact] if declined: Screen reader user will not be able to fully use some of the contacts app interfaces (switches, list items, etc). The pull request improves the verbosity of elements spoken as well. [Testing completed]: Tests are passing. Tested manually with screen reader. It did cause a regression fixed in bug 1059087. Other than that it has been in master for a while without any more issues. [Risk to taking this patch] (and alternatives if risky): Medium. Some CSS changes. It did cause 1 regression because the old markup being used in dialer that was fixed in bug 1059087 that is also up for approval. [String changes made]: https://github.com/mozilla-b2g/gaia/pull/23348/files#diff-10
Attachment #8479637 -
Flags: approval-gaia-v2.1- → approval-gaia-v2.1?
Assignee | ||
Comment 18•10 years ago
|
||
Scratch: "Fix missing spacing between "Carrier Name" and "Type Label"."
Updated•10 years ago
|
Attachment #8479637 -
Flags: approval-gaia-v2.1? → approval-gaia-v2.1+
Comment 19•10 years ago
|
||
Needs rebasing for v2.1 uplift.
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → fixed
Flags: needinfo?(yzenevich)
Keywords: branch-patch-needed
Target Milestone: --- → 2.1 S4 (12sep)
Comment 20•10 years ago
|
||
I was going to rebase this myself so that I could land bug 1059087 on top of it, but it was too complicated an uplift without knowing what I was doing. Please make sure to make the changes in this patch in both of these places: https://github.com/mozilla-b2g/gaia/blob/v2.1/apps/communications/contacts/elements/phone_details.html https://github.com/mozilla-b2g/gaia/blob/v2.1/apps/communications/contacts/elements/details.html
Assignee | ||
Comment 21•10 years ago
|
||
Flags: needinfo?(yzenevich)
Updated•10 years ago
|
Keywords: branch-patch-needed
Comment 22•10 years ago
|
||
v2.1: https://github.com/mozilla-b2g/gaia/commit/36975afde437307b3873a7145f625b9beaa4a947
Comment 23•10 years ago
|
||
Hi Eitan, Could you provide the expected result for me to verify this bug? Thank you!
Flags: needinfo?(eitan)
Reporter | ||
Comment 24•10 years ago
|
||
This is a whole bunch of accessibility improvements. I'll defer to the patch author to determine the best way to verify.
Flags: needinfo?(eitan) → needinfo?(yzenevich)
Assignee | ||
Comment 25•10 years ago
|
||
There are several things that were worked on: * settings screen should have all elements readable and accessible (activatable) with the screen reader, that also includes all the sub-pages * contacts details should have all elements readable and accessible (activatable) with the screen reader * add contacts screen should have all elements readable and accessible including things like drop downs and check boxes. * the user should be able to search for contacts and consequently select them while using the screen reader
Flags: needinfo?(yzenevich)
You need to log in
before you can comment on or make changes to this bug.
Description
•