Website Accessibility

What we are aiming for

We build this site to the Web Content Accessibility Guidelines 2.2, Level AA. We treat that as the standard to meet rather than a badge to display, which means being straight with you about the parts that do not meet it yet.

What is in place

• Landmarks and headings. Every page has one <main>, one header, one footer and one navigation region, and exactly one first-level heading. Heading levels descend in order without skipping.
• Skip link. A “skip to content” link is the first thing a keyboard user reaches, hidden by clipping rather than by moving it off-screen, so it does not create a stray horizontal scroll.
• Visible focus. Every link, button and form control shows a clear green focus ring when reached by keyboard, with an offset so it is not swallowed by the control’s own edge.
• Keyboard operation. The navigation, including its expanding panels, and both forms can be operated without a mouse.
• Image dimensions and alt text. Images carry width and height so the page does not jump as it loads, and meaningful images have text alternatives.
• Reduced motion. If your system asks for less motion, the reveal animations and transitions are switched off rather than merely shortened.
• Colour and contrast. Body text is dark ink on cream or white; the deep green and pale lime pairings used for buttons and panels were chosen to clear the AA contrast ratio.
• Text scaling. Type is set in relative units, so increasing your browser’s text size enlarges the page rather than clipping it.
• Form labels. Every field has a real label associated with it, required fields are marked, and validation messages name the field they refer to.

Where it falls short

Known gaps, as of the date above:

• The coverage map on the home page and on each location page has an empty text alternative, so a screen reader skips it. The surrounding text lists the same coverage, but the map itself should be described. This is on our list.
• The favicon is detailed enough that it is hard to make out at very small sizes. It does not affect page content.
• Downloadable reports we send to clients are not remediated for screen readers. Ask and we will provide the same content in an accessible format.
• Third-party fonts are fetched from Google. If that request is blocked, the page falls back to a system font, which changes the appearance but not the content or structure.

How we test

We check the rendered markup of every page rather than trusting a plugin’s dashboard: heading order, landmark counts, image attributes and structured data are validated across the whole site. That catches structural problems, but it does not replace testing with real assistive technology, which is why the report route below matters.

Tell us about a barrier

If something on this site is difficult or impossible for you to use, we want to hear about it, and we do not need you to know why it is broken.

• Email info@devsolutionai.com
• Call 0334 9447041, Monday to Friday

It helps if you can tell us the page, what you were trying to do, and what happened instead — plus your browser and any assistive technology, if you know it. We reply within four business hours during office hours. If a fix will take longer than that, we will tell you what we are doing and give you the information another way in the meantime.

Alternative formats

Anything on this site can be provided in another format — plain text, large print, or read out over a call. Just ask.