Accessibility statement for SchemeReady

The standard we work to

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The website and the app are partially conformant with that standard: the known exceptions are listed below. We are a private company, so the public sector accessibility regulations do not apply to us, but we use the same standard because it is the one most people ask for.

What you should be able to do

• Use every page and every part of the app with a keyboard alone, with a visible focus ring on the thing you are on, and a skip link at the top of every page.
• Zoom to 400 per cent, or use a narrow phone screen, without content being cut off or scrolling sideways.
• Read the text against its background at a contrast of at least 4.5 to 1 in both the light and the dark colour scheme, which follows your device setting.
• Use a screen reader: pages have one main heading, headings in order, landmarks for the header, navigation, main content and footer, labels on every form field, captions on tables and text on every button.
• Hear about things that change without a page load, such as a saved answer, a licence check or a loaded list, through live regions.
• Turn off animation: we honour the reduce motion setting on your device. The home page carries one decorative drawing behind the heading. It stops on its own after about half a minute, it never starts if your device asks for reduced motion, it does nothing while the page is in a background tab or scrolled past, and it is hidden from screen readers.
• Understand every state without relying on colour: the four bands always print their names, and errors are written next to the field they belong to.
• Use the site module on a phone with one hand, with buttons at least 44 pixels tall and other targets at least 24 by 24 pixels.
• Open the question and answer sections and the menu without JavaScript, with a plain menu and the company details shown instead.

Known limitations

PDF files

The report, checklist, site visit records and template PDFs are made in the browser by a library that does not write tagged PDF, so headings, tables and reading order are not marked for assistive technology. Every report in the app also has an HTML view with the same content and full heading and table markup. Use that as the accessible version, print it from the browser if you need paper, and tell us if anything in it is not read correctly.

Excel files

The evidence list, action plan and registers workbook are ordinary spreadsheets with header rows, frozen panes and drop-down lists. They work with screen readers in Excel, but sheet-level descriptions are limited. The same rows are in the HTML view of the report.

The sample report embed

The sample report page embeds a PDF. If your browser or assistive technology cannot read it, use the download link beside it, or the description of each part of the report on the same page.

Checkout

Payment is taken on pages run by Polar Software, Inc., our payment partner. We do not control those pages. If you cannot complete a purchase there, email us and we will find another way.

The Denver House site

Links to the expert hour and the company pages go to the Denver House Consultancy website, which has its own design. This statement does not cover it.

Word templates

The template Word files use real headings and tables, but form fields are plain table cells rather than Word content controls, so a screen reader announces them as table cells.

How we test

Each page and each screen of the app is checked with the keyboard alone, at 400 per cent zoom, with the browser's reduce motion and dark scheme settings, and with a screen reader (VoiceOver on macOS and iOS, and NVDA on Windows where available). Colour pairs are checked against the 4.5 to 1 ratio with a script before any change to the stylesheet. We have not yet commissioned an external audit of the site.

Tell us about a problem

If you find something you cannot use, or you need any of our content in another format, email info@denverhouse.co.uk with the page or screen, what you were trying to do, and the browser and assistive technology you were using. We aim to reply within two working days and to fix anything we can. Problems that turn out to be in the PDF format are answered with the HTML view, which we can also send as a file.

What we are working on

• Tagged PDF output, when a browser library that writes it is available without a build step.
• A text-only export of the report for people who prefer plain documents.
• An external review of the app's site module by someone who uses a screen reader on a phone.

Technical information

The website is plain HTML, CSS and JavaScript with no framework. The pages work without JavaScript apart from the shared menu, the price and checkout links, the live template list and the welcome page form, each of which has a plain fallback on the page. The app needs JavaScript and stores your answers in your browser. It has been tested in current versions of Chrome, Edge, Firefox and Safari on desktop, and Safari on iOS and Chrome on Android.