Legal

Accessibility

What we built in, what we have verified, and what we have not. If something on this site blocks you, we want to know and we will fix it.

Last updated

We build to accessibility as an acceptance criterion rather than a post-launch cleanup. This page sets out what that meant in practice for this website, and where the limits of our testing are.

What we have built in

  • Semantic HTML — headings in a logical order, real lists, real form labels, and landmarks so a screen reader user can navigate by structure.
  • Full keyboard operation — every link, button, menu, form field and expandable section is reachable and operable by keyboard, with a skip link to main content as the first focusable element.
  • Visible focus indicators — a consistent, high-contrast focus ring that is never removed for cosmetic reasons.
  • Contrast — body and supporting text colours were chosen against the page background to meet or exceed the WCAG 2.2 AA 4.5:1 ratio for normal text.
  • Reduced motion — if your system requests reduced motion, entrance animations and smooth scrolling are switched off and content renders in its final state immediately, rather than playing a shortened animation.
  • Works without JavaScript — navigation, expandable sections and both forms function with JavaScript unavailable. Scripts add convenience, not capability.
  • Touch targets — buttons, form fields and navigation items are at least 44px tall. Secondary standalone links, such as those in the footer, are at least 28px, clearing the WCAG 2.2 AA minimum of 24px. Links inside a sentence follow the surrounding text, which that criterion explicitly permits.
  • Text scaling — the layout uses relative units and reflows to 200% zoom without content being cut off or overlapping.
  • Form errors — described in text next to the field, linked programmatically to the input, and never signalled by colour alone.
  • Meaningful alternatives — decorative graphics are hidden from assistive technology; the interface schematic on our product pages has a text caption explaining what it shows.

What we have tested

  • Keyboard-only navigation of every page and both forms
  • Contrast ratios calculated against the design tokens used
  • Rendering and reflow at 200% zoom and at small mobile widths
  • Behaviour with JavaScript disabled
  • Behaviour with a reduced-motion preference set
  • Automated HTML and accessibility linting during the build

What we have not verified

We want to be straightforward about this rather than claim a conformance level we have not evidenced:

  • This site has not been audited by an independent accessibility specialist.
  • We have not completed systematic testing with screen readers across the full range of combinations — NVDA, JAWS, VoiceOver and TalkBack each behave differently, and automated tooling does not substitute for that.
  • We have not tested with switch access, voice control or magnification software.

Full WCAG validation requires manual testing with assistive technologies and review by an accessibility expert. Our position is therefore that this site was built to WCAG 2.2 AA intent, and that we have not had that independently confirmed.

Known limitations

  • The desktop navigation dropdowns open on hover and on keyboard focus. They do not close on Escape — moving focus away closes them.
  • Some technology and skill lists are dense at small sizes. They remain readable and reflow correctly, but they are long to move through with a screen reader.

Tell us if something does not work

If you hit a barrier on this site, please tell us what page you were on, what you were trying to do, and what assistive technology or browser you were using. Write to info@sncorporates.com.

We will acknowledge within one business day, tell you whether we can fix it and roughly when, and offer another way to get what you needed in the meantime. A reported barrier is treated as a defect, not a feature request.

Our client work

We hold the front-end work we deliver for clients to the same standard — contrast, keyboard operation, focus visibility and reduced-motion support are acceptance criteria on our builds, not optional extras. Where a client needs formal conformance evidence, we recommend an independent audit and will work to its findings.