Accessibility pod

[lizpearl]

Issue description

We want get.gov and manage.get.gov (including /admin) to be Section 508 Compliant. See items under Links to other issues below for more context.

Changes that are needed for compliance are captured in the tickets that have the priority BLOCKER
Also, consider working on a closely related non-BLOCKER ticket can easily be done with a BLOCKER ticket.

While working towards compliance, we also want to make sure we looking holistically at maintaining compliance. Can we structure things differently? Do we need to give the devs pointers?

Suggestions of how to work

This Renewal Pod doc is an awesome example of tracking and communicating work

Acceptance criteria

• Consult together on how to approach the compliance work
• Complete all accessibility tickets with the priority BLOCKER
• ACs from Document Accessibility Best Practices for Developers #3342. Devs should add items (especially from observations of ongoing a11y dev work), edit, and assist as needed.

Additional context

Notes on ticket creation:

• If possible, add any tickets as a sub-issue of this ticket. Most likely that will only apply to bundles since other tickets already have parents
• Label your tickets with dev and/or design and also Pod: Accessibility Compliance

Links to other issues

• Accessibility - 508 assessment and remediation #3335
• Accessibility: Obtain Section 508 Compliance Certification for manage.get.gov #2577
• Accessibility: Obtain Section 508 Compliance Certification for get.gov get.gov#356
• Document Accessibility Best Practices for Developers #3342