Ensure new design is accessible
Categories
(Firefox :: Address Bar, task, P1)
Tracking
()
People
(Reporter: bugzilla, Assigned: mak)
References
(Blocks 1 open bug)
Details
(Whiteboard: [proton-address-bar])
Proton will not change any address bar functionality, so the things to check here are high contrast modes and the contrast between the new hover/selected states in the results pane.
|
Reporter | |
Updated•4 years ago
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 1•4 years ago
|
||
We should also check RTL while there.
|
|
Assignee | |
Comment 2•4 years ago
|
||
And check the new Add Engine options in the search shortcuts and the context menu.
|
||
Updated•4 years ago
|
|
|
Reporter | |
Comment 3•4 years ago
•
|
||
I think this was a P2 just because all the bugs were set to P2 when I filed them. I think accessibility should block MR1, so I'm setting this to P1.
|
|
Assignee | |
Comment 4•4 years ago
|
||
Hover/selected for the default themes was already confirmed by UX in https://bugzilla.mozilla.org/show_bug.cgi?id=1702018#c6 and previous discussions. I think here we should concentrate on HC looking ok on Windows and Linux with the Default theme, checking urlbar elements can be keyboard navigated (including the overflow meatball menu) and check new Add Engine options (in the shortcut buttons and in the context menu) are accessible with a screen reader.
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 5•4 years ago
|
||
I tested High Contrast on Windows and Linux (Ubuntu 20), NVDA on Windows and VoiceOver on Mac.
These are the issues I noticed during my accessibility review:
High Contrast Mode issues: Bug 1705814, Bug 1706321
Keyboard navigation issues: Bug 1706326
Screen readers issues: Bug 1706334, bug 1706337 (this is not related to Proton, but it's a recent regression)
|
||
Comment 6•4 years ago
|
||
Taking this out of uplift queries.
Description
•