Legal

Accessibility

Parkva builds this site to WCAG 2.2 Level AA. Here is what we check, what we have not checked yet, and how to tell us something is broken.

  • We build this site to WCAG 2.2 Level AA, and we treat that as the floor rather than the goal.
  • Every page works from the keyboard, has one main heading, and reads in a sensible order.
  • Page motion can be turned off from the control in the footer, and your browser or phone setting is honoured either way.
  • Two screen-reader passes, one on VoiceOver for iOS and one on NVDA for Windows, are scheduled and have not run yet. This page will say when they do.
  • If something here does not work for you, write to info@parkva.com and tell us what you were trying to do.

This box is Parkva’s plain-English summary. It is not the policy, and where the two read differently the text below is the one that counts.

Effective
Last changed
Reviewed

Video pages carry a transcript or offer to email one.

The standard we build to

Every page on this site is built to meet WCAG 2.2 at Level AA. That is the version published in October 2023, and it is the bar the whole site is measured against, not a target for later.

We are not claiming a certificate. No third party has audited this site. What follows is what we actually do and what we have not done yet.

What we build and check

These are the things we design for and check as the site changes:

  • One heading structure per page. Every page has exactly one main heading, and the headings under it are real headings in order, not text styled to look like one.
  • Keyboard first. Every link, button, menu, and form control can be reached and used with a keyboard alone, and the focus outline is visible on both the light and the dark backgrounds.
  • The header never hides what you are on. The bar at the top of the page is fixed, so we size the scroll offset to it. Tabbing to something just below the fold brings the whole control into view rather than half of it.
  • Targets you can hit. Pointer targets are at least 24 by 24 pixels, and the main touch controls are 44.
  • No sideways scrolling. Pages are designed at a 390 pixel width first, and we check that nothing overflows sideways at that size.
  • Colour is never the only signal. Status is carried by a word as well as a colour, and links in body text keep their underline.
  • Images say what they show. A photo or a screenshot carries a description of the state it is showing, not the name of the component in it. Decorative shapes are hidden from screen readers instead of being described.
  • Plain HTML underneath. The pages are static HTML and CSS. Reading the site does not require JavaScript. Submitting a form does, and that is a real limitation, listed below.

Turning off motion

There is a Motion control in the footer of every page. Switching it off stops the animation on the site: the scrolling line that runs down the page, the reveals, the video loops, and the page-to-page transitions. Text never sits at zero opacity waiting for an animation, so with motion off you see the same words in the same order.

If your browser, phone, or computer is already set to reduce motion, we honour that without you touching anything. The footer control is there for the case where the system setting is not what you want on this site, and your choice is remembered in your own browser.

Where we are not there yet

  • No screen-reader pass has been recorded yet. One pass on VoiceOver for iOS and one on NVDA for Windows are scheduled over the site’s main pages. Until they are done, we are telling you the pages are built correctly, not that they have been used with a screen reader end to end. When the passes run, this section will name the date and what they turned up.
  • Forms need JavaScript. The demo and contact forms are submitted by a script. With JavaScript off the rest of the site reads normally, but a form will not send. If that is your situation, write to us at the address below and we will pick it up from there.
  • Video captions vary. Every video page carries a written transcript, or offers to email you one. Captions on the player itself are not on every video, and each player says which it is.
  • PDFs are not fully tagged. Documents we link to are the versions our team produced. If you need one of them in another format, ask and we will get you the content another way.
  • Automated checks are still being wired in. Running an accessibility scanner over every page on every change, in a desktop, a mobile, and a reduced-motion browser, is work in progress rather than something already running on every commit.

Telling us something is broken

Write to info@parkva.com. It helps if you can tell us:

  • the address of the page,
  • what you were trying to do,
  • what happened instead, and
  • what you were using, for example Safari on an iPhone with VoiceOver.

A person reads it and a person replies. If the problem is on a page you need right now, say so and tell us what you needed off it, and we will send you the content directly rather than making you wait for the fix.