COMPARELY.Resume a quote

Accessibility

Comparison journeys involve long forms under time pressure. Accessibility here is a functional requirement, not a policy page decoration.

What we hold ourselves to

  • The whole journey works with the keyboard alone: visible focus, a skip link, and logical tab order.
  • Forms announce errors in a summary that receives focus, with inline messages tied to their fields.
  • Colour contrast meets WCAG 2.2 AA for text and interactive states; tokens are tested, not eyeballed.
  • Animations respect prefers-reduced-motion and never block interaction.
  • Core journeys work with JavaScript disabled: filtering, sorting and comparison are server rendered.
  • Prices and figures use tabular numerals so columns stay readable.

When something does not work

If any part of this site blocks you, that is a defect worth reporting. On a live service this page would carry a monitored contact route and a response commitment.

Standard applied

Target: WCAG 2.2 level AA across the journey, verified with automated scans and manual keyboard and screen reader passes on every release. This statement itself follows the pattern public sector bodies use for accessibility statements.