Permission indicator sharing state should change more than just the color
Categories
(Firefox :: Site Permissions, defect, P3)
Tracking
()
| a11y-review | requested |
People
(Reporter: bvandersloot, Unassigned)
Details
For accessibility reasons, state changes should not be represented by color only. Perhaps a badge or something would make it clearer when a permission is being shared.
Updated•17 days ago
|
Another UX rule is that information should never be available only temporarily. What if the user is looking away while the page accesses data, or what if a malicious page only accesses data when the page is not in focus, making sure the user does not see it?
I would recommend using badges which show a number that increases each time the permission has been used. This is a very common design that I think most people are familiar with, and it solves all the UX issues.
Comment 2•10 days ago
|
||
Benjamin, will this bug be assigned and uplifted for 153? Thanks.
| Reporter | ||
Comment 3•10 days ago
|
||
We will not. I will request a11y review to see if it is worth prioritization.
| Reporter | ||
Comment 4•10 days ago
|
||
Description:
We noticed that the permissions UI displays some state via the color of the icon alone. That was pointed out as a potential a11y issue, so this bug was filed.
How do we test this?
Open a video call in the browser. When you mute the camera, the camera icon turns grey. When active, it's red.
When will this ship?
It's been shipped a long time.
The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible:
https://wiki.mozilla.org/Accessibility/Guidelines
Please describe the accessibility guidelines you considered and what steps you've taken to address them:
n/a
Describe any areas of concern to which you want the accessibility team to give special attention:
This is legacy behavior and we would just like to know how much of an issue this is so we can assign it the right priority.
Comment 5•7 days ago
|
||
The bug is marked as tracked for firefox153 (beta). However, the bug still isn't assigned, has low priority and has low severity.
:dmehic, could you please find an assignee, increase the priority and increase the severity for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Updated•7 days ago
|
Updated•7 days ago
|
Description
•