You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inaccessible permissions are a huge issue. They can make people with disabilities less safe, while not even KNOWING they are less safe. I believe it is important to have a section in this document specifically on accessibility cross-linked to the relevant WCAG criteria. Off the top of my mind, that would be labels, meaningful sequence, keyboard interaction, non-graphical descriptions, keyboard focus indicator, and color ratio. There may be a few I missed. Happy to attend a meeting to discuss further. You can reach out to me at [email protected] to schedule that.
The text was updated successfully, but these errors were encountered:
Is this a problem with how UAs implement their permission dialogs, or with something about how websites frame their permission requests?
I don't think it makes sense to have the permissions document say something generic like "follow best practices", but if there's a special way that the WCAG (or native accessibility guidelines) apply to permissions that they wouldn't apply to other parts of browser UI, that could make sense to explain here.
Inaccessible permissions are a huge issue. They can make people with disabilities less safe, while not even KNOWING they are less safe. I believe it is important to have a section in this document specifically on accessibility cross-linked to the relevant WCAG criteria. Off the top of my mind, that would be labels, meaningful sequence, keyboard interaction, non-graphical descriptions, keyboard focus indicator, and color ratio. There may be a few I missed. Happy to attend a meeting to discuss further. You can reach out to me at [email protected] to schedule that.
The text was updated successfully, but these errors were encountered: