Custom accessible software development
Appfront builds bespoke web applications and software for government bodies that comply with WCAG 2.1/2.2 Level AA, the European standard EN 301 549 and the Dutch Temporary Decree on Digital Accessibility of Government. We build accessibility in from the design stage, covering semantics, contrast, keyboard operation and forms, and we support you with accessibility audits and your accessibility statement. This way, your software demonstrably meets legal requirements and the standards set in public tenders.
What is digitally accessible software?
Digitally accessible software is software that everyone can use, including people who use screen readers, have low vision or colour blindness, cannot use a mouse, or find fine motor control difficult. For government bodies, this is not an optional extra but a legal obligation: websites and web applications must comply with WCAG 2.1 Level AA through the European standard EN 301 549, and this must be demonstrable with an accessibility statement. The official guidance is available at digitoegankelijk.nl.
In practice, this comes down to concrete choices in the software itself: semantic HTML so assistive technology can understand 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. Bespoke development often suits this better than an off-the-shelf package, because with your own software you retain full control over the HTML, the components and the forms: precisely the places where accessibility is either achieved or broken.
Appfront builds this accessibility into the design from the start and tests against the WCAG success criteria throughout development. We also support with the broader software landscape of municipalities and with public-facing applications such as a citizen portal, where accessibility matters even more because every resident needs to be able to use it.
Legal obligation
The Temporary Decree on Digital Accessibility of Government requires government bodies to ensure 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 fulfils that obligation.
Accessible by design
Accessibility is built into the components from the very first design, rather than being repaired afterwards. Semantics, contrast, keyboard operation and focus are considered in every build, so the software remains accessible not only now but also as it is further developed.
Ready for tender
Contracting authorities routinely include WCAG and EN 301 549 as a requirement. We deliver software that complies, along with the technical justification and documentation, so you can demonstrate this in the tender and in your accessibility statement.
How Appfront builds digitally accessible software
We follow an approach that builds accessibility into every step, rather than adding it at the end. From mapping your target users and legal requirements through to go-live and ongoing management, we use the WCAG success criteria and the requirements of EN 301 549 as our benchmark, so the outcome demonstrably meets the standard.
We map out your target users, processes and legal requirements: which WCAG level applies, which usage scenarios exist, and which data and forms must be accessible.
We design the interface and components with accessibility as the starting point: contrast, reading order, focus paths and clear forms, all checked against the WCAG guidelines.
Implementation using semantic HTML and reusable components, tested continuously with screen readers, keyboard navigation and automated checks. You see working builds along the way.
Controlled go-live, support with the accessibility audit and the accessibility statement, followed by maintenance that keeps accessibility assured with every change.
What building to WCAG standards means in practice
Digital accessibility is not a tick-box exercise but a set of concrete requirements built into the software itself. Below are the areas we consistently focus on during 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 allows a screen reader to understand the structure and lets users navigate quickly. Where necessary we add ARIA, but only when the standard semantics fall short.
Contrast & readability
Text and interface elements have sufficient colour contrast in line with WCAG requirements, and information is never conveyed by colour alone. Text remains legible when enlarged or resized, so partially sighted users can use the software comfortably.
Keyboard operation & focus
All functionality can be operated fully by keyboard, in a logical order and without keyboard traps. Focus is always visible, so users who do not use a mouse know exactly where they are in the application.
Accessible forms
Forms with explicit labels, clear instructions and easy-to-understand error messages linked programmatically to their fields. Applications, reports and sign-ups stay accessible to everyone, which is essential for public-facing government services.
Alt text & media
Images receive 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 & statement
We test using automated checks, screen readers and manual reviews against the WCAG success criteria, and document the findings. That documentation supports the accessibility audit and the accessibility statement you publish and update annually.
For which government organisations
The accessibility obligation applies across the whole of government. Below are some organisations and applications for which accessible web-based software is particularly relevant, as they are used by large and diverse audiences.
Municipalities
Municipalities use a lot of public-facing software: applications, reports, appointments and self-service. That is exactly where everything must be accessible to every resident. We build this as accessible custom software that fits within the broader software landscape of municipalities.
Citizen portals
A citizen portal where residents handle their affairs and track their status, often signing in via DigiD. Because the entire public must be able to use it, WCAG conformance here is not an option but a prerequisite.
Water boards & implementation
Water boards and implementing bodies such as DUO, CBR, SVB and UWV provide software through which citizens and businesses carry out mandatory tasks. Accessibility is legally required there and is taken into account in government-wide digitalisation programmes.
Public-facing web portals
Portals for grants, permits, record access and applications that residents and businesses use every day. An accessible X municipality website and the software behind it together form one accessible chain, from the first click to the confirmation.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore 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 needs to connect to national services, we handle the relevant integrations, built accessibly into the user interface. Think of signing in with DigiD for citizens, eHerkenning for businesses and displaying messages via MijnOverheid.
For organisations that want to keep their sites and apps in line with the DigiToegankelijk register, see our page on building a DigiToegankelijk integration.
Why choose Appfront for digitally accessible software?
Appfront builds bespoke software for organisations in the Netherlands, including the public sector. We ensure accessibility from the design stage, so the outcome demonstrably meets WCAG and EN 301 549. It is not a retrofit but 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 manage the software. No black box, but transparent code and clear agreements on accessibility, maintenance and further development.
You work with a dedicated point of contact who understands both the technical and functional sides. This keeps lines of communication short and speeds up decisions when choices need to be made during the build.
The same obligation applies to mobile apps, with different points of attention; see our page on digitally accessible apps. For public-facing applications, we look at the citizen portal and the X municipality website as one connected whole.
- Accessibility by design, tested against WCAG 2.1/2.2 AA
- Familiar with EN 301 549 and the Dutch Temporary Decision on Digital Accessibility
- Semantic HTML, keyboard operation and focus management as standard
- Support with accessibility audits and the accessibility statement
- Experience with government integrations such as DigiD and eHerkenning
- Clear documentation your team can read and manage
- A fixed point of contact, no account managers passed around
- Accessibility safeguarded with every further development, not just once
Security, privacy and accessibility
Government software almost always processes personal data. Appfront therefore builds to data minimisation and least privilege, with appropriate logging and encryption. For information security we align with the Baseline Informatiebeveiliging Overheid (BIO), the mandatory standards 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 demonstrably comply with the GDPR, and we record the accessibility testing as evidence for your accessibility statement. The official frameworks for accessibility are published at digitoegankelijk.nl.
Would you like to discuss this for a specific project? Feel free to contact us.
- GDPR-compliant data processing and data 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
- Evidence for the accessibility statement
- Documentation for your record of processing activities
Frequently asked questions about accessible software
Answers to the questions we are asked most often about WCAG, the Temporary Decree and accessible government software.
The Temporary Decree on Digital Accessibility for Government requires public sector organisations to make their websites and mobile apps accessible and to keep them that way. This is done 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 been in force since 2018 and was incorporated into the Digital Government Act in 2023. The up-to-date, official guidance is available on digitoegankelijk.nl.
The obligation applies to public sector bodies: municipalities, water boards, ministries, the 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 or commission software for any of these organisations, it must meet the accessibility requirements.
For government bodies, WCAG level A and AA is the mandatory level, 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 prepared should the standard be tightened in future. Level AAA is not a legal requirement, but we apply specific AAA criteria where they are relevant to your audience.
Accessibility by design means we consider accessibility from the design stage onwards, rather than fixing it afterwards. In practice, this means 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 structure and reading order. This is more sustainable and cheaper than an accessibility overhaul of an existing application that did not take it into account.
Yes. We build the software so that it demonstrably meets WCAG, and we support you in drafting the accessibility statement using the statement assistant, as well as in commissioning an accessibility audit. The link to the audit belongs in the statement, which you publish and update annually. We provide the technical justification and documentation so that this process runs smoothly.
Because the legal obligation rests with the public body 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 has demonstrably embedded accessibility in its development process reduces the risk for the client. Appfront delivers software that complies, along with the supporting evidence needed to demonstrate this in a tender.
This page covers digitally accessible web-based software and web applications for government bodies. The same legal requirement applies to mobile apps, but with partly different technical considerations. We have a separate page on digitally accessible apps for that. We are happy to work with you to determine which route suits your channel and audience.
We start by mapping out where the barriers lie, based on the WCAG success criteria and the requirements of EN 301 549. Next, we set priorities: critical blockers for screen reader and keyboard users come first, followed by the remaining criteria. You can choose to implement targeted fixes or fold accessibility into a broader development project, and we will deliver the documentation you need for your accessibility statement.
Ready to build digitally accessible software?
Tell us which software you want to make compliant with WCAG and the Temporary Digital Accessibility Decision, or which new system you want to build. We are happy to help with design, testing and the accessibility statement. A no-obligation first conversation will quickly give you a clear picture of the options. Get in touch to arrange a meeting.