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

Purpose of your request domain screen reader output #2914

Open
Tracked by #2913
AnnaGingle opened this issue Oct 7, 2024 · 1 comment · May be fixed by #3105
Open
Tracked by #2913

Purpose of your request domain screen reader output #2914

AnnaGingle opened this issue Oct 7, 2024 · 1 comment · May be fixed by #3105
Assignees
Labels
accessibility bundled Parent ticket will be sprinted and this ticket is included in the parent dev

Comments

@AnnaGingle
Copy link

AnnaGingle commented Oct 7, 2024

Screenshot 2024-10-07 at 4 20 10 PM

Current screen reader output

Purpose * You can enter up to 2000 characters required

<label>: Purpose *
aria-describedby: You can enter up to 2000 characters
required: required

What it should be

Default:
What is the purpose of your requested domain? Describe how you’ll use your .gov domain. Will it be used for a website, email, or something else? You can enter up to 2000 characters required

<legend>: What is the purpose of your requested domain?
<label>: Describe how you’ll use your .gov domain. Will it be used for a website, email, or something else?
aria-describedby: You can enter up to 2000 characters
required: required

Error state:
What is the purpose of your requested domain? Describe how you’ll use your .gov domain. Will it be used for a website, email, or something else? You can enter up to 2000 characters required, Describe how you’ll use the .gov domain you’re requesting.
required: required, Describe how you’ll use the .gov domain you’re requesting.

Prioritization Comments

WCAG Conformance Level: 2.1 AA
WCAG Standard that applies:
1.3.1 - Info and Relationships (Critical, partially supported)
3.3.2 - Labels or Instructions (Critical, partially supported)
4.1.2 - Name, Role, Value (Critical, partially supported)
Critical Failure if Not Met?: No
Prioritization: High/Must Do
Reason: This issue impacts accessibility by providing slightly incorrect labeling and descriptions for screen reader users. However given the context of this issue, the screenreader does say "required" in the ARIA output so this is not a complete failure. Ensuring accessible and descriptive labels is essential for clear form navigation, especially for users relying on assistive technologies.

@lizpearl lizpearl moved this from 👶 New to 🍦 Backlog in .gov Product Board Nov 6, 2024
@erinysong erinysong moved this from 🍦 Backlog to 🏗 In progress in .gov Product Board Nov 20, 2024
@erinysong erinysong self-assigned this Nov 21, 2024
@erinysong
Copy link
Contributor

erinysong commented Nov 21, 2024

How important is it that we reach this screenreader output from a legend? A legend typically indicates that we group together related field and are traditionally grouped with a box around them (example below: DNSSEC fields grouped under a legend) We can style our CSS to remove this but given this form only has one field, would we rather just add screenreader text indicating the details above without changing the HTML to a legend?

Example: DNSSEC form grouped in a legend
Image

@lizpearl lizpearl added the bundled Parent ticket will be sprinted and this ticket is included in the parent label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility bundled Parent ticket will be sprinted and this ticket is included in the parent dev
Projects
Status: 🏗 In progress
Development

Successfully merging a pull request may close this issue.

4 participants