Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add accessibility considerations #412

Closed
wants to merge 1 commit into from

Conversation

chaals
Copy link

@chaals chaals commented Jan 25, 2023

closes #411 (minimally - this is still punting issues like actually explaining to real people what "this feature on this origin" actually means).

The following tasks have been completed:

  • Modified Web platform tests (link)

Implementation commitment:

  • WebKit (link to issue)
  • Blink (link to issue)
  • Gecko (link to issue)

Preview | Diff

fix #411 (minimally - this is still punting issues like actually explaining to real people what "this feature on this origin" actually means).
<p>
Interfaces intended to allow the user to review, update, and reset the
[=permission=] [=permission/state=] of [=powerful features=] associated with an [=origin=].
MUST respect platform accessibility conventions.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this true of every UA interface? Why would permissions need special text for this? Were there specific problems with permission UI? Did browsers push back when you filed bugs about those?

Copy link
Member

@miketaylr miketaylr Feb 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ping @chaals ^^

Copy link
Member

@marcoscaceres marcoscaceres Feb 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tend to agree with @jyasskin... this is seems somewhat overly general and doesn't really add much.

I'd be inclined to add guidance around this if we had seen issues (or foresee accessibility issues!) with the UIs being presented.

So far, the UIs have been ok, no?

@marcoscaceres
Copy link
Member

We discussed this in the Editors meeting and decided we will keep this as is. Hope that's ok @chaals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No references to accessibility
4 participants