Accessibility, with the findings attached.
A statement is worth something only if it names what is still wrong. This one lists the standard, the scripts that test against it, and the four things we have not proven.
Last audited 11 October 2026 · WCAG 2.2 Level AA
One · The standard
What this site is held to
WCAG 2.2 Level AA. That is the level EN 301 549 points at, the harmonised European standard the European Accessibility Act is measured against, and it is the target we build to on this site and on the sites we build for other people. The same work covers WCAG 2.1 Level AA, which is the benchmark United States courts and settlements apply under Title III of the Americans with Disabilities Act, because no technical standard has been written into that law. One standard, two jurisdictions, no separate effort.
WCAG 2.2Two · Status
Partially conformant, self-assessed
After the October 2026 redesign the full audit was run again. Every page passes the automated WCAG 2.2 A and AA rules we can run, at a 320-pixel viewport and at a desktop one, including the 404, and all 27 checks in our own motion, keyboard and structure script pass. Keyboard routes, reduced motion, reflow and focus visibility were checked by hand. Nobody outside fyzno has audited the site, and it has not been tested by a person who uses a screen reader daily. Section Four lists what that leaves open. We say partially conformant because that is what a self-assessment can honestly claim.
Three · Method
How it was checked, and with what
Two scripts in this repository, run against a live build. The first drives axe-core over every route at 390 and 1440 pixels wide with every WCAG 2.2 A and AA rule enabled, including the 2.5.8 target-size rule that axe leaves off by default. The second checks the things this codebase can break invisibly: content stranded behind an animation under prefers-reduced-motion, the keyboard route through the brief, one h1 per page, and the skip link as the first tab stop. By hand on top of that: tab order against the fixed header, reflow at 320 pixels, text at 200 per cent, and the accessibility tree read back on each page. Automated rules cover about a third of the success criteria. The rest is judgement, and judgement is fallible.
Four · Known limits
What we have not proven
No third-party audit and no VPAT. No test session with someone who uses assistive technology as their daily means of access; we read the accessibility tree, which is not the same thing. The particle field behind the home page, the layer names beside it and the outlined wordmark in the footer are decorative and hidden from assistive technology; the same information is in the text of each page. The site publishes no video or audio, so captions and transcripts are untested ground here rather than solved problems. The one kind of PDF it publishes, the Terms and Conditions in English and Dutch, is generated from the same text as the web page, as a tagged PDF with real headings, lists, a document language and the sections as bookmarks. We have not tested those PDFs with a screen reader; the web pages carry the identical text and remain the accessible reference. If you hit something this page does not mention, section Seven is the point of it.
Five · Motion
Reduced motion turns all of it off
The site moves: headlines rise into place, the home page has a particle field that changes shape as you scroll, and scrolling is smoothed. If your system asks for reduced motion, every part of that stops. Text appears straight away, scrolling is your browser's own, the particle field stands still and changes shape without animating, the custom cursor and page transition are switched off, and nothing pins or slides sideways. A script checks on every route that nothing stays hidden when that preference is set. There is no autoplaying video and nothing flashes.
Six · Contrast
Higher contrast and forced colours
If your system asks for more contrast, muted text and the thin dividing lines are made noticeably brighter. In Windows high contrast and other forced-colour modes, the system palette takes over: decorative canvases, the custom cursor and the page transition are removed, and every card and button keeps a visible edge. Body text is held to at least 4.5 to 1 against its background in the default theme, and large headings to at least 3 to 1.
Seven · Report a barrier
Tell us and we will tell you when
Write to info@fyzno.com with the word Accessibility in the subject line, or use the phone number or WhatsApp thread in the footer if mail is the barrier. A signed reply comes back within 48 hours: what we found, whether we can fix it, and by when. If the fix will take longer than that, we send you the content another way in the meantime. That is the part of this that actually matters. Tell us what you were trying to do, on which page, and with what browser and assistive technology if you know it.
Eight · Legal position
Which law applies, and why we published anyway
The European Accessibility Act has applied since 28 June 2025, carried into Dutch law by the Implementatiewet toegankelijkheidsvoorschriften producten en diensten. Enforcement is split by sector; for websites and electronic communications the supervisory authority in the Netherlands is the ACM. Whether this particular site falls inside the Act is arguable, because it sells nothing to consumers and fyzno is small enough for the microenterprise exemption to be in play. We would rather not have that argument. We build sites for organisations that are squarely in scope, so publishing a statement with real findings in it is the only version of this that is worth anything.
Directive (EU) 2019/882Nine · No overlay
There is no accessibility widget on this site
Deliberately. Overlay products that promise conformance from one script tag are widely reported to break the assistive technology they claim to help, and they are the subject of a large share of the accessibility litigation filed each year. They also cannot be installed here without a third-party script, which our Content-Security-Policy blocks and our privacy page says we do not run. The accessible version of this site is this site.
Ten · When this changes
Reviewed with the code, not annually
The audit runs in the same pass as any change that touches layout, motion, or a form, and this page is rewritten when a finding changes. The date at the top of the page is the date of the last audit, not the date of the last edit to the wording. If a claim here is no longer true, that is a defect and we would like to hear about it on the address in section Seven.
Something on this site blocked you? Write to info@fyzno.com, or call +31 85 369 75 22. A signed reply comes back within 48 hours, and the content reaches you another way while the fix is being made.
What the site stores about you is in privacy. What we owe you under an engagement is in the terms.