Checkout Loom accessibility statement: a website built to work for everyone who visits
Checkout Loom accessibility statement explains how we build this site for WCAG 2.2 AA website accessibility, so that every store owner can read, understand and use it whatever their device, ability or assistive technology, what we do, how we test, where we know we fall short and exactly what to do if something gets in your way, with a written reply within five working days.
Accessibility is part of how every page is built, not a layer added at the end. These are the six things we hold ourselves to, and the sections below give the detail.
We aim for WCAG 2.2 level AA
The Web Content Accessibility Guidelines are the standard we test against, across contrast, structure, navigation, forms and motion, on every page we publish.
Text you can read
Body text is large and has strong contrast against its background, and it resizes with your browser settings without breaking the layout or hiding content.
Forms you can finish
Every field has a visible label, required fields are announced and errors say what went wrong and how to fix it, in words and not only in colour.
Motion that respects you
Animated illustrations stop moving when your device asks for reduced motion, nothing flashes and the page works exactly the same without any animation.
Every screen size
Pages reflow from large monitors to small phones without sideways scrolling, and tap targets are comfortably large for fingers and pointers.
Tell us when we fall short
If you meet a barrier, the contact form is the way to report it. We confirm within one working day and reply with a plan within five working days.
The statement
Checkout Loom accessibility statement, section by section
Use the contents list to jump to any part of this statement. Each part opens with a one-sentence summary in plain words and then explains what we do in detail.
Last updated: 14 October 202614 sectionsPlain-English summary on every section
Accessibility contents
01Our commitment
We want every store owner to be able to use this site, and we treat accessibility as part of quality, not as an extra.
Checkout Loom builds automation for online stores, and the people who use it are as varied as the stores they run. Some use a keyboard instead of a mouse, some use a screen reader, some enlarge the text, some have a small phone and some simply prefer a calm page. We want all of them to be able to read this site, understand it and get what they came for.
We build accessibility into every page from the start, test it before the page goes live and keep improving it. This statement describes what we do, what we know is not perfect yet and how to tell us about a problem.
02Our standard
We aim to meet WCAG 2.2 level AA on every page of this site.
Checkout Loom aims to meet the Web Content Accessibility Guidelines, known as WCAG, version 2.2 at level AA. These guidelines explain how to make web content more accessible to people with visual, hearing, motor and cognitive disabilities, and they also make a site easier for everyone to use, for example on a small screen or in bright light.
WCAG is organised around four principles: content must be perceivable, operable, understandable and robust. The sections below describe what we do for each one, and the table later on this page shows the same thing at a glance.
03What we do
We build in the features that matter most, and we test them.
Structure: Pages use proper headings, landmarks and lists, so screen readers and keyboard users can move around quickly and skip repeated content.
Contrast and size: Text meets the contrast ratios in the guidelines, and the base size is large, between sixteen and eighteen pixels depending on the screen.
Keyboard use: Everything you can do with a mouse you can do with a keyboard, in a logical order, and the focus indicator is always visible.
Forms: Fields have visible labels, hints are tied to their fields and errors are announced and explained.
Images and illustrations: Decorative illustrations are hidden from assistive technology, and meaningful ones carry text alternatives that say what they show.
Motion: Animation respects the reduced-motion setting, nothing flashes more than three times a second and no information depends on animation.
Enlarging and reflow: Pages remain usable at two hundred percent enlarge and on narrow screens, without horizontal scrolling.
Colour: We never use colour alone to carry meaning, so people who cannot tell colours apart lose nothing.
04Perceivable: seeing and hearing the content
Everything on the page can be read, heard or magnified by the tool you use.
Text has enough contrast against its background and can be resized without losing content. Images that carry meaning have text alternatives, and decorative images are marked so that screen readers skip them. We do not rely on audio alone, and where we use charts or diagrams, the same information is also given in text.
Pages work in different orientations and display modes, and they respect the colour and contrast preferences your device offers where we can.
05Operable: using the page without a mouse
Everything works with a keyboard, a touch screen or a switch, and nothing times out without warning.
Every link, button, form field and menu can be reached and used with a keyboard, and the order of focus follows the order of the content. The focus indicator is always visible, so you can see where you are. Touch targets are large enough for fingers, and nothing depends on a complicated gesture.
We avoid content that moves, blinks or scrolls on its own for longer than a few seconds, and where we have an animated illustration it stops for visitors who ask for reduced motion.
06Understandable: clear words and predictable pages
We write in plain language, label things clearly and keep pages behaving the way you expect.
We write in plain English, keep sentences readable and explain terms the first time we use them. Navigation and headings are consistent from page to page, forms say what each field is for and error messages explain how to put things right. Nothing changes the page unexpectedly when you move through a form or press a key.
07Robust: working with the tools you use
The pages are built with standard code so that browsers and assistive technology can understand them now and later.
We use standard, valid markup, proper names and roles for interactive parts and no hacks that confuse assistive technology. That makes the site more likely to keep working as browsers and screen readers change.
08Testing
We check every page on real screen sizes and with assistive technology before it goes live.
Before a page goes live, we test it at phone, tablet, laptop and desktop widths for overflow and overlap, check it with a keyboard and a screen reader and run automated checks for contrast and structure. We repeat the checks whenever a page changes significantly.
What we check
How we check it
When
Layout at four widths
We view each page at phone, tablet, laptop and desktop widths and look for overflow, overlap and clipped text.
Before every page goes live.
Keyboard use
We move through the page using only the keyboard, including forms, menus and expandable sections.
Before every page goes live.
Screen reader use
We listen to headings, links, forms and images with a screen reader.
For new page types and after major changes.
Contrast and structure
We run automated checks for colour contrast, heading order, labels and landmarks.
Before every page goes live.
Enlarged text and page size
We enlarge the text and the page to two hundred percent.
Before every page goes live.
Reduced motion
We switch on the reduced-motion setting and confirm that animation stops.
Before every page goes live.
09Assistive technology and browsers
We design for the combinations most people use, and we try to keep things working beyond them.
This site is designed to work with current versions of the major browsers and with the screen readers and magnifiers built into common operating systems. We test with a keyboard and a screen reader, and we take reports from people who use other tools seriously, because they often find things we miss.
If your combination of browser and assistive technology does not work, tell us which one you use and what happened, and we will investigate.
10Known limitations
A few things are not perfect yet, and we are open about them.
Third-party tools: Some tools we rely on, such as the payment form at checkout and the optional spam-protection challenge on forms, are provided by other companies, and we cannot fully control their accessibility. We choose providers that publish their own accessibility commitments, and we offer another way to complete anything that does not work for you.
Older articles: Some older guides and articles may contain an image that needs a better description, and we correct these as we find them.
Long tables: Wide tables may need horizontal scrolling inside their own container on very small screens, although the table stays reachable by keyboard.
Embedded media: If we embed a video or an interactive element from another provider, its controls follow that provider’s accessibility.
11Alternative ways to reach us
If a form or page does not work for you, we will help another way.
If you cannot use a form on this site, tell us what you need through any route that works for you, and we will find another way to help. We can accept information in a different format, and we are happy to talk through a quote or a project in writing, step by step, at the pace that suits you.
We work in writing because it suits many people who use assistive technology, gives you time to think and leaves a clear record of what was agreed.
12Report a barrier
Tell us about any accessibility problem, and we will respond within five working days.
If you find something that is hard to read, reach or use, please tell us through the contact form and choose “Something else”. Include the page, what you were trying to do and the device or assistive technology you were using.
Step
What happens
When
1. You report it
You tell us what happened, on which page and with which device or assistive technology.
Whenever you meet a barrier.
2. We confirm
A person confirms in writing that we received your report.
Within one working day.
3. We reply with a plan
We tell you what we found, what we will change and when, or what we can do for you in the meantime.
Within five working days.
4. We fix it
We fix the problem as quickly as we can and tell you when it is done.
As soon as possible, and we keep you updated.
13If you are not satisfied
You can take your concern further if our answer does not solve the problem.
We would always like the chance to put a problem right first. If you are not satisfied with our reply, you can contact the body that enforces accessibility rules where you live. In the European Union that is usually a national authority for the Web Accessibility Directive or the European Accessibility Act, in the United Kingdom it is the Equality Advisory and Support Service, and in the United States you can contact the Department of Justice or the relevant state agency. Rules and routes differ by country and may not apply to every business.
14Keeping this statement current
We review it regularly and update it when we improve the site.
We review this statement and our accessibility testing regularly, and we update the statement when our practices or our site change. The date at the top shows the last review. For how we handle data on this site, see the privacy policy.
Our commitments
Six commitments behind this accessibility statement
A statement is only worth something if the habits behind it are real. These are the habits we hold ourselves to.
We test before we publish
Every page is checked at four screen widths, with a keyboard, with a screen reader and with automated tools before it goes live.
We write plainly
We use plain English, explain terms the first time we use them and keep headings and labels clear and consistent.
We respect your settings
Reduced motion, text size, enlarge and colour preferences are respected, and nothing depends on animation.
We listen to reports
We take every report of a barrier seriously, confirm it within one working day and reply with a plan within five.
We are honest about gaps
We list what we know is not perfect, and we do not claim a standard we have not met.
We keep improving
We review this statement and our testing regularly, and we fix problems as soon as we find them.
WCAG at a glance
The four WCAG principles and what we do for each
Every WCAG success criterion belongs to one of four principles, so this table shows how our work maps to them.
Principle
What it means
What we do on this site
Perceivable
Information must be presented in ways people can perceive.
Strong contrast, resizable text, text alternatives for meaningful images and no meaning carried by colour alone.
Operable
People must be able to operate the interface.
Full keyboard use, visible focus, large touch targets and no time limits that cannot be extended.
Understandable
Information and operation must be understandable.
Plain language, consistent navigation, labelled forms and helpful error messages.
Robust
Content must work with current and future tools.
Standard markup, proper names and roles and testing with assistive technology.
Devices
How the site adapts to your screen
Accessible also means usable on the device in your hand, so here is how the layout changes from a phone to a desktop monitor.
Screen
How the layout behaves
What stays the same
Phone
Content sits in a single column, cards stack one per row and tables reflow so that each cell keeps its label.
Text size, contrast, headings and every feature.
Tablet
Cards sit two to a row and the contents list becomes a collapsible panel.
Text size, contrast, headings and every feature.
Laptop and desktop
Cards sit three to a row and the contents list stays beside the text as you read.
Text size, contrast, headings and every feature.
At every size the page can be enlarged, the text can be enlarged and nothing is hidden because the screen is small.
Questions
Common questions about accessibility on this site
Ten short answers to what visitors ask about using this site. If yours is missing, ask it through the contact form and a person will answer within five working days.
Which standard do you follow?
We aim for WCAG 2.2 level AA, the current widely used standard for web accessibility, and we test pages against it before they go live.
Can I use this site with a screen reader?
Yes, pages use headings, landmarks and labelled forms so that screen readers can move around and complete tasks. If you find something that does not work, please tell us.
Do the animations cause problems?
Animations are gentle, nothing flashes and they stop when your device asks for reduced motion. The page works exactly the same without them.
What if a form is hard for me to use?
Tell us through any route that works for you and we will take your details another way. We are happy to handle a quote or a question step by step in writing.
How do I report a problem?
Use the contact form and describe the page and the problem. We confirm within one working day and respond within five.
Does the site work when I enlarge it to 200 percent?
Yes, pages stay usable when you enlarge the text and the page to two hundred percent, and they reflow without sideways scrolling.
Can I use the keyboard only?
Yes, everything you can do with a mouse you can do with a keyboard, and the focus indicator shows where you are.
Are the checkout and spam-protection tools accessible?
They are supplied by other companies, so we cannot fully control them. We choose providers that publish accessibility commitments and offer another way to complete anything that does not work for you.
Do you test with real assistive technology?
Yes, we use a keyboard and a screen reader as well as automated checks, and we take reports from people who use other tools seriously.
How often is this statement updated?
We review it regularly and update it when our practices or our site change. The date at the top shows the last review.
Related
Related pages for accessibility
Our policies are written to work together. These are the ones most often read alongside the accessibility statement.
Tell us what happened and we will fix it. Your report helps every visitor who comes after you, and a person replies in writing within five working days.