Accessibility Statement.
Our commitment to a website usable by everyone — and how to tell us when it isn’t.
Overview
PCI wants its website to be usable by as many people as possible, regardless of ability or device. This statement sets out our approach, the standards we aim for, and how to report a barrier so we can fix it.
At a glance
What we aim for
- Alignment with WCAG 2.1 AA principles
- Semantic structure and keyboard navigation
- Sufficient colour contrast and readable text
- Text alternatives for meaningful images
- Ongoing testing and improvement
Reporting a barrier
PCI applies this consistently and documents what it does, so the approach can be checked and improved. Final detail is published as the institute matures, and is governed by the related policies below.
Common questions
Which standard does PCI follow?
We aim to align with WCAG 2.1 AA principles.
What if I find an accessibility barrier?
Tell us and we will aim to address it; reasonable accommodations also apply to certification.
Is the site keyboard-navigable?
Yes — semantic structure and keyboard navigation are part of the approach.
Why this matters
Clear policies matter because they are how fairness is made real. A certification body that treats everyone consistently — on eligibility, conduct, security, impartiality and appeals — is one whose decisions can be trusted, and whose credential therefore means the same thing for everyone who holds it. These pages set out those commitments plainly.
PCI states its position honestly, including where processes are still being established. The aim is not legal cover for its own sake but genuine, transparent governance — the substance that lets a credential, and the body behind it, earn and keep professional trust.
- Substance over marketing
- Fair, transparent process
- Honesty about our status
- Responsible, governed use of AI
Founding-stage document · Version 1.0 — effective date to be confirmed · Reviewed under PCI governance. PCI makes no claims of accreditation or recognition beyond what is true today.
How accessibility is designed in
Accessibility works best when it is part of how pages are built, not a repair applied afterwards. The practices below run through the whole site, not a handful of showcase pages.
Keyboard first
Navigation, search, forms and expandable questions can all be reached and operated with a keyboard alone, with a visible focus state and a skip link straight to the main content.
Semantic structure
Pages use proper landmarks, a single heading hierarchy and labelled form fields, so screen readers can announce where you are and what each control does.
Readable by default
Text is real text, never an image of text. Contrast and sizing aim at WCAG 2.1 AA, and layouts reflow rather than break when you zoom.
Reduced motion
If your device asks for reduced motion, decorative scroll animations are switched off entirely rather than merely toned down.
Descriptive links
Link text is written to make sense out of context, so a list of links read aloud by assistive technology stays meaningful.
Honest limitations
Where a page falls short of the standard we aim for, we treat that as a defect to be fixed and prioritised — not a footnote.
Tell us what is not working
If any part of this site is hard to use with your device or assistive technology, we want to know about it. The most useful reports include:
- The address of the page where you hit the barrier
- What you were trying to do, and what happened instead
- Your device, browser and any assistive technology in use
- How the barrier affected you — blocked completely, or made harder
Send this through the contact page. Reports are acknowledged promptly and prioritised by severity: a barrier that prevents someone enrolling or reading a policy is treated with more urgency than a cosmetic fault. If you need the substance of a page or document in a different format, ask — we will provide an accessible alternative wherever practicable. And if you are not satisfied with how a report is handled, the complaints policy applies to accessibility exactly as it does to everything else.
Do I need an account to report an accessibility problem?
No. Anyone can report a barrier, whether or not they are a member or candidate. The contact form and email route are open to all visitors, and reports are reviewed regardless of who sends them.
Keep going
The standard we build to, and the loop when we miss
The site is built toward WCAG 2.1 AA: semantic structure, keyboard operability, visible focus, alt text, sufficient contrast, motion that respects reduced-motion preferences, and forms with real labels. Examination accessibility runs further, through individually-assessed accommodations.
Where we fall short, the loop is simple: report the barrier via contact, we acknowledge it, and fixes enter corrective action with an owner. Accessibility feedback is treated as a defect report, not a favour.