Accessibility Statement — WCAG 2.1 AA Conformance | JP Sheet

WCAG 2.1
AA
Target

WCAG 2.1 Level AA conformance target

JP Sheet aims to meet the Web Content Accessibility Guidelines 2.1 at Level AA — the international standard adopted by the EU Accessibility Act, the UK Public Sector Bodies Accessibility Regulations, and US federal accessibility law.

What is our current conformance status?

Partial conformance with WCAG 2.1 Level AA.

This means the majority of our pages meet the AA criteria, but some content or components do not fully conform yet. We are actively working to close the remaining gaps. We re-review accessibility every quarter.

Our review uses a combination of:

Automated tools (Lighthouse, axe DevTools)
Manual keyboard-only testing
Screen reader testing with NVDA, JAWS and VoiceOver
Colour contrast verification with WebAIM Contrast Checker
Real-user feedback (we treat every accessibility report as a priority bug)

What accessibility features does JP Sheet have?

Across the site, we have built in the following:

Keyboard navigationAll interactive elements (forms, buttons, links) work without a mouse — Tab, Shift+Tab, Enter, Space.

Screen reader friendlySemantic HTML5, proper heading hierarchy, ARIA labels where needed.

Image alt textEvery image on the site has descriptive alt text.

Sufficient colour contrastBody text meets WCAG AA contrast ratio (4.5:1 minimum).

Responsive designPages reflow for mobile, tablet, desktop, and high-zoom (up to 400%).

Respects user preferencesHonours system font-size, reduced-motion, and dark-mode preferences.

No auto-playing mediaNo audio or video plays without user action.

Focus indicatorsVisible focus rings on every interactive element when tabbed to.

Skip-to-contentKeyboard users can skip past the navigation directly to the page content.

Cookie banner accessibilityCookie consent dialog uses ARIA role="dialog" and aria-live for screen readers.

Form labelsEvery form input has an associated label, not just a placeholder.

Error messagesForm errors are announced clearly and associated with the relevant field.

What accessibility issues do we know about?

Honest disclosure of what we're still working on:

Chatbot keyboard focusThe AI chatbot widget may not correctly manage keyboard focus when it opens and closes. We are working on a fix for this. Workaround: close the chatbot with Escape, then continue tabbing.

Some PDF reports not fully taggedVerification reports delivered as PDFs may not have fully-tagged structure for screen readers. The HTML version of every report is fully accessible — please request the HTML link if you need it.

Third-party widgetsEmbedded YouTube videos, Stripe Elements, and PayPal buttons follow their providers' accessibility levels. We link to those providers' accessibility statements below.

Complex tables on country pagesSome import-cost comparison tables may not yet have full row/column header semantics. We are restructuring these as part of our 2026 review.

If you encounter any other barrier, please tell us — see the contact section below.

Which assistive technologies do we test with?

We test JP Sheet with the following combinations on each quarterly review:

Screen readers: NVDA (Windows + Firefox / Chrome), JAWS (Windows + Chrome), VoiceOver (macOS Safari, iOS Safari)
Browser zoom: 200%, 400%
Operating-system text scaling: Windows scaling 150%, macOS large text, iOS Dynamic Type
Keyboard-only navigation: Tab order, focus management, dialog handling
Reduced motion preference: Animations and transitions disabled when the OS requests reduced motion

If you use a technology not in this list and something doesn't work, please tell us — we will add it to our test suite.

What about third-party content?

Some elements on JP Sheet are provided by third parties and follow those providers' accessibility commitments:

Stripe Elements (payment form) — Stripe's accessibility statement
PayPal Smart Buttons — PayPal's accessibility commitment
YouTube embedded videos — YouTube's accessibility resources
Cloudflare CDN — content delivery only, no UI

Which accessibility laws and standards does JP Sheet aim to meet?

Our WCAG 2.1 AA target covers the substantive requirements of the major accessibility laws worldwide:

EU Accessibility Act (Directive 2019/882, in force from June 2025)
UK Public Sector Bodies Accessibility Regulations 2018 (we follow the same standard voluntarily)
Americans with Disabilities Act (ADA) — Title III, as interpreted for websites by US courts
Section 508 of the US Rehabilitation Act
AODA (Accessibility for Ontarians with Disabilities Act)
EN 301 549 (European harmonised standard for ICT accessibility)

How do I report an accessibility issue?

If anything on JP Sheet is hard for you to access — a button you can't reach with a keyboard, text you can't enlarge, a form your screen reader can't navigate — please tell us. We treat accessibility reports as priority bugs.

♿ Report an access difficulty

Email us with subject "Accessibility" and we will acknowledge within 48 hours, with a fix or workaround.

Email [email protected]

What to include:

The URL of the page where you ran into the issue
What you were trying to do
What happened (or didn't happen)
The assistive technology and browser you're using, if you know it

We will respond within 48 hours with either a fix, a workaround, or a timeline. If we can't fix the issue immediately, we will help you complete your task by another route — for example, by processing your verification order over email rather than the website.

When is this statement updated?

This accessibility statement is reviewed every quarter alongside our accessibility audit. The date at the top reflects the most recent review. We will update this statement when:

A new accessibility feature is launched
A known issue is resolved
A new known issue is identified
Our testing matrix changes
Applicable law changes

Related: Privacy Policy · Terms · Support