[PAUSE STUFF] Determine Content accessibility needs

[SamHyler]

Overview

Determine accessibility needs and make a plan to implement them.

Can include for example word choice (A UX example would be: using deceptive design rather than "dark pattern"), writing for screen readers, adding alt text, etc.

See also Dev issue https://github.com/hackforla/expunge-assist/issues/487

Define Content accessibility goals. This issue follows up on UXR accessibility goals issue #959.

When looking at this issue and starting again, please review and adapt below.

Action Items

• [ ] Initiate this discussion with Design to see how we can proceed together
• [ ] Determine what accessibility needs users have and the tools needed
• [ ] Determine content accessibility recommendations
• [ ] Update content/writing guidelines with accessibility guidelines
• [ ] Update website and collaborate with any necessary teams

From other issue (now closed)

• [ ] Review accessibility standards and guidelines such as WCAG
• [ ] Brainstorm content accessibility goals in this document
• [ ] Identify 3-4 accessibility goals for UXR accessibility research by 7/7

Resources/Instructions

From now closed issue:

• [ ] Read the ADA Compliance Guide.
• [ ] The a11y project
• [ ] Issue #959 websites and resources
• [ ] Web Content Accessibility Guidelines (WCAG) website
• [ ] W3C Web Accessibility Initiative (WAI)

See also https://github.com/hackforla/expunge-assist/issues/410

[aahvocado]

should link with #487

[SamHyler]

https://github.com/hackforla/expunge-assist/issues/967