Accessibility/508 audit

[lbeaufort]

We are overdue for a 508/accessibility/a11y audit. We should do the audit and enter follow-up issues separately. Here are some ideas on how to test: https://www.section508.gov/test

Front-facing sites

• Front-end site (including eregs)
• API docs
• Pattern library

Next steps

• identify weaknesses and an 80:20
• make tickets for different issues (e.g., it would be easier to hit site-wide table <caption> tags with one ticket and then <figure><image> with a different ticket)

[patphongs]

Some ideas to conduct accessibility audits on our website:

1. Take a look at 18F's accessibility guide, it has a lot of good tips: https://accessibility.18f.gov
2. Run an audit on each type of page template, we have several and you can see them in our pattern library: https://fec-pattern-library.app.cloud.gov/docs/page-layouts/collection-page.html. That will help point out which templates can be fixed immediately in terms of accessibility compliance.
3. Run an analysis on our datatables and visualization work
4. Run a design audit in terms of colors we use for accessibility. A lot of the work that has been done already has kept color schemes and readability in mind.
5. There's lots of different tools we can use for accessibility. WAVE is a popular tool. There are other tools as well: https://accessibility.18f.gov/tools/

[lbeaufort]

We could also add a11y into our build pipeline: https://github.com/usdoj-crt/crt-portal/blob/7b0fa359d14187eece5a9a82f4ee80218e1172e0/.circleci/config.yml#L62