A website accessible to blind people
my site’s accessibility score in PageSpeed
In short
A blind person uses a website through a screen reader, which reads its content aloud. The screen reader only works well when the site is written properly in code. Below I describe what that takes, how to check your own site in a few minutes, and why “accessibility widget” overlays do not solve it.
Since October I build every site to WCAG 2.1 level AA. It is the international web accessibility standard, the same one European Union regulations refer to. It is included in the price of every website package, not an extra.
How a blind person uses a website
On a computer, most often with the free NVDA screen reader; on an iPhone, with the built-in VoiceOver. The screen reader does not see how the page looks. It reads what is in the code: headings, image descriptions, the names of buttons and form fields. The user jumps between headings like a table of contents and moves around the page with the Tab key or with gestures.
That is why a site can look great and still be completely unusable for that person. A button showing only a basket icon with no description is read out as just “button”. A form field without a label is read as “edit text”, with no hint whether it wants a name or a phone number.
What the code needs
- Image descriptions. Every photo that carries information has alternative text, e.g. “Treatment room with a dental chair”. Decorative images get an empty description so the screen reader skips them.
- Headings in order. One main title, with subheadings below it that do not skip levels. This outline is how a blind person navigates.
- Button names. Carousel arrows, the menu button and social media icons have a description the screen reader can read.
- Form field labels. Every field has a name attached, and error or “message sent” notices are announced by the screen reader on their own.
- Keyboard use. You can go through the whole page with the Tab key, you can always see where you are, and the first Tab offers a “Skip to content” link so you do not have to go through the whole menu every time.
- Contrast. Regular text has a contrast ratio with its background of at least 4.5 to 1, large text 3 to 1. This also helps people with low vision and anyone reading in sunlight.
- Motion under control. Animations and carousels can be paused, and the site respects the “reduce motion” setting on the phone.
Why not an accessibility widget
Online you will easily find overlays that add an icon with a menu to your site: enlarge text, change contrast, read aloud. They are added with a single script, so they are tempting. The problem is that they do not fix the code. An image without a description still has none, and a field without a label still has none. Blind people have their own screen readers, set up the way they like, and the overlay often gets in their way. In the United States, companies using such overlays have been sued for lack of accessibility.
tfagency.pl also has an accessibility switch, the icon with a figure in the header. It reduces motion, darkens and enlarges text, and underlines links. To be honest about who it helps: people with low vision and those bothered by animation. What helps a blind person is the site’s code, not the switch.
How to check your own site in a few minutes
- Keyboard. Open the site on a computer, put the mouse aside and press Tab. Can you see where you are? Can you reach the menu, the phone number and the form?
- VoiceOver on an iPhone. You turn it on in Settings, under Accessibility. Slide your finger across the screen and listen to what the phone reads for photos and buttons. Before you turn it on, check how to turn it off, because it changes how gestures work.
- PageSpeed Insights. This free Google tool shows an “Accessibility” score from 0 to 100 and a list of specific issues. My site scores 100 there.
A score of 100 is a good sign, not proof. An automated test catches only some problems: it checks whether an image has a description, but not whether the description makes sense. That is why the keyboard and screen reader test matters more than the number.
What about the law?
Since 28 June 2025, Poland has had rules implementing the EU’s European Accessibility Act. They cover selected products and services, including online shops, and microenterprises providing services are exempt. Whether they apply to your business is a question for a lawyer or the official guidance, because I do not give legal advice. I build accessible sites whether the law requires it or not.
If you would like me to look at your current site from this angle, get in touch. I will tell you what can be fixed in the existing code and what would need a rebuild.