Skip to content

Add a11y guidance for user agents #238

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -963,8 +963,14 @@ <h3>
<h2>
Accessibility Considerations
</h2>
<p class="issue" title="Work in Progress">
This section is a work in progress as this document evolves.
<p>
[=User agents=] SHOULD mediate presentation and issuance requests in a
way that offers support for a wide range of user input methods, including
input hardware like keyboards, pointing devices, touch screens, voice
recognition, etc. Additionally, user agents SHOULD support accessible
output methods during these requests to ensure that prompts for
[=user consent=] during such requests can be meaningfully communicated to
Copy link
Collaborator

@timcappalli timcappalli May 14, 2025

Choose a reason for hiding this comment

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

We've traditionally said that the browser only handles permission, not consent.

It seems we have a mismatch on the term definition / section title and meaning. Opened an issue here: #239

the widest range of end-users.
</p>
</section>
<section id="idl-index"></section>
Expand Down