Accessibility

What we aimed at

WCAG 2.2 level AA. We believe the site meets it, tested by hand rather than only by an automated checker, which catches roughly a third of real problems.

What that means in practice

• Everything works from the keyboard. The menu, the service accordions, the tabs, the estimator, the custom dropdowns and the form are all reachable and operable with Tab, arrow keys, Enter and Escape, with a visible focus ring at every step.
• Screen readers get real structure. One h1 per page, landmarks, breadcrumbs, labelled form fields, error messages tied to the field they belong to, and the accordions and tabs follow the published WAI-ARIA patterns rather than being made of styled divs.
• Motion can be switched off. If your system asks for reduced motion, every animation stops: no scroll reveals, no moving dial, no sliding panels.
• Contrast was measured, not guessed. Body text and interface labels are tested against their actual backgrounds, and several colours on this site were lightened specifically because they missed the ratio.
• Text resizes. The whole type scale is fluid, and the layout holds together when you zoom to 200 per cent.
• It works without JavaScript. With scripts disabled every page still renders completely, because content is never revealed by script alone.

Known limitations

• The hero dial is decorative and is described to screen readers as a single image rather than element by element. It carries no information that is not also written on the page.
• The twelve system diagrams are labelled with a summary rather than a full text alternative for every node. If one of them matters to you and the label is not enough, ask us and we will write it out.
• The estimator has been tested with a keyboard and with a screen reader, but not yet with voice control software.

Tell us if something is wrong

Write to contact@zegleragency.com with the page and what happened. Accessibility problems are treated as bugs, not requests: we fix them, and we will tell you when it is done.