Plainfiles

Accessibility statement

We want everyone to be able to read our guides and use this site, whatever device, settings or assistive technology they use.

This statement applies to the Plainfiles website at plainfiles.co.uk. The site is run by TurboKast Ltd. This statement was prepared on 22 October 2026, when the site was last tested.

The standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2, level AA. Based on the testing described below, we believe every page on the site meets that standard. This is our own assessment. The site has not been audited by an independent accessibility specialist.

What we have done

  • Every page has one main heading, a logical heading order, and landmarks (header, navigation, main content and footer) so screen reader users can jump around.
  • A “Skip to content” link is the first thing keyboard users reach. It becomes visible when it has focus.
  • Everything can be used with a keyboard alone. Focus is always visible, with a thick ring that has strong contrast against the page.
  • Text and controls meet the minimum colour contrast ratios (4.5 to 1 for text, 3 to 1 for buttons and focus rings). Colour is never the only way we show something: links are underlined, and the current page in the menu also has an underline.
  • The pages reflow to a single column down to 320 CSS pixels wide, with no sideways scrolling, so they work at 400% zoom. Text can be enlarged to 200% without losing content.
  • Tables have captions and proper header cells. If a table is too wide for a small screen it scrolls inside its own box, which you can reach and scroll with the keyboard.
  • Images that carry meaning have text descriptions. Images that only decorate are hidden from screen readers.
  • Buttons and links say where they lead, for example “Buy on Payhip (opens payhip.com)”. Links open in the same tab.
  • The site follows your device settings for dark mode, reduced motion, forced colours (Windows high contrast) and text spacing.
  • There is no JavaScript, no animation, no autoplay, no time limits, no cookies and no forms on the site.
  • Guides are written in plain English, with abbreviations spelled out the first time they appear on a page.

How we tested

Testing was done on 22 October 2026 against every page of the built site, using a script kept in the site’s repository (tools/a11y_check) so it can be repeated after every change.

  • Automated checks: axe-core 4.14 (WCAG 2.0, 2.1 and 2.2 level A and AA rules plus best-practice rules), Lighthouse 12.8 accessibility audits (mobile and desktop) and html-validate 9.7 for HTML errors. They were run at several screen sizes, in light and dark colour schemes.
  • Browser: Google Chrome 154 (headless). We did not test in Firefox, Safari or Edge.
  • Layout and zoom: full-page screenshots at 320, 375, 414, 768, 1024, 1280 and 1920 pixels wide, plus the widths that 200% and 400% zoom produce, checked by eye and by script for sideways scrolling, clipped text and overlapping content. We also tested with the WCAG text-spacing settings applied, text enlarged to 200%, reduced motion, dark mode and forced colours.
  • Keyboard: the script tabbed through every page, checked the skip link, tab order, focus visibility and focus ring contrast, and that focused items are not hidden.
  • Screen reader output: we read the browser’s accessibility tree (the structure screen readers use) for pages of every type. No one tested the site using a real screen reader such as NVDA, JAWS, VoiceOver or TalkBack, and no disabled people were involved in testing. A screen reader user may find problems that these checks cannot.
  • Contrast and size: we calculated the colour contrast of every piece of text and every button, and checked that clickable targets are at least 24 by 24 CSS pixels.

Known limitations

  • Product preview images. The pictures of each kit and logbook contain small text. Their text descriptions summarise what they show but do not repeat every word. The same information is on the page as ordinary text.
  • The downloads themselves. The Word, Excel and PDF templates you get when you buy a kit were not part of this website test. We have not audited them for accessibility. The Word and Excel files are editable so you can change fonts, sizes and colours. The same goes for the free sample PDFs on the kit, logbook and guide pages: each is one or two pages copied from our products, and they are not tagged for screen readers. Ask us if you would like the content of a sample in another format.
  • Other websites. We link to GOV.UK, legislation.gov.uk, Payhip and other sites. We do not control their accessibility.
  • Wide tables. On very narrow screens or with very large text, some tables scroll sideways inside their own box rather than rewrapping.
  • Official wording. Where we quote legal terms we keep the official words so you can match them to the source. These can be harder to read than the rest of the page. Each guide explains them in plain English.
  • Language. The site is in English only.
  • Dark mode. It follows your device setting. There is no switch on the page.

Tell us about a problem

If you cannot use part of this site, or something is hard to read or understand, email us at support@turbokast.com. Tell us the page and what went wrong, and the browser or assistive technology you were using if you know it. We aim to reply within 5 working days and to fix problems as quickly as we can. You can also ask for information from a page in another format, for example as plain text.

If you are not happy with our response

You can contact the Equality Advisory and Support Service (EASS), which is free and independent. In Northern Ireland, contact the Equality Commission for Northern Ireland.

Keeping this up to date

We repeat the checks whenever the site changes, and we will review this statement at least once a year. It was last updated on 22 October 2026.