Home · Accessibility

Accessibility statement

We sell accessible websites, so it would be strange if ours were not one.

Last updated 18 September 2026

1. Our commitment

This statement applies to https://smartersweb.uk, run by Smarter Web Solutions Limited. We want as many people as possible to be able to use it, whatever device or assistive technology they use.

We aim to meet the Web Content Accessibility Guidelines version 2.2 at level AA. We believe the site currently meets that standard, with the exceptions noted in section 4.

2. What we have done

  • Keyboard access. Every link, button, menu and form control can be reached and operated with a keyboard alone, in a logical order, with a clearly visible focus outline.
  • Skip link. A "skip to content" link is the first thing a keyboard or screen reader user meets on every page.
  • Colour contrast. Text meets or exceeds the 4.5:1 contrast ratio required at level AA, in both the light and dark appearance.
  • Not relying on colour alone. Errors, links and states are distinguished by text and shape as well as colour.
  • Structure. Pages use one h1 and a correctly nested heading hierarchy, real lists, real tables with header cells, and landmark regions so a screen reader can navigate by structure.
  • Forms. Every field has a visible, permanently associated label. Errors are described in text, listed near the field concerned and announced to assistive technology, never signalled by a red border alone.
  • Reduced motion. If your system asks for reduced motion, animations and smooth scrolling are switched off automatically.
  • Zoom and reflow. The layout works at 200% zoom and down to 320 pixels wide without horizontal scrolling or loss of content.
  • Dark mode. The site follows your system preference and offers a manual toggle, with contrast checked in both.
  • No motion traps. Nothing auto-plays, flashes, or moves without you asking it to. There is no carousel that rotates on its own.
  • Plain language. We write in short sentences and explain technical terms when we have to use them.

3. How we tested

The site was checked during development by keyboard-only navigation of every page and form, inspection of the heading and landmark structure, contrast measurement of every text and background pairing in both appearances, and testing at 320 pixels wide and at 200% browser zoom. It contains no images conveying information, so there is no alternative text debt.

4. Known limitations

  • The services and company menus in the main navigation open on hover on a pointer device and on click elsewhere. They are fully keyboard operable, but a very small number of older screen reader and browser combinations may announce the expanded state inconsistently. Every destination in those menus is also reachable from the services page and the footer, so nothing is behind a menu alone.
  • Accordion panels on the FAQ and pricing pages use the browser's native disclosure element. Support is good but older browsers present it more plainly.
  • We have not yet completed a full audit with JAWS. We have tested with the assistive technology available to us and will extend coverage.

If you hit something not listed here, please tell us. Real reports are more useful than any audit.

5. Reporting a problem

Email hello@smartersweb.uk or call +44 7912 315516. Tell us the page, what you were trying to do, and what happened. We acknowledge within two working days and aim to fix confirmed problems within 20 working days.

If you need any information on this website in a different format — large print, plain text, or read aloud over the phone — ask and we will provide it at no charge.

6. If you are not happy with our response

Tell us first and give us a chance to put it right. If you remain dissatisfied, the Equality Advisory and Support Service can advise you on your rights under the Equality Act 2010: equalityadvisoryservice.com.

7. Scope of this statement

This statement covers this website only. Websites we build for clients are theirs to maintain after handover, and their accessibility depends on the content added afterwards. We include accessibility in every build as standard and are always happy to audit an existing site — see services.