Last updated August 2026
Accessibility statement
What we built in
Semantic landmarks and heading structure on every page. A skip link to the main content. Full keyboard operability, including the menus, accordions and the contact form, with visible focus styles throughout. Text contrast at or above AA on every ground the site uses. Form fields with real labels, and errors announced to assistive technology. Meaningful alternative text on photography — captions describe the activity shown. Touch targets sized for hands, not cursors.
Motion
The site uses restrained animation — reveals, a drawn map motif, counted figures. All of it respects prefers-reduced-motion: with that setting on, content appears immediately in its final state and nothing moves. No content is available only through an animation, and nothing autoplays with sound.
Known limitations
The regional map and the meridian line-work are decorative SVG; the information they carry — office cities, addresses and telephone numbers — is always present as text beside them. The client marks are images of third-party logos; each carries the organization’s name as its alternative text, and the full list also appears as plain text on the clients page. The downloadable company profile is a designed PDF and may not read as fluently in a screen reader as this website; every fact in it that this website relies on is also published here as HTML.
Testing
Accessibility is checked automatically on every build, not audited once and forgotten. An axe-core pass runs against WCAG 2.0, 2.1 and 2.2 A and AA on all twenty-six routes, alongside tests that assert every page renders completely with JavaScript disabled and with reduced motion enabled, and that no element crosses the viewport edge at any width from 320px to 1440px. Keyboard tests cover the skip link, the desktop menu, the mobile drawer’s focus trap and the disclosure controls.
Two findings from that suite shaped the current build: the telephone links in the footer were below the 24 × 24 px minimum target size required by WCAG 2.2, and the lightest tone in our type scale was being used for small metadata at 2.9:1. Both are fixed, and the tests now prevent them recurring. Automated checks do not replace judgement, so manual keyboard and screen-reader passes are run before each release.
Tell us when something fails you
If any part of this website does not work with your assistive technology, or you need any content in another format, write to hasiconsulting@hasiconsulting.com. We reply within two working days, and fixing an access barrier goes to the top of the list, not the backlog.