What resources do you use to decide what is most vital when you start advocating for Accessibility in an application? What resources do you use when you start testing for Accessibility?

Charles Penn asked 

One of the great things about accessibility testing is that the simplest resource is a keyboard. As keyboard navigation is foundational to good access and other assistive technologies rely on it, ensuring it is good is a high priority.

In my article, The 6 most common digital accessibility bugs and how to fix them, I go through the most common issues, how to test for them, and how to fix them. In terms of resources.

Low-contrast needs a checker, and there are lots of free options, like the WAVE tool from WebAIM. WAVE can also check for missing alternative text, or just use developer tools. WAVE will tell you if there are missing form input labels, empty links or buttons, and if no language has been defined.

From there, it would depend on what you were specifically checking for. There are lots of screen readers on desktop and mobile, lots of tools like taba11y to map tab routes. Then there are automated checkers such as WAVE, DevTools, and Lighthouse.

Hope that helps

Check out more answers in the AMA about Accessibility Testing collection.