The web is undoubtedly most important resource today. Modern websites are built in small building blocks; components. Practices from test-driven software development have employed to automate correctness of these building blocks.
Being the most important source of information, internet should be accessible to all. It is important to provide equal access and opportunity to people with disabilities.
You can find many tools to check accessibility on web pages. But, in my opinion, when you’re testing web pages in a modern application, you’re are very late. Accessibility testing should be employed at the lowest level; you should create accessible components.
Unit Testing Accessibility
Let’s simple component which renders following HTML:
Elements with ARIA roles must use a vaild, non-abstract ARIA role.
Above is a very simple example to check static HTML for accessibility. Next, I would be exploring techniques to test accessibility for all four types of disabilities — visual, auditory, motor and cognitive. The a11y project has curated a list of rules as web accessibility checklist, an automated tool to run these rules would be next step in my accessibility exploration.