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.
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: