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.

Sign up for GitHub

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 19 commits into
base: main
Choose a base branch
from
Open

Add a11y guidance for user agents #238

Changes from all commits
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
e06dd05
Add a11y guidance for user agents
MasterKale May 13, 2025
a245634
Merge branch 'main' into 229-horizontal-review-accessibility
MasterKale Jun 2, 2025
05ecad5
Change "consent" -> "permission"
MasterKale Jun 2, 2025
fe2bb38
Merge branch 'main' into 229-horizontal-review-accessibility
MasterKale Jun 11, 2025
d3691d7
Merge branch 'main' into 229-horizontal-review-accessibility
marcoscaceres Jul 1, 2025
4d54404
Merge branch 'main' into 229-horizontal-review-accessibility
MasterKale Jul 8, 2025
8e19913
Update copy for PR feedback
MasterKale Jul 8, 2025
291797a
Apply suggestions from code review
marcoscaceres Aug 5, 2025
3cc117e
Merge branch 'main' into 229-horizontal-review-accessibility
marcoscaceres Aug 5, 2025
d292753
Merge branch 'main' into 229-horizontal-review-accessibility
marcoscaceres Aug 21, 2025
698bc50
Merge branch 'main' into 229-horizontal-review-accessibility
marcoscaceres Aug 27, 2025
b8d011c
Merge branch 'main' into 229-horizontal-review-accessibility
MasterKale Aug 27, 2025
e1c0743
Incorporate feedback
MasterKale Aug 27, 2025
4bf85e7
Point to issuance and presentation in the spec
MasterKale Aug 27, 2025
5357eec
Use regular dashes to match the rest of the doc
MasterKale Aug 27, 2025
0892b30
Merge branch 'main' into 229-horizontal-review-accessibility
MasterKale Sep 3, 2025
fa0d26c
Remove informative class from a11y section
MasterKale Sep 3, 2025
103e713
Merge branch 'main' into 229-horizontal-review-accessibility
MasterKale Sep 10, 2025
0348eea
Incorporate PR feedback
MasterKale Sep 10, 2025
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
17 changes: 14 additions & 3 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2062,15 +2062,26 @@ <h4>
</p>
</section>
</section>
<section class="informative">
<section>
<!--
// MARK: Accessibility Considerations
-->
<h2>
Accessibility Considerations
</h2>
<p class="issue" title="Work in Progress">
This section is a work in progress as this document evolves.
<p>
Implementers need to consider accessibility when designing [=credential choosers=]
Copy link
Contributor

Choose a reason for hiding this comment

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

"credential choosers" are out of scope for this API, this it is the responsibility of the underlying platform to display them.
Not sure if this actually fits here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okay, good point. This should really be about user agents, that might put some UI before invoking the credential chooser, making that UI accessible. Could a simple replacement here work?

Copy link
Collaborator

@marcoscaceres marcoscaceres Sep 3, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

I'm ok with keeping [=credential choosers=] here... the API still needs to present a credential chooser because Cred Man explicitly requires it as part of the get a credential steps.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I dug into the CredMan definition that [=credential choosers=] ends up getting linked to, and it's to a section on User Mediated Selection that talks about credential choosers as something that User Agents implement:

https://www.w3.org/TR/credential-management-1/#user-mediated-selection

When responding to a call to get() on an origin which requires user mediation, user agents MUST ask the user for permission to share credential information. This SHOULD take the form of a credential chooser which presents the user with a list of credentials that are available for use on a site, allowing them to select one which should be provided to the website, or to abort the request entirely.

This must be what @marcoscaceres is referring to above (I'm making this connection more for my benefit.) So perhaps it's okay to keep the mention of credential choosers here. @mohamedamir might this change your mind about this particular section of accessibility guidance?

specifically for this API. The content of modal dialogs
presented during [=digital credential/issuance request|issuance=]
or [=digital credential/presentation requests|presentation=],
which can include text, QR codes, and other visual media,
SHOULD be labelled and exposed to assistive technologies.
</p>
<p>
Interactive elements, particularly those that allow the user
to continue or abort [=digital credential/issuance request|issuance=]
or [=digital credential/presentation requests|presentation=] requests,
MUST be operable in a device-independent manner.
</p>
</section>
<section id="idl-index"></section>
Expand Down