Accessibility statement
This site conforms to WCAG 2.2 Level AA
We build accessible publications for a living — it would be a poor advertisement if the site selling that work could not be used with a keyboard. This page sets out what we claim, how it was checked, and what to do if you find something we missed.
The claim
Conformance status
| Item | Detail |
|---|---|
| Standard | Web Content Accessibility Guidelines (WCAG) 2.2, www.w3.org/TR/WCAG22 |
| Conformance level | Level AA |
| Scope | All pages published under dmr.pub |
| Basis of claim | Self-assessment by DMI Systems, not yet a third-party audit |
| Technologies relied upon | HTML, CSS, SVG and JavaScript. The site is fully usable with JavaScript disabled, apart from the navigation menus, which fall back to their section links. |
| Date of this statement | 14 September 2026 |
| Related standards | The measures below also address EN 301 549 and Section 508 requirements that map to WCAG 2.2 AA |
A self-assessment is not an audit
This claim rests on our own testing, described below. A formal, defensible accessibility conformance report — an ACR or VPAT of the kind a state adoption team or a legal reviewer will accept — needs independent evaluation. That work is done by the group's accessibility practice at A11Y – NIMAS Master, and we will publish one for this site.
Measures taken
What was built in
Perceivable
- Contrast measured, not estimated
- Every text and background pair was computed. Body text clears 4.5:1 and large text 3:1 throughout. The secondary blue was darkened from the old brand value because white text on it reached only 4.1:1.
- Interface boundaries at 3:1
- Form field borders, card edges and the coloured rules that identify each component clear 1.4.11 Non-text Contrast.
- Structure carries meaning
- Real headings in order, description lists for term-and-definition pairs, table headers with scope, and captions on every data table.
- Images described or hidden
- Meaningful images carry alt text; decorative marks and icons are hidden from assistive technology rather than announced as noise.
- Reflows to 320px
- No horizontal scrolling of the page at 320 CSS px. Wide tables and code samples scroll inside their own containers.
Operable, understandable, robust
- Keyboard throughout
- Every control is reachable and operable by keyboard, with no traps. Menus open on focus and close on Escape or a click outside.
- Focus you can see, and see past
- A 3 px focus ring that switches between dark and light so it is visible on every band — and scroll padding so the sticky header never hides the focused control (2.4.11, new in 2.2).
- Targets of at least 24 px
- Menu carets, footer links and form controls meet 2.5.8 Target Size, new in 2.2.
- No dragging, no cognitive tests
- Nothing on this site requires a drag gesture (2.5.7) and there is no sign-in, so no accessible-authentication burden (3.3.8).
- Help in the same place
- Contact details sit in the same position on every page (3.2.6), and the skip link is the first thing a keyboard user reaches.
- Named, role-bearing controls
- Menu buttons expose their expanded state; the current page is marked for assistive technology as well as visually.
How it was tested
Contrast ratios were computed for every foreground and background pair in the stylesheet rather than sampled by eye. Structure, headings, landmarks, link text, form labels and ARIA state were reviewed page by page. Keyboard operation was walked through on the navigation, the disclosure panels and the enquiry form.
What has not yet happened is a full assistive-technology pass — screen reader testing across JAWS, NVDA and VoiceOver, and testing with voice control and magnification. Until that is done, treat this as a careful self-assessment rather than a verified audit.
Known limitations
- The enquiry form has no live messaging yet
- It is labelled, keyboard-operable and clears contrast, but its error and success states are handled by the browser rather than by us, so they are not yet tested against 3.3.1 and 3.3.3.
- Third-party software
- Reading applications such as Adobe Digital Editions, and the ByteBooks account service, are not ours and we cannot warrant their accessibility.
- No AT audit yet
- Screen reader and voice-control testing is scheduled, not complete.
Found something that does not work?
Tell us what you were trying to do, which page you were on, and what you use to browse. We aim to respond within five working days and to fix confirmed problems at the next release.