Accessibility Feedback for Staging Review [Claims & Appeals - Notice of Disagreement]

[joshkimux]

Accessibility Feedback for Staging Review [Claims & Appeals - Notice of Disagreement]

Feedback framework

• ❗️ Must for if the feedback must be applied
• ⚠️ Should if the feedback is best practice
• ✔️ Consider for suggestions/enhancements

Definition of done

1. Review and acknowledge feedback.
2. Fix and/or document decisions made.
3. Accessibility specialist will close ticket after reviewing documented decisions / validating fix.

Point of Contact

VFS Point of Contact: Josh and Angela

Pending items that need more review before being written into tickets (once ID.me is fixed)

1. Determine if sandwiched text between interactive elements is easy to miss when using the tab key. Can be addressed by placing instructional language above interactive elements, not below. Potential defect 2.

2. Determine if focus is being managed well, particularly when it comes to screen reader announcements. May be easier for focus to be placed on an actual input instead of the label/legend/paragraph. Potential defect 2-3.

3. Determine if buttons not having unique labels will present accessibility challenges. Potential defect 3.

4. Determine if a more descriptive label e.g. "Please specify other reasons" is needed. Potential defect 3-4.

[Mottie]

Pending issue updates:

1. Content added to an additional info dropdown

   Open additional info

   

2. No change - awaiting decision

3. Edit aria-label now includes the issue name (see PR #17508)

   Edit button with updated aria-label

   

4. Area of disagreement page content updated

   Other reason content update

   

   This last one, I'm not sure if the checkbox needs an aria-describedby that points to the "Please specify" input?

[joshkimux]

@Mottie 1, 2, and 4 look great; I don't think we'll need aria-describedby for the checkbox 🥳