Uploaded August 2021 | Updated November 2026, 3 hours ago
Web designers and developers, if you're building accessible websites or you want to, we need to talk.
So many web designers and developers who THINK they are building accessible websites really aren't!
I know this because I've done accessibility audits of websites built by some of them. I've also seen the websites of web designers and developers who think they just created an accessible website.
You might think that using an accessible theme makes your websites accessible.
You might think that testing the site with a screen reader means your websites are accessible.
You might think that getting your sites to pass an automated checker—or more than one—means your site is accessible.
You might think that adding ARIA to HTML tags makes your sites accessible.
You might think that ticking off a list of WCAG guidelines makes your sites accessible.
You might think doing all of these things will make your sites accessible.
Let me tell you: this is not the case! And I'm telling you this because you could get yourself in hot water… you could get your clients in hot water. And I don't want to see that.
First off, there is so much more to accessibility than a theme. Many themes have accessibility issues, some of them major ones. But themes also don't affect the design or the text or the images or audio and video on the site.
They also don't do anything for the downloadable documents on the site. Those often get overlooked.
When you test with only a screen reader, you're ignoring so many other groups of people with a disability that is not related to the use of a screen reader.
Automated checkers can only detect about 25% to 30% of issues. Some are better than others. Some are worse than others. And some find more things on one site than they will on the next site you check.
The majority of issues require human inspection and manual fixing.
When it comes to ARIA, adding more is not better. I see this all the time when I do audits. In many cases, where I see web developers adding ARIA, it was not only unnecessary to add it in the first place, but it made the accessibility of the site much worse!
I mentioned WCAG a minute ago. You could potentially check off a list of WCAG guidelines and still end up with an inaccessible website.
Many guidelines are open to interpretation and unclear. One of my students even said they made her eyes glaze over.
And how would you know if you're interpreting them correctly?
If you want to learn more about how to get into web accessibility and find out 3 common mistakes, register for my free workshop on Sept. 1. Go to bit.ly/3easysteps4
Web designers and developers, if you're building accessible websites or you want to, we need to talk.
So many web designers and developers who THINK they are building accessible websites really aren't!
I know this because I've done accessibility audits of websites built by some of them. I've also seen the websites of web designers and developers who think they just created an accessible website.
You might think that using an accessible theme makes your websites accessible.
You might think that testing the site with a screen reader means your websites are accessible.
You might think that getting your sites to pass an automated checker—or more than one—means your site is accessible.
You might think that adding ARIA to HTML tags makes your sites accessible.
You might think that ticking off a list of WCAG guidelines makes your sites accessible.
You might think doing all of these things will make your sites accessible.
Let me tell you: this is not the case! And I'm telling you this because you could get yourself in hot water… you could get your clients in hot water. And I don't want to see that.
First off, there is so much more to accessibility than a theme. Many themes have accessibility issues, some of them major ones. But themes also don't affect the design or the text or the images or audio and video on the site.
They also don't do anything for the downloadable documents on the site. Those often get overlooked.
When you test with only a screen reader, you're ignoring so many other groups of people with a disability that is not related to the use of a screen reader.
Automated checkers can only detect about 25% to 30% of issues. Some are better than others. Some are worse than others. And some find more things on one site than they will on the next site you check.
The majority of issues require human inspection and manual fixing.
When it comes to ARIA, adding more is not better. I see this all the time when I do audits. In many cases, where I see web developers adding ARIA, it was not only unnecessary to add it in the first place, but it made the accessibility of the site much worse!
I mentioned WCAG a minute ago. You could potentially check off a list of WCAG guidelines and still end up with an inaccessible website.
Many guidelines are open to interpretation and unclear. One of my students even said they made her eyes glaze over.
And how would you know if you're interpreting them correctly?
If you want to learn more about how to get into web accessibility and find out 3 common mistakes, register for my free workshop on Sept. 1. Go to bit.ly/3easysteps4










