Accessibility at Audact

1. Formal WCAG 2.2 AA audit roadmap

Item
Target completion
Status
Q4 2026
Item
Vendor shortlist
Status
Shortlist: Deque · Level Access · Knowability. Not yet selected, not yet engaged.
Item
Budget
Status
€3,000 - €8,000
Item
Scope
Status
10-15 representative page sample + full conformance audit

Formal WCAG 2.2 AA audit roadmap
Item	Status
Target completion	Q4 2026
Vendor shortlist	Shortlist: Deque · Level Access · Knowability. Not yet selected, not yet engaged.
Budget	€3,000 - €8,000
Scope	10-15 representative page sample + full conformance audit

2. Current commitments, and where each one actually stands

Each row names the measurement it rests on. A commitment without one is a promise, and this is not the page for promises.

Control
Semantic HTML, landmark regions, and a skip-to-content link on every page
Status
Verified on every page
Ground
Every page carries one main element with the skip-link target, one h1, and a header, navigation and footer. Verified by measurement on nine pages.
Control
Keyboard operation with a visible focus indicator on every operable element
Status
Verified on 441 controls
Ground
441 focusable elements across nine pages, each measured before and after receiving focus. Every one changes appearance.
Control
Colour contrast at WCAG AA for body text and interactive elements
Status
Verified by measurement, not by audit; re-run pending
Ground
176 English pages at 1440 px, plus 17 pages in English, German and Dutch at 1440 and 390 px, each text measured against the background actually rendered behind it. No text below its threshold. The method was proved on an injected line at 1.52:1, which it flagged. Corrected on 28 August 2026: that run read the colour set on the text and not the colour an enclosing opacity layer composites it into, so it reported nothing on /en/demos where Lighthouse measured 1.87:1. An injected line carries no opacity above it, which is why the positive control could not catch this. The three affected rows are fixed and the script now folds in the opacity of every ancestor; the page count above dates from before that correction and is due a re-run.
Control
Reduced motion: animation respects prefers-reduced-motion
Status
Verified for the animation that exists
Ground
Counted in pixels, because a computed style does not see a canvas. Without the preference, two of the five canvases on the home page pass through 5 and 7 distinct states in 1.8 seconds; under reduce, every canvas shows 2 — blank, then final. CSS animations and transitions are cut to 0.01 ms by the same query.
Control
Every form field has an associated label
Status
Verified on both form variants
Ground
Measured in the browser on the application form and the enterprise form: every rendered field resolves to a label element or an ARIA label. The no-JavaScript variant wraps each field in its own label.
Control
Errors and confirmations are announced to assistive technology
Status
Verified in the application form
Ground
In the agency-application form an error renders with role=alert and aria-live=assertive, and the confirmation with role=status and aria-live=polite. The formal statement said these were still being added; they are present, and that statement has been corrected.
Control
The field that caused an error is marked as invalid and points at the message
Status
In remediation
Ground
The enterprise contact form does not do this: submitting /for-enterprise at 1440 px with its required fields empty leaves none of its seven fields carrying aria-invalid and none pointing at a message with aria-describedby. This row named the agency-application form until 27 August 2026; that form was fixed later the same day and now marks all three of its required fields, so the gap moved rather than closed. The measurement is the same read-out in both places, which is what makes this a gap and not a house style.
Control
Autocomplete hints on fields that ask for information about the person
Status
Partially conformant
Ground
The text fields carry an autocomplete hint: the agency name, the email address and, on the enterprise form, the contact name. The select lists carry none, and the no-JavaScript variant of the application form carries none at all.
Control
Expandable components report their expanded or collapsed state
Status
Verified in Chromium; not tested with a screen reader
Ground
The mobile-menu button goes from aria-expanded=false to true when activated; the navigation groups and the optional-fields toggle carry aria-expanded with aria-controls. Whether every screen reader announces it has not been tested.
Control
Third-party audit against WCAG 2.2 AA
Status
Planned, no vendor engaged
Ground
Q4 2026. No auditor engaged; see section 1.

Accessibility controls, their status, and the measurement behind each
Control	Status	Ground
Semantic HTML, landmark regions, and a skip-to-content link on every page	Verified on every page	Every page carries one main element with the skip-link target, one h1, and a header, navigation and footer. Verified by measurement on nine pages.
Keyboard operation with a visible focus indicator on every operable element	Verified on 441 controls	441 focusable elements across nine pages, each measured before and after receiving focus. Every one changes appearance.
Colour contrast at WCAG AA for body text and interactive elements	Verified by measurement, not by audit; re-run pending	176 English pages at 1440 px, plus 17 pages in English, German and Dutch at 1440 and 390 px, each text measured against the background actually rendered behind it. No text below its threshold. The method was proved on an injected line at 1.52:1, which it flagged. Corrected on 28 August 2026: that run read the colour set on the text and not the colour an enclosing opacity layer composites it into, so it reported nothing on /en/demos where Lighthouse measured 1.87:1. An injected line carries no opacity above it, which is why the positive control could not catch this. The three affected rows are fixed and the script now folds in the opacity of every ancestor; the page count above dates from before that correction and is due a re-run.
Reduced motion: animation respects prefers-reduced-motion	Verified for the animation that exists	Counted in pixels, because a computed style does not see a canvas. Without the preference, two of the five canvases on the home page pass through 5 and 7 distinct states in 1.8 seconds; under reduce, every canvas shows 2 — blank, then final. CSS animations and transitions are cut to 0.01 ms by the same query.
Every form field has an associated label	Verified on both form variants	Measured in the browser on the application form and the enterprise form: every rendered field resolves to a label element or an ARIA label. The no-JavaScript variant wraps each field in its own label.
Errors and confirmations are announced to assistive technology	Verified in the application form	In the agency-application form an error renders with role=alert and aria-live=assertive, and the confirmation with role=status and aria-live=polite. The formal statement said these were still being added; they are present, and that statement has been corrected.
The field that caused an error is marked as invalid and points at the message	In remediation	The enterprise contact form does not do this: submitting /for-enterprise at 1440 px with its required fields empty leaves none of its seven fields carrying aria-invalid and none pointing at a message with aria-describedby. This row named the agency-application form until 27 August 2026; that form was fixed later the same day and now marks all three of its required fields, so the gap moved rather than closed. The measurement is the same read-out in both places, which is what makes this a gap and not a house style.
Autocomplete hints on fields that ask for information about the person	Partially conformant	The text fields carry an autocomplete hint: the agency name, the email address and, on the enterprise form, the contact name. The select lists carry none, and the no-JavaScript variant of the application form carries none at all.
Expandable components report their expanded or collapsed state	Verified in Chromium; not tested with a screen reader	The mobile-menu button goes from aria-expanded=false to true when activated; the navigation groups and the optional-fields toggle carry aria-expanded with aria-controls. Whether every screen reader announces it has not been tested.
Third-party audit against WCAG 2.2 AA	Planned, no vendor engaged	Q4 2026. No auditor engaged; see section 1.

Every "verified" above is a measurement, not a certification. The measurements were taken on 27 August 2026 on the marketing site at 1440 and 390 px in English, German and Dutch. They do not cover the platform dashboard, and they do not separately cover the seven locales that fall back to English. The formal status of this site is the one recorded in the accessibility statement: partially conformant with WCAG 2.1 level AA.

3. Contact

Accessibility feedback, known issues, and requests for alternative formats: accessibility@audact.ai. We aim to respond within 10 business days.