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

.gov Registrar: Ensure unique and descriptive accessible names for IP Address form fields #3589

Open
4 tasks
SamiyahKey opened this issue Feb 27, 2025 · 1 comment
Assignees
Labels
accessibility pertains to Section 508 compliance or other accessibility needs blocked Is dependent on another issue and cannot be worked 👥 Pod:Accessibility Compliance Describes work needed for get.gov and manage.get.gov to be Section 508 Compliant compliance indicates that the issue is required to satisfy a necessary compliance req dev issue is for the dev team

Comments

@SamiyahKey
Copy link

SamiyahKey commented Feb 27, 2025

Issue description

As a screen reader user, I need each “IP address (IPv4 or IPv6)” form field to have a unique and descriptive accessible name so that I can understand which server the field corresponds to and enter the correct IP address without confusion.

This will ensure compliance with Trusted Tester ID [1.3.1 Info and Relationships] and WCAG success criteria 2.4.4 Name, Role Value, which requires that the purpose fields be clear from their labels alone.

URL: DNS name servers | calgiftedskool.gov | .gov Registrar (cloud.gov)

Current Issue:

  • The IP address form fields currently share the same accessible name, making them indistinguishable for screen reader users.

  • This creates confusion as users cannot determine which IP address field belongs to which server.

Image

Acceptance criteria

  • Each IP address form field has a unique and descriptive accessible name that clearly indicates the server it corresponds to (e.g., “Server 1 IP Address (IPv4 or IPv6),” “Server 2 – IP Address (IPv4 or IPv6)”).

  • The accessible name should match or align with the visible label to provide a consistent experience.

  • Screen readers should announce distinct labels for each IP address field.

  • Implementation should be verified using assistive technologies such as NVDA, JAWS, or VoiceOver.

Additional context

This story resolves issue 5 Trusted Tester 508 report and remediation plan

Links to other issues

This issue is blocked by #3256

@SamiyahKey SamiyahKey moved this from 👶 New to 🎯 Ready in .gov Product Board Feb 27, 2025
@SamiyahKey SamiyahKey added dev issue is for the dev team compliance indicates that the issue is required to satisfy a necessary compliance req accessibility pertains to Section 508 compliance or other accessibility needs 👥 Pod:Accessibility Compliance Describes work needed for get.gov and manage.get.gov to be Section 508 Compliant labels Feb 27, 2025
@zandercymatics zandercymatics added the blocked Is dependent on another issue and cannot be worked label Mar 3, 2025
@zandercymatics
Copy link
Contributor

zandercymatics commented Mar 3, 2025

@SamiyahKey Added a "blocked" label as this is waiting on this ticket that dave is working on + moved this into the next sprint for that reason

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility pertains to Section 508 compliance or other accessibility needs blocked Is dependent on another issue and cannot be worked 👥 Pod:Accessibility Compliance Describes work needed for get.gov and manage.get.gov to be Section 508 Compliant compliance indicates that the issue is required to satisfy a necessary compliance req dev issue is for the dev team
Projects
Status: 🎯 Ready
Development

No branches or pull requests

2 participants