web accessibility from Tilburg

Accessible website (WCAG)

A website that works for everyone, including with an impairment or assistive software. Schwung builds accessibility to WCAG in from the foundation, not as a check afterwards. That's often legally required, and it makes your site faster and more findable.

What is an accessible website (WCAG)?

An accessible website is usable by everyone, including people with a visual, motor, auditory or cognitive impairment and those using a screen reader or other aid. The international standard is WCAG, laid down in Europe in the EN 301 549 norm.

At Schwung accessibility isn't an afterthought but a starting point. We design and build to WCAG level AA from the ground up, so you don't have to repair afterwards. It pays off: an accessible site is clearer, faster and more findable for people and search engines alike.

01: Design

Accessible design from the ground up

Not afterwards, but up front

Accessibility starts in the design: sufficient colour contrast, legible typography, clear focus states and a logical structure. By taking this into account up front, we avoid expensive repairs later.

  • Colour contrast & legibility
  • Keyboard & focus navigation
  • Clear, logical structure
02: Build

WCAG-compliant, semantic code

Works with assistive software

Under the hood we build semantic, clean code that screen readers and other aids understand. Correct headings, labels, alt text and ARIA where needed, so the site works as intended, for everyone.

  • Semantic HTML & correct headings
  • Alt text, labels & ARIA
  • Tested screen-reader experience
03: Law & standard

Meeting WCAG, EN 301 549 & the EAA

Accountable and demonstrable

For governments the accessibility obligation has applied for some time; since 28 June 2025 the European Accessibility Act extends it to many private services. We make sure you demonstrably meet WCAG level AA, and help with an accessibility statement.

  • WCAG level AA & EN 301 549
  • European Accessibility Act (EAA)
  • Accessibility statement
04: Audit & remediation

Make an existing site accessible

Measure, fix, safeguard

Already have a site? We test it against WCAG, record the issues and fix them in a targeted way. With a large backlog, a fresh build that's accessible from the ground up is often cheaper than endless repairs. We'll tell you honestly what makes sense in your case.

  • Accessibility audit (WCAG)
  • Targeted remediation & prioritisation
  • Safeguarding during further development
Accessibility · WCAG 2.1

The four WCAG principles as our compass.

We build every accessible site on the four WCAG principles: perceivable, operable, understandable and robust. For the municipal programme Duurzaam Hilvarenbeek, for instance, we already laid a WCAG-ready foundation with these principles as our compass; the accessibility process itself, the audit toward level AA, starts there in a later phase.

01 Perceivable Alt text, sufficient colour contrast, correct heading structure.
02 Operable Keyboard navigation, clear buttons and links, predictable behaviour.
03 Understandable Clear labels, consistent controls, predictable interactions.
04 Robust Clean semantic HTML, ARIA attributes, screen-reader friendly.
The Duurzaam Hilvarenbeek website
Brand identity & development

Duurzaam Hilvarenbeek

Brand identity for a multi-year municipal programme

Step by step toward accessibility

Accessibility isn't an on-off switch but a growth path. Full WCAG level AA is an ambitious goal, especially at the content level: consistent heading structures, alt text, plain language, sufficient contrast and transcripts under videos. We work toward it in phases, biggest gains first.

Advice

Five steps that keep it manageable

From quick wins to a full growth path
  • Start with quick wins. Use what's already built into browsers and operating systems, such as read-aloud and zoom functions, so you don't invest twice.
  • Set a growth path. Grow toward level AA in phases rather than trying to reach everything at once. That keeps the implementation manageable.
  • Involve content managers early. Train editors in accessible writing and image use. Technical measures have little effect if the content doesn't keep up.
  • Test with real users. Have the site tested by people with a disability. That yields insights a checklist or tool never fully gives.
  • Document choices and exceptions. Record why you make certain choices. It shows awareness and helps with audits and accountability.

How the legal process works

For government organisations, digital accessibility is regulated by law. You publish an accessibility statement (toegankelijkheidsverklaring) and demonstrate that you're working on improvement. We guide that process, from baseline to statement.

  1. Publish an accessibility statement. That brings you within the legal framework (status C, valid for six months).
  2. Have an accessibility audit carried out within six months of launch. With the audit and a concrete improvement plan your status moves to B; a full assessment gives status A or B and is valid for three years.
  3. Keep the statement current. Update it at least once a year with visible progress, such as issues resolved.

Statuses A, B and C count as 'compliant with the law', D and E do not. In practice most government bodies are in the assessment-and-optimisation phase: a statement and an audit exist, but the process is still ongoing. That's exactly where we think along.

Frequently asked questions about accessible websites

What is an accessible website?

An accessible website is usable by everyone, including people with a visual, motor, auditory or cognitive impairment and those using assistive software such as a screen reader. The standard for this is WCAG (Web Content Accessibility Guidelines), laid down in Europe in the EN 301 549 norm.

Is an accessible website legally required?

For governments and public organisations the requirement has applied for some time (based on EN 301 549). Since 28 June 2025 the European Accessibility Act extends that requirement to many private services, such as webshops, banking and ticketing. Not sure whether it applies to you? We're happy to take a look with you.

Which level do I need, A, AA or AAA?

In practice WCAG level AA is the standard you must meet; that's also the level the legislation follows. Level AAA is an aspiration for specific elements, not a realistic requirement for an entire site. We design and build to AA as standard.

Can you make our existing website accessible?

Yes. We audit your current site, record where it falls short against WCAG and fix that in a targeted way. With a substantial backlog, a fresh build that's accessible from the ground up is often cheaper than endless repairs. We'll tell you honestly what makes sense in your case.

Does accessibility also make my site more findable?

Yes. Many accessibility measures, clear structure, good headings, alt text, speed and semantic code, are exactly what search engines and AI systems need to understand your content. An accessible site is therefore usually faster and more findable.

Arjan Hoogervorst, developer at Schwung

Call Arjan.

A new accessible site, or making your current site WCAG-proof? Arjan will think along on approach, audit and tech.