.gov Registrar : Ensure unique and descriptive accessible names for delete buttons in DNS name servers

[SamiyahKey]

Issue description

As a screen reader user, I need each delete button on the DNS name servers fields to have a unique and descriptive accessible name so that I can identify which server it is associated with and confidently perform the correct action. @zandercymatics has also pointed out other issues with buttons throughout all pages of the domain management workflow that he will correct (these were not called out in the Section 508 compliance test)

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 of links and buttons be clear from their labels alone.

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

Current Issue:

• The delete buttons on the page currently share the same accessible name, making them indistinguishable for screen reader users.

• This creates confusion as users cannot determine which button corresponds to which server.

Acceptance criteria

• Each delete button has a unique and descriptive accessible name that clearly indicates the server it corresponds to (e.g., "Delete Server 1," "Delete Server 2").

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

• Zander to survey all buttons and correct accessible names on the following pages:

• Domain overview
• DNS
• Name servers
• DNSSEC
• Suborganization
• Security email
• Domain managers

• Screen readers should announce distinct labels for each delete button.

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

Additional context

By programmatically giving the buttons unique accessible names, we reduce the risk of in users selecting the wrong search function, causing frustration and inefficiency. This improves the overall user experience.

Additional guidance:

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

WAI ARIA Accessible Names and Descriptions

Links to other issues

No response

[zandercymatics]

@SamiyahKey Since the DNS page is undergoing a refactor by dave, that part of the ticket is blocked until that gets merged!
I can however work elsewhere and on other pages. Will add blocked and add to the next sprint