Why good SEO is always accessible

Accessibility and SEO are very similar. That’s why you should consider both on your website.

Published: 24.07.2024 | Updated: 27.11.2025 (translated)
Content: SEO best practices, UX, accessibility, technical SEO

As an online marketing freelancer, I regularly test new SEO tools. If I don’t want to keep the tool afterwards, I usually just delete my account. And that’s exactly where I recently came across something that frustrated me a bit:

Please call us to delete your account

Admittedly: “You have to call us so we can delete your data” would be annoying anyway. But that’s not actually what bothers me the most. The fact is that it is certainly not accessible to force customers to call a call center in order to exercise their right to have their data deleted.

For deaf people, that’s almost impossible or only possible with considerable extra effort. But it’s also a huge barrier for people with social anxiety, non-verbal people (e.g. with autism spectrum disorder), or simply for people who are hard of hearing.

Especially with an SEO tool, this just makes me suspicious, because SEO specialists should always keep accessibility in mind. Good search engine optimization is, by definition, accessible.

Why accessibility and SEO always go hand in hand

The most obvious reason is the legal situation. All major internet service providers – Google, Apple, Meta & Co. – are driven by compliance. And many legal systems now have laws on accessibility that often also regulate the accessibility of digital offerings.

In the US, for example, there is the Americans with Disabilities Act (ADA), in the EU the European Accessibility Act (EAA), and even in Switzerland there is the BehiG, which at least mandates accessibility for government websites. It would be a mistake to think of these laws as mere paper tigers, because the topic has already been extensively litigated in court and has cost some large companies hefty fines.

Infographic: Selected accessibility court cases

That’s precisely why it’s no surprise that Google takes the topic seriously and wants to steer its content providers towards following accessibility best practices. Not least for this reason, it’s standard SEO practice to add an alt text to every image, for example.

These accessibility best practices also help your SEO

Accessibility is far from just a “we have to do it” topic. Very often, web accessibility runs parallel to SEO best practices. Because ultimately, both pursue the same goal: good UX, clean, well-structured code, clear language, and easy-to-navigate websites. All of these are not only prerequisites for a high ranking on Google, but also the basic requirements that allow people with impairments to use a website at all. There are many examples of this:

Alt texts

As already mentioned, pretty much every SEO specialist and content manager learns this on day one: “Short, meaningful alt texts for every image.” And the reason for this is not, as is often mistakenly assumed, that the specific text itself is a ranking factor.

No, alt texts help people who navigate the web using a screen reader (e.g. blind people). Instead of seeing the images, they have them “read out” to them. And for Google, this is an easy way to check whether a website is accessible – and downgrade it in the rankings if not.

Alt texts can also help other users: If an image is accidentally deleted or someone with a slow internet connection loads your site, the site still makes sense even if the image is missing.

HTML tags and structure

It’s a common phenomenon that website owners use H3 headings instead of H2 headings just because it “looks nicer”. My clear recommendation is to adjust the stylesheet instead or, if necessary, change the size via inline CSS rather than using such workarounds. Because that harms both accessibility and SEO.

A person using a screen reader can only understand the text if the HTML tags make sense and an H3 heading is only used when the paragraph is actually a sub-section of an H2 heading.

(If you’re curious how a website is navigated with a screen reader, you can watch this video)

The Google crawler has exactly the same problem. It also doesn’t understand that a heading level has been misused purely for aesthetic reasons, and so it misinterprets the text. The most important section of your blog post can quickly become a minor sidebar in the eyes of the search engine.

And ARIA elements (Accessible Rich Internet Applications) also tell both screen readers and the Google crawler how to interpret an element – for example, a form field.

Descriptive navigation elements

A similar mechanism applies to links and navigation elements. An anchorless link (i.e. a link without visible text) gives neither a blind person nor the Google crawler any clue what to expect on the linked page or how it relates to the current page. This makes it very hard to use the important ranking signal of link text effectively.

Tables and lists in images

The next faux pas is particularly annoying: it’s common to see lists and tables on websites that have, for aesthetic reasons, been…

Tables, lists, and other highly structured elements are especially information-dense and contain highly relevant clues for understanding the text. By contrast, an image is unreadable for both screen readers and Google. As a result, this information – which would likely have a very positive effect on the page’s ranking – becomes completely inaccessible.

How accessibility also improves your user experience

Accessibility best practices in web design don’t just have a direct positive effect on SEO. They also help your site indirectly in many other ways. The best ranking on the strongest keyword is useless if 99% of users leave the site within a few seconds. SEO specialists and content managers should therefore always care about user experience as well. And here too, there are plenty of natural parallels between web accessibility and content management best practices.

Add subtitles to your videos

It’s pretty obvious: if you embed a YouTube video on your website without subtitles, people with hearing problems can’t really watch it. But that’s far from the only reason you should use subtitles. We now consume most of the internet on our phones. Often on the train. Maybe while waiting for a friend in a café. Or at work when we take a quick 2-minute break.

In none of these situations can we watch a video with sound without headphones. For all of these people, the video is therefore just as unusable as it is for someone who is deaf. And subtitles are becoming more relevant regardless of location or device: 80% of 18–24-year-olds say they sometimes or always watch series and films with subtitles. If you want people to watch your video, you basically need subtitles nowadays.

Intense animations, flashes, and loud sounds

Whether it’s a flashing video, strobe-like CSS animations, surprising pop-ups, or loud sounds from an autoplay video: these elements can trigger serious episodes for people with epilepsy or PTSD. But even for everyone else, they can quickly become very stressful – and people usually respond to acute, unexpected stress by fleeing, which in this case means closing your site.

Contrast and font size

This is a fundamental aspect of accessible web design. Small fonts or poor contrast between background and text make the site challenging for people with poor eyesight – and for example also for people with dyslexia. But even people with perfect vision have very little tolerance for this. Closing your site and opening a competitor’s is usually 100 times easier than trying to fight through text that’s hard to read.

Error messages

With this practice, you’re not only hurting accessibility, you’re also breaking your conversion path: if a form on your site doesn’t clearly and understandably explain what the user did wrong when submitting it, you have to expect that some people simply won’t submit it. For people using a screen reader, for people with cognitive impairments, or for older, less digitally experienced users, solving the problem may simply not be possible.

Again, you need to assume that users who encounter this problem will simply take their request elsewhere.

How to test your website’s accessibility

I hope it’s clear now why you should regularly ask yourself whether your website is accessible. If you want to test your own website, I recommend running an accessibility scan using Google Lighthouse. All you need is Google Chrome. Just right-click anywhere on your site, select “Inspect”, and then switch to the “Lighthouse” tab.

Lighthouse accessibility report tool

Checking how your website performs with a screen reader is also very easy. On your phone, you can enable screen reader mode on Android and on iPhone with just a few taps.

And if you’re now really fired up about web accessibility, you can dive deeper into the topic with the Web Content Accessibility Guidelines in this detailed resource. If you run into problems analysing or fixing barriers on your site, I’ll be happy to help and make sure that your website is optimised not only for SEO but also for accessibility.

Because web accessibility is a topic very close to my heart, I offer free, no-obligation consulting on this topic.

I’d be happy to hear from you.