PRoVENaccess accessibility statement

How this website is built to work for everyone.

We advise other organisations on accessibility, so we hold our own website to the same standard. This page states the standards we build to, what we have checked, what is still open, and how to tell us if something gets in your way.

In short: we built this site to be usable by everyone. This page lists what we checked, what is still left, and how to tell us about a problem.

Our commitment

Practise what we preach.

Written for the people who use this site, not for a legal file.

PRoVENaccess helps organisations make their websites, applications and documents usable by more people. We keep this website under regular review, so the advice we give is the advice we follow.

For us accessibility is not a one-off test. Every page we add or change is checked against the same list we use on client work. Anything we cannot fix straight away is written down on this page.

Standards

What we build to.

The reference points behind every design and code decision on this site.

WCAG 2.2

The international rules for accessible web content, published by the World Wide Web Consortium (W3C). These guidelines inform how we design, build and review this website.

Section 508 and EN 301 549

The accessibility requirements used in United States federal purchasing and in European public purchasing. Both follow WCAG, so work done against WCAG normally covers them too.

PDF/UA for documents

The international standard for accessible PDF files. We apply it to the reports and documents we hand over, and to anything you can download from this site.

A clear keyboard path

Every link, button and form field can be reached and used with the keyboard alone. The focus ring changes colour to stay visible on the background behind it, at a contrast of at least 3 to 1.

Conformance status

Where the site stands today.

A plain answer, because a claim without evidence helps nobody.

Current status

Partially conformant with WCAG 2.2 at Levels A and AA

Automated checks on every page found no violations, keyboard use passed, and hand testing with the NVDA and JAWS screen readers read the site well. We are not yet claiming full conformance, because VoiceOver and TalkBack have not been tested. This statement will be updated when that work is complete.

"Partially conformant" means some parts of the site do not yet meet the standard in full. We would rather say that plainly than publish a badge we cannot support.

Checked and working

What we have already tested.

  • Automated scanning of every page with axe-core 4.10.3 — no violations found
  • Keyboard-only use of every page, menu and form, with a visible focus ring on each control
  • Hand testing with the NVDA and JAWS screen readers on Windows across every page — headings, reading order, menus, links, form fields and error messages
  • Zoom to 400% and a 320-pixel-wide screen — no lost content and no sideways scrolling
  • Heading levels, page titles, language setting, links and landmark regions
  • Text sizes checked for the contrast each level asks for, including help and error messages
  • Motion reduced for people who ask for less animation, and colours kept readable in Windows High Contrast mode
  • Form errors shown in a summary at the top, each one linking straight to the field that needs fixing
Still open

What is not finished yet.

Screen readers still to cover

NVDA and JAWS on Windows have been tested by hand and the site reads well. VoiceOver on macOS, iPhone and iPad, and TalkBack on Android, have not been tested yet. Until they are, we cannot say the site is fully conformant.

The enquiry form

The contact page sends your message to us by email rather than preparing a draft for you to send yourself, and nothing you type is stored on this website. Our sending address has not finished its setup yet, so an enquiry submitted today may not reach us; if that happens the page says so plainly instead of pretending the message went through.

Older browsers and tools

We check current versions of the main browsers and assistive technology. Older combinations may still show problems.

Feedback

Found a barrier? Tell us.

We read every report ourselves, and we fix what we can confirm.

If anything on this site is hard to use, we want to know. Use the contact page and tell us what you were trying to do, what happened, and which browser, device and assistive technology you were using.

We aim to reply within two business days, and to tell you what happens next. If a barrier is confirmed, we fix it or explain when it will be fixed.

You can also ask for anything on this site in another format, such as a simpler HTML page or a plain-text version.

How to report a problem

  • Use the contact page and pick "Report an accessibility barrier" under "What can we help with?".
  • Include the web address of the page where the problem happened.
  • Tell us what you were trying to do and what went wrong.
  • Mention your browser, device and assistive technology, if you know them.
Report a barrier
Technical details

How the site is made.

The technologies this statement covers.

Built with

HTML, CSS and JavaScript, using a standard component library whose dialogs, menus and form controls follow accessible conventions.

Browsers we check

Current versions of Chrome, Edge, Firefox and Safari on Windows, macOS, Android and iPhone.

Assistive technology we test with

NVDA and JAWS on Windows, VoiceOver on macOS and iOS, TalkBack on Android, plus keyboard-only and magnifier use.

Text size and zoom

Text can grow to 200% and the page can zoom to 400% without losing content or function.

About this statement

This statement was prepared on 9 October 2026 and covers every page on this website. It is reviewed at least every six months, and again whenever the site changes enough to affect accessibility. It describes the state of the site on the date above; it is not a certificate of conformance.

The review used automated scanning with axe-core 4.10.3 on every page, plus manual keyboard, zoom, reflow, colour and structure checks. Hand testing with NVDA and JAWS on Windows was completed on 9 October 2026; VoiceOver and TalkBack testing is still to be done.

Start with a scoped conversation.

Tell us what you are working on and what you need to demonstrate.

Tell us about your project