WCAG 2.1 / 2.2 AA Accessible by design Government & procurement

Custom accessible software development

Appfront builds custom web applications and software for government bodies that meet WCAG 2.1/2.2 level AA, the European standard EN 301 549 and the Dutch Temporary Decree on Digital Accessibility of Government (Tijdelijk besluit digitale toegankelijkheid overheid). We build accessibility in from the design stage, covering semantics, contrast, keyboard operation and forms, and support you with the accessibility audit and the accessibility statement. This way, your software demonstrably complies with the law and with the requirements set in tenders.

What is digitally accessible software?

Digitally accessible software is software that everyone can use, including people who use a screen reader, are visually impaired or colour-blind, cannot operate a mouse or have difficulty with fine motor control. For government bodies this is not an extra but a legal obligation: websites and web applications must meet WCAG 2.1 level AA via the European standard EN 301 549, and this must be demonstrable with an accessibility statement. The official explanation can be found at digitoegankelijk.nl.

In practice, it comes down to concrete choices in the software itself: semantic HTML so assistive technology understands the structure, sufficient colour contrast, full keyboard operation, a visible focus indicator, correctly labelled forms with clear error messages, alt text for images and a logical reading and navigation order. Custom software often suits this better than an off-the-shelf package, because with your own software you keep full control over the HTML, the components and the forms, which are precisely the places where accessibility is made or broken.

Appfront builds this accessibility in from the design stage and tests against the WCAG success criteria throughout development. We also provide support with the wider software landscape of municipalities and with public-facing applications such as a citizen portal, where accessibility carries extra weight because every resident must be able to use it.

Legal obligation

The Temporary Decree on Digital Accessibility of Government Bodies (Tijdelijk besluit digitale toegankelijkheid overheid) requires government bodies to make their websites and apps comply with EN 301 549 and WCAG, and to publish an accessibility statement about this. We make sure the software demonstrably meets that obligation.

Accessible by design

Accessibility is built into the components from the very first design, not bolted on as a fix afterwards. Semantics, contrast, keyboard operation and focus are included in every build, so the software stays accessible not only now but also as it continues to evolve.

Ready for procurement

Contracting authorities routinely include WCAG and EN 301 549 as a requirement. We deliver software that complies, plus the technical substantiation and documentation, so you can demonstrate this in the procurement process and in your accessibility statement.

How Appfront builds digitally accessible software

We work with an approach in which accessibility is safeguarded at every step, not only at the end. From mapping your target group and legal requirements through to go-live and ongoing maintenance, we always use the WCAG success criteria and the requirements of EN 301 549 as the benchmark, so the result demonstrably complies.

1
Discovery & requirements

We map out the target group, the processes and the legal requirements: which WCAG level applies, which usage scenarios exist and which data and forms must be accessible.

2
Design

We design the interface and components with accessibility as the starting point: contrast, reading order, focus paths and clear forms, tested against the WCAG guidelines.

3
Build & testing

Implementation with semantic HTML and reusable components, continuously tested with a screen reader, keyboard and automated checks. You see working builds along the way.

4
Statement & maintenance

Controlled go-live, support with the accessibility audit and the accessibility statement, followed by maintenance in which accessibility remains safeguarded with every change.

What building to WCAG standards means in practice

Digital accessibility is not a tick-box but a set of concrete requirements built into the software itself. Below are the areas we focus on throughout design and development, derived from the WCAG success criteria and the EN 301 549 standard.

Semantic structure

Correct HTML with headings, landmarks, lists and buttons that do what they say. This lets a screen reader understand the structure and helps users navigate quickly. Where needed, we supplement it with ARIA, but only when standard semantics fall short.

Contrast and legibility

Text and interface elements have sufficient colour contrast in line with the WCAG requirements, and information is never conveyed by colour alone. Text stays legible when enlarged or resized, so visually impaired users can also use the software comfortably.

Keyboard operation and focus

All functionality can be operated entirely with the keyboard, in a logical order and without keyboard traps. Focus is always visible, so users who don't use a mouse know exactly where they are in the application.

Accessible forms

Forms with explicit labels, clear instructions and understandable, programmatically linked error messages. Requests, reports and registrations therefore remain completable for everyone, which is crucial for public-facing government services.

Alt text and media

Images get appropriate alt text, and decorative images are correctly hidden from assistive technology. For video and audio, we provide captions and text alternatives where needed, so information is never lost.

Testing and statement

We test against the WCAG success criteria using automated checks, screen readers and manual checks, and document the findings. This documentation supports the accessibility audit and the accessibility statement that you publish and update annually.

Which government organisations it applies to

The accessibility obligation applies to the whole of government. Below are a number of organisations and use cases for which accessible web-based software is particularly relevant, because they are used by large, diverse audiences.

Municipalities

Municipalities use a lot of public-facing software: applications, reports, appointments and self-service. This is exactly where everything must be accessible to every resident. We build this as accessible custom software, fitting the broader software landscape of municipalities.

Citizen portals

A citizen portal where residents handle their affairs and track their status, often with login via DigiD. Because the entire public must be able to use it, WCAG conformance here is not optional but a prerequisite.

Water boards and implementing bodies

Water boards and implementing organisations such as DUO, the CBR, the SVB or the UWV offer software that citizens and businesses use to carry out mandatory actions. Accessibility is a legal requirement there and is included in government-wide digitalisation programmes.

Public-facing web portals

Portals for subsidies, permits, access to records and applications that residents and entrepreneurs work with daily. An accessible municipal website and the software behind it together form one accessible chain, from first click to confirmation.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and government integrations

We build digitally accessible software on a modern web stack in which semantic HTML, accessible components and automated accessibility checks are standard. Where government software has to connect to national services, we build the relevant integrations, integrated accessibly into the user interface. Think of logging in via DigiD for citizens, eHerkenning for businesses and displaying messages via MijnOverheid.

For organisations that want to keep their sites and apps in sync with the DigiToegankelijk register, there is our page about a DigiToegankelijk integration.

Semantic HTML5 WCAG 2.1 / 2.2 AA EN 301 549 ARIA where needed Node.js / Python / PHP / .NET React & Vue (accessible components) Design tokens & contrast Keyboard navigation & focus management Screen reader testing axe / Lighthouse audits DigiD integration eHerkenning MijnOverheid Accessibility statement (completion assistant) Automated CI checks GitHub Actions

Why Appfront for accessible software?

Appfront builds custom software for organisations in the Netherlands, including the public sector. We safeguard accessibility from the design stage, so the result demonstrably meets WCAG and EN 301 549, not as a fix after the fact, but as an integral part of the development process.

On every project we write clear documentation and make sure your own team, or a future supplier, can understand and maintain the software. No black box, but transparent code and clear agreements on accessibility, maintenance and further development.

You work with a single point of contact who understands both the technical and the functional side. That keeps communication lines short and speeds up decisions when choices have to be made during the build.

The same obligation applies to mobile apps, but with different points of attention; see our page on digitally accessible apps. For public-facing applications, we look at the citizen portal and the municipal website as one coherent whole.

  • Accessibility by design, tested against WCAG 2.1/2.2 AA
  • Familiar with EN 301 549 and the Dutch Temporary Decree on digital accessibility
  • Semantic HTML, keyboard operation and focus management as standard
  • Support with accessibility audits and accessibility statements
  • Experience with government integrations such as DigiD and eHerkenning
  • Clear documentation that your team can read and maintain
  • A single point of contact, no passing you between account managers
  • Accessibility safeguarded with every iteration, not just once

Security, privacy and accessibility

Government software almost always processes personal data. That is why Appfront builds according to data minimisation and least privilege, with appropriate logging and encryption. For information security, we align with the Baseline Informatiebeveiliging Overheid (BIO), the mandatory security framework for the Dutch government.

Accessibility and privacy go hand in hand here: we document the data flows so that your record of processing activities is complete and you can demonstrably comply with the GDPR, and we record the accessibility testing as supporting evidence for your accessibility statement. The official accessibility frameworks can be found at digitoegankelijk.nl.

Would you like to discuss this for a specific project? Feel free to get in touch.

  • GDPR-compliant data processing and minimisation
  • Alignment with the Baseline Informatiebeveiliging Overheid (BIO)
  • WCAG 2.1/2.2 AA and EN 301 549 as a design requirement
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least-privilege principles
  • Audit logs with traceable data flows
  • Supporting evidence for the accessibility statement
  • Documentation for your record of processing activities

Frequently asked questions about accessible software

Answers to the questions we get most often about WCAG, the Temporary Decree and accessible government software.

The Temporary Decree on digital accessibility for government bodies requires public sector organisations to make their websites and mobile apps accessible and to keep them that way. They do this by complying with the European standard EN 301 549, which refers to the Web Content Accessibility Guidelines (WCAG). You must also publish an accessibility statement for each website or app. The decree has applied since 2018 and was incorporated into the Wet digitale overheid (Digital Government Act) in 2023. The current, official explanation is available at digitoegankelijk.nl.

The obligation applies to public bodies: municipalities, water boards, ministries, central government and implementing organisations such as the Tax Administration, DUO, the CBR, the SVB, the UWV, the RDW and the CAK. Their websites, web applications and mobile apps are also covered. Some media organisations are exempt. If you build software, or get software built, for one of these organisations, it must meet the accessibility requirements.

For government bodies, WCAG Level A and AA are mandatory, via the EN 301 549 standard. In practice, we work to WCAG 2.1 Level AA and take the newer WCAG 2.2 success criteria into account, so your software is also prepared for any future tightening of the standard. Level AAA is not a legal requirement, but we apply specific AAA criteria where they make sense for your audience.

Accessibility by design means we build accessibility in from the design stage rather than fixing it afterwards. In practice: semantic HTML, sufficient colour contrast, full keyboard operability, visible focus indicators, correctly labelled forms with clear error messages, alt text for images, and a logical heading and reading order. This is more sustainable and cheaper than retrofitting accessibility onto an existing application that never took it into account.

Yes. We build the software so that it demonstrably meets WCAG, and we support you in drawing up the accessibility statement via the Dutch government's online statement tool, and in arranging an accessibility audit. The link to the audit belongs in the statement, which you publish and update every year. We provide the technical substantiation and documentation so that the process runs smoothly.

Because the legal obligation lies with the government organisation itself, contracting authorities routinely include WCAG and EN 301 549 as a requirement or award criterion in tenders for software and websites. A supplier that can demonstrate it has built accessibility into its development process reduces the risk for the client. Appfront delivers compliant software, along with the supporting evidence to demonstrate this in the tender.

This page covers accessible web-based software and web applications for government bodies. The same legal obligation applies to mobile apps, but with partly different technical considerations. We have a separate page on digitally accessible apps for that. We're happy to look with you at which route suits your channel and audience.

Then we first map out where the problems lie, based on WCAG success criteria and the requirements of EN 301 549. We then draw up a prioritisation: critical barriers for screen reader and keyboard users first, then the remaining criteria. We can make individual improvements or include accessibility in a broader programme of further development, and we provide the documentation for your accessibility statement.

Ready to build accessible software?

Tell us which software you want to bring into line with WCAG and the Digital Accessibility Decree, or which new system you want to build — we're happy to advise on design, testing and the accessibility statement. A no-obligation initial conversation will quickly give you a clear picture of the possibilities. Get in touch to arrange a meeting.

Edit content