Skip to main content
Jasper Bloem

Services — Accessibility

WCAG accessibility for your website

More and more organizations need to make their website accessible under WCAG 2.2, from municipalities and healthcare providers to businesses working with government clients. I audit your site, fix the technical issues (color contrast, keyboard navigation, forms, alt text, focus order) and help draft an accessibility statement where needed. Not a checkbox exercise, but a site that genuinely works for everyone who uses it.

Why WCAG accessibility

01

Starts with a concrete audit

I go through your site manually with a keyboard and screen reader, not just an automated scan. Tools like axe or Lighthouse only catch part of the WCAG issues on their own.

02

Technical fixes, not just a report

Color contrast, focus states, ARIA labels, form validation, heading structure: I implement the fixes myself in the code, instead of handing over a list of findings your team still has to act on.

03

Understanding of the legal side

For government bodies and many (semi-)public organizations, WCAG 2.2 AA is a legal requirement in the Netherlands. I also help draft and publish the accompanying accessibility statement.

04

Stays fixed after delivery

Accessibility isn't a one-time check: new content and components introduce new issues. Where useful, I build in checks (linting, contrast rules in the design system) to help keep it that way.

What I build

  • WCAG 2.2 AA audit, manual with keyboard and screen reader
  • Fixing color contrast, focus states and keyboard navigation
  • Semantic HTML, ARIA labels and heading structure
  • Accessible forms and error messages
  • Drafting and publishing an accessibility statement
  • Embedding accessibility into new features and content going forward

Sound like your project?

From first conversation to launch, I'd love to think along on your project around WCAG accessibility.

Tell me about your project

Frequently asked questions

Good Questions

Setting expectations before we start, with a real process and honest answers.

For government bodies and many public organizations, yes, under Dutch digital accessibility regulation. For commercial businesses it isn't always a legal requirement yet, but the European Accessibility Act extends the obligation to more private sectors from 2025, and clients increasingly ask for it in tenders regardless.

In practice, WCAG 2.2 AA is the standard used by regulation and most tenders. AAA is stricter and not realistic or necessary for most sites, so I target AA by default unless you specifically need AAA.

Yes, an audit is platform-independent. I test the site as it currently runs and then implement fixes in whatever platform you already use: WordPress, Laravel, Next.js or something else.

Contact

Say Hello

Got a project in mind? Tell me a bit about it and I'll get back to you within a day.