Accessibility Statement

We build accessible websites for a living, so we hold ka-performancefl.com to the same standard we sell. This page says what we aim for, what is actually in place, where the site still falls short, and how to reach a human if any of it gets in your way.

The standard we build to

We aim to meet WCAG 2.2 at Level AA. That is the level most accessibility regulations point at, and it is the level we measure client work against too. To be straight with you: this is our own assessment, checked with automated tooling and manual keyboard and screen reader passes. It has not been audited by an independent third party, so we describe the site as aiming at Level AA rather than certified against it.

What is in place

• Colour contrast measured against AA for body text, headings, and interface controls.
• Every page usable by keyboard alone, with a visible focus outline on anything you can interact with.
• A skip-to-content link as the very first stop in the tab order, so you can jump past the navigation instead of tabbing through it on every page.
• Headings, landmarks, and lists marked up as real structure so screen readers can navigate by them.
• Text alternatives on images that carry meaning, and decorative artwork hidden from assistive technology instead of read aloud.
• Labels and accessible names on buttons, form fields, dialogs, and icon-only controls.
• Motion respects your system setting. If you have asked your device to reduce motion, the scroll animations, the drifting reviews, and the page-turn effects stop moving.
• Content is written to be readable, and the layout reflows without horizontal scrolling down to a phone-sized screen.

How we handle artwork

The portfolios and the illustrated picture book present artwork as content, which changes what conformance means on those pages.

Where text appears inside a piece, it is part of the composition and cannot be re-rendered as live text without altering the work. WCAG 2.2 excepts this under 1.4.5 where the particular presentation is essential, the same provision that covers logotypes. The same applies to contrast: 1.4.3 does not impose a contrast requirement on text that is part of a picture containing significant other visual content.

What we do owe, and what we hold ourselves to, is a text alternative for every piece that describes the work and includes any words appearing within it. Interface text around the artwork, including titles, artist names, captions, and controls, is live text held to the full AA standard.

Where we can avoid the question entirely, we do. The picture book is built from the illustrator's untexted artwork with the story set as live HTML over it, so the prose itself selects, resizes, and is read aloud like any other text on the site. Only the lettering genuinely painted into a scene stays part of the image.

How we test

Automated tools catch roughly a third of real accessibility problems, so we treat them as the floor rather than the audit. Every page of this site is checked with axe-core against the WCAG 2.0, 2.1, and 2.2 A and AA rule sets, and with Lighthouse. On top of that, a scripted keyboard pass walks the entire tab order of every page and checks that each stop is reachable, in a sensible order, and shows a visible focus indicator. Where axe cannot decide, usually contrast on an element whose background is animated or overlapping, we measure it by hand.

The training section, added in September 2026, went through all of that plus a read of each page's accessibility tree as a screen reader would present it, and a full keyboard play-through of the embedded sample confirming that focus enters the frame, moves through it, and hands back to the page rather than getting stuck. The scripts that do this live in the site's repository and run before every deploy that touches those pages, so the statement stays true rather than aspirational.

Known limitations

The home page leans on scroll-driven animation. The content is built to be understandable without the motion, and the sequence stops entirely when reduced motion is requested. We are continuing to simplify the interaction for people who keep motion enabled.

The training samples run inside a frame on the samples pages. Frames are the most common place for keyboard focus to get trapped, so each viewer page has a "skip past the sample" link that appears when you tab to it, and every sample can also be opened on its own in a new tab, full screen and with no frame at all. The samples themselves are built to be operable with the keyboard alone, with no timing and no sound.

The training section has not yet had a live session with a person driving a screen reader end to end, as opposed to our review of what the screen reader would be given. That session is next on our list, and this page will say so when it has happened.

Third-party content

A few things on this site come from outside it: customer reviews pulled from Google, and the voice assistant demo on our services page. We choose these carefully and wrap them in our own accessible controls where we can, but we do not control everything they render. If one of them is what is blocking you, tell us anyway. We would rather replace a component than leave you stuck with it.

Tell us if something blocks you

If any part of this site is difficult or impossible to use, we want to hear about it, and we will fix it. Email help@ka-performancefl.com with whatever detail you have: the page you were on, what you were trying to do, and the browser or assistive technology you were using. Rough notes are fine, you do not need to diagnose it for us.

The same address works for accessibility requests more generally. If you need something from this site in a different format, or you would rather give us your project details by phone or email than through a form, ask and we will make it work.