---

WCAG testing and web accessibility

Your website, app and documents have to work for blind and visually impaired people: for those who use a screen reader, magnification or only a keyboard. I have used a screen reader every day for more than 30 years. I test, advise and build so your digital products hold up in practice, not only on paper.

---

WCAG testing

Automated tools find about a third of the problems that stop a blind user. The rest you only find by using the site the way users do. I do both.

• Manual testing with real assistive technology. JAWS and NVDA on Windows, VoiceOver on Mac and iPhone, TalkBack on Android. Keyboard only. Zoom to 400 percent.
• Automated scanning of every page as a supplement.
• A report you can act on. Every issue with its WCAG criterion, where it is, what it means for the user, and how to fix it. Sorted by severity.
• A walkthrough with your developers, so the fixes are right the first time.
• A retest once you have fixed things, and a statement from me on what was tested, how, and what was found. Publish it if you wish.

---

Advice and documents

• Requirements and law. What WCAG 2.2, EN 301 549, the Web Accessibility Directive and the European Accessibility Act mean for you, and what to do first.
• PDF and documents. I make your PDFs, Word templates and forms readable with a screen reader.
• Usability testing with blind and low-vision users. Honest feedback from people who use the technology every day.
• In from the start. I take part in design and development so accessibility is built in rather than fixed afterwards.

---

Accessible tools built with AI

I am blind, and I build software. I describe what I want, let AI write the code, and test, correct and steer myself. It is called vibecoding, and I use it for clients: prototypes, internal tools and assistive tools the market does not offer because the audience is small. Everything is tested with a screen reader and keyboard along the way, not afterwards. I also run AI workshops for teams.

---

How it works

1. Discovery call. We agree what to test or build, who the users are, and what you need the result for.

2. The work. Testing, advice or development, as agreed.

3. Report and walkthrough. You get the result and a meeting where we go through it.

4. Fixes and retest. You fix, I retest, and you get the statement.