Continuous manual accessibility testing

In modern development workflows, automated linters continuously validate our front-end code. This ensures that the UI remains error-free.

But usability involves human interaction and comprehension. It extends far beyond the syntax of our HTML, CSS and JavaScript.

We realise this, so we manually test it. Continuously.

If continuous manual usability testing is a part of our workflow, why is manual accessibility testing only done at the end of the project?

Manual usability testing

We continuously manually test usability during development, to ensure that the UI is usable.

To validate our approach, we should also test with representatives of the target user group, as often as possible.

But sometimes budget constraints get in the way of this. Either way, the target user group will use the site and benefit or suffer, based on the usability decisions that we have made.

Manual accessibility testing

We should also continuously manually test accessibility during development, to ensure that the UI is accessible.

To validate our approach, we should also test with representatives of the impaired user group, as often as possible.

But sometimes budget constraints get in the way of this. Either way, the impaired user group will use the site and benefit or suffer, based on the accessibility (and usability) decisions that we have made.

I think the only thing standing in our way here is knowledge. Once we know how to test, continuous accessibility testing will become a natural part of our workflow.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.