From e06dd0558e669daae28b43eabd91bf21a79fbddc Mon Sep 17 00:00:00 2001
From: Matthew Miller <mmiller@duosecurity.com>
Date: Tue, 13 May 2025 14:11:18 -0700
Subject: [PATCH 1/3] Add a11y guidance for user agents

---
 index.html | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 6e8a43fc..9ddd5741 100644
--- a/index.html
+++ b/index.html
@@ -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
+        the widest range of end-users.
       </p>
     </section>
     <section id="idl-index"></section>

From 05ecad50e0a54a30833d1d5af3479b12ebb82611 Mon Sep 17 00:00:00 2001
From: Matthew Miller <mmiller@duosecurity.com>
Date: Mon, 2 Jun 2025 12:14:08 -0700
Subject: [PATCH 2/3] Change "consent" -> "permission"

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 13d80f7e..3a86ba41 100644
--- a/index.html
+++ b/index.html
@@ -978,7 +978,7 @@ <h2>
         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
+        [=user permission=] during such requests can be meaningfully communicated to
         the widest range of end-users.
       </p>
     </section>

From 8e199138411b7cbc22aea04a8e5aedbb804595d2 Mon Sep 17 00:00:00 2001
From: Matthew Miller <matthew@millerti.me>
Date: Tue, 8 Jul 2025 14:34:48 -0700
Subject: [PATCH 3/3] Update copy for PR feedback

---
 index.html | 23 ++++++++++++++++-------
 1 file changed, 16 insertions(+), 7 deletions(-)

diff --git a/index.html b/index.html
index d80646d6..5015a2c0 100644
--- a/index.html
+++ b/index.html
@@ -86,6 +86,13 @@
           date: "2025-02-25",
           publisher: "W3C"
         },
+        "credman-accessibility": {
+          title: "5.3. Credential Selection",
+          href:" https://w3c.github.io/webappsec-credential-management/#user-mediated-selection",
+          authors: ["Nina Satragno", "Marcos Cáceres"],
+          date: "2024-08-13",
+          publisher: "W3C"
+        }
       },
       xref: {
         profile: "web-platform",
@@ -1894,13 +1901,15 @@ <h2>
         Accessibility Considerations
       </h2>
       <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 permission=] during such requests can be meaningfully communicated to
-        the widest range of end-users.
+        Credential presentation and issuance facilitated by the Digital Credentials API have many
+        of the same accessibility considerations as detailed in [[[credman-accessibility]]] of the
+        Credential Management API.
+      </p>
+      <p>
+        [=credential chooser | Credential choosers=] have additional responsibilities. Contents
+        displayed to users during these ceremonies, including modal dialogs and QR codes, should be
+        accessible to screen readers. Interactive elements of a ceremony should also be
+        keyboard-accessible whether the user wishes to proceed with the ceremony or abort it.
       </p>
     </section>
     <section id="idl-index"></section>