Usable by all. Better for business.
Around one in five people lives with a permanent or temporary disability. Accessibility widens your audience and improves satisfaction - and since the European Accessibility Act it's also required. A green Lighthouse score alone isn't enough, as we learned on our own website.
- From automated analysis (Lighthouse & axe) to a real screen-reader test with a blind user.
- How we honestly raised our accessibility score from 82 to 91 - and why the last points are the hardest.
- Three concrete findings that no automated test would have caught.
Tested with a blind user (JAWS screen reader) · WCAG 2.1 AA · guided by a certified UX designer
The whitepaper is available in German only.
Shall we get in touch?
No newsletter, no ads. We'd like a personal, one-to-one conversation about your projects, your challenges, and whether we could work together.
The process in six steps
From automated scan to a test with a blind user - condensed in the whitepaper.
-
Starting point
Understand project, audience & goal
-
Automated analysis
Lighthouse & axe
-
Prioritisation
By impact & effort
-
Screen-reader test
With a blind user
-
Scope & execution
Run real flows
-
Results
Fix the findings
We don't just talk about accessibility - we test it.
For our own website we asked a blind user to test us with the JAWS screen reader - someone who has worked with it daily for over 20 years. A green score doesn't tell you whether a site is genuinely usable. That's exactly the gap we documented, self-critically.
Navigation & focus
in progressThe English header claim was marked up as a heading and broke the reading flow for the screen reader. As a first step we tagged it correctly with lang="en" - the full fix is in progress.
Contact-form focus
fixedWhen toggling, focus jumped back to the top of the page and required fields were marked only visually. Now every field is clearly labelled via aria-label - with autocomplete and fillable without guessing.
Language switcher
fixedThe language switcher was hard to find. We reworked it: the current and available languages are now announced clearly, with extra aria-labels per component.
A single test doesn't replace a full audit. But it pinpoints where score and reality diverge - and delivers the most valuable insights first.
Ready to reach more people?
Get the whitepaper and see what an honest accessibility process looks like in practice.
Download whitepaperPrefer to write to us directly?
Let's Build Something Great Together
Have a question or want to discuss a project? We'd love to hear from you. Fill out the form below and we'll get back to you as soon as possible.
You can also reach us directly at [email protected]