Commitment
ConsumerWise aims to make its consumer information usable by as many people as reasonably possible. Accessibility is treated as part of information quality: a legally accurate guide is not very useful if navigation, contrast, keyboard access or layout makes it difficult to read.
Standards used
The site aims to follow the principles of WCAG 2.2 at AA level where reasonably practicable, but this page does not claim that every page has passed a formal independent conformance audit. The design is reviewed as components and content evolve.
Structure and navigation
Pages use semantic headings and landmarks, a skip link, descriptive link text and responsive layouts. Guides and documentation use in-page navigation so long material can be scanned without reading every section in order.
Keyboard and focus
Primary navigation, mobile menus, search, cookie controls and interactive tools should be usable without a mouse. Focus should remain visible, controls should have accessible names and essential actions should not be available only on hover.
Colour, typography and reflow
The design uses high-contrast text and avoids using colour as the only indication of meaning. Layouts are intended to reflow to one column on narrow screens rather than forcing desktop grids or wide tables. User zoom should not be blocked.
Motion
ConsumerWise does not depend on decorative animation to convey essential information. The stylesheet includes reduced-motion handling where motion is used.
External documents and websites
Official sources can include PDFs and third-party websites that ConsumerWise does not control. Their accessibility is the responsibility of the relevant publisher. Where a source creates a barrier, users may be able to request an accessible format from that body.
Known limitations and reporting
A large site can contain isolated defects even when the global design is accessible. Report a barrier through the contact route with the page, browser/device, assistive technology if relevant, and what prevented access. Accessibility issues should be treated as bugs and prioritised according to their impact.