Accessibility
Built to a standard, without an external audit to confirm it
DUN-AI targets WCAG 2.2 Level AA. That target has guided the build, and specific measures are listed below. No independent audit has been carried out, so no conformance is claimed.
An accessibility statement that asserts conformance without an external audit is a claim nobody has checked. This page describes what was done during development and what remains untested. It will be replaced by a formal statement once an independent audit, including testing with assistive technology by people who use it daily, has been completed.
Measures taken
Structure and navigation
- A skip link to the main content on every page
- Semantic landmarks and a single, ordered heading hierarchy
- Navigation regions labelled so they can be distinguished
- The current page marked programmatically, not only visually
- Full keyboard operability with a visible focus indicator
Forms
- Every control has a persistent, associated label
- Guidance is linked to the control rather than placed as placeholder text
- Errors are announced, described in words, and identify the field
- Targets meet a minimum size on touch devices
Content and colour
- Text contrast meets or exceeds the AA threshold throughout
- Colour never carries meaning alone. Every outcome, band and warning also carries a word
- Layout reflows to narrow viewports and tolerates 200% zoom
- Motion preferences are honoured; no animation is essential
- Language and direction are declared on the document
Data presentation
- Figures are presented in real data tables with captions and header cells, not as images or canvas drawings
- Where a visual bar appears, the number beside it carries the same information and the bar is hidden from assistive technology
- Wide tables scroll within their own region, never the whole page
Deliberate design decisions
Two choices were made specifically to reduce accessibility risk rather than to fix it afterwards.
No charting library
Charts are the most common source of inaccessible data presentation, and a textual equivalent maintained beside a chart drifts out of step with it. Presenting the data as a table means there is only one representation, and it is the accessible one.
No custom widgets where a native element exists
Native controls carry keyboard behaviour, focus management and assistive technology support that a re-implementation has to earn back. The interface uses standard elements almost everywhere.
Known gaps
- No testing has been carried out with screen reader users, voice control users or switch access users.
- No formal audit against the full WCAG 2.2 AA success criteria has been performed; checking during development covered the criteria the interface exercises, not all of them.
- Reports rendered for print have not been tested against document accessibility standards, and PDF export is not implemented.
- Only English is provided. No translation or right-to-left presentation has been tested, although the architecture carries language and direction explicitly so it can be.
If something is inaccessible to you
Please tell us through the contact page, describing the page, what you were trying to do and the assistive technology you were using. Reports of this kind are treated as defects, not feedback, and we will tell you what we intend to do and when.