Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility Fixes #18

Open
DanielMiller-agile6 opened this issue Mar 13, 2020 · 1 comment
Open

Accessibility Fixes #18

DanielMiller-agile6 opened this issue Mar 13, 2020 · 1 comment
Labels
Bug Something isn't working

Comments

@DanielMiller-agile6
Copy link
Contributor

I ran some quick accessibility tests over the agile6.com site (using Axe Chrome plugin) and found a few issues. There aren't many serious or critical failures, but most of these should be quick fixes. We're also missing skip nav links, which are helpful for screen readers and keyboard navigation. As a government contracting company, it might be good to show that we practice what we preach regarding 508 compliance :).

First steps would be to resolve issues found from these tests, but we could delve deeper in the future with a more robust accessibility audit and automated axe-core tests as part of our build and deploy process.

Here are a few screenshots of errors I found:

Screen Shot 2020-03-13 at 2 33 56 PM

Screen Shot 2020-03-13 at 2 36 18 PM

Screen Shot 2020-03-13 at 2 37 18 PM

@DanielMiller-agile6 DanielMiller-agile6 added the Bug Something isn't working label Mar 13, 2020
@ElijahLynn
Copy link
Contributor

Thanks for reporting this, tracking for now until have more time to help out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants