Accessibility

We are working towards WCAG 2.2 at level AA. We are not claiming to meet it. This site is part-built, the audit against that standard has not been done, and until it has, saying we conform would be a claim we cannot support.

• +A skip link is the first thing in the tab order on every page, so a keyboard user reaches the content without tabbing through the whole header first.
• +The page is marked up with the standard landmarks, header, navigation, main and footer, which is how a screen reader user jumps straight to a region.
• +Headings run in order, so the page can be navigated by heading rather than by scrolling.
• +The navigation works from the keyboard, including the services dropdown, and focused controls show a visible ring rather than the browser default, which is close to invisible on a dark background.
• +Every photograph carries alternative text describing what is in it. Decorative parts, including the animated field and the scrolling client strip, are hidden from screen readers rather than described at them.
• +Touch targets on phones are at least 44px on a side.
• +The animated field respects the reduced-motion setting on your device and stops moving.
• +Text is set against the dark ground at a size and weight intended to stay readable, and the layout reflows down to a narrow phone without a horizontal scrollbar.

These are the ones we know about. They are being worked on, and this list is the honest state of the site rather than a formality.

• +Some of the muted grey text may fall below the 4.5:1 contrast ratio AA asks for. The palette has not been measured properly, and where a colour fails it will be changed rather than argued about.
• +The client strip keeps scrolling even when your device asks for reduced motion. This is deliberate: iOS turns that setting on whenever Low Power Mode is on, whether or not anyone asked for less motion, and honouring it froze the row on any phone below twenty percent battery. The row can always be stopped, by pointing at it on a desktop or tapping a logo on a phone, which is the pause mechanism the standard asks for. We are still not satisfied with the trade and are looking at it again.
• +The site has not been tested end to end with a screen reader. It has been built to be readable by one; that is not the same as having sat down with NVDA or VoiceOver and gone through every page, which is what we owe it.

If something here does not work with the tools you use, we want to know, and a specific report is worth more than a polite one. Write to marketing@recognizegroup.com with the page address, what you were trying to do, and the browser and assistive technology you were using.

We aim to reply within five working days, and to tell you either when it will be fixed or why it will not be.

If any content on this site is not reachable for you, ask us for it in another format and we will send it. Nobody should have to fight a website to find out what a company does.