Accessibility

Conformance

yellowimp.com conforms to WCAG 2.2 Level AA. That’s the current version of the international accessibility standard, and Level AA is the level regulators and courts generally point to. I assessed the site against it on 21 August 2026 and there are no known failures.

The assessment was my own, using industry-standard tooling and manual testing. The standard allows for self-assessment.

If anything here blocks you, you can still order

This matters more to me than the paragraph above. If any part of this site stops you buying something, email me and I’ll take the order that way and sort out payment and delivery by hand. You don’t need to explain yourself or prove anything. Same products, same prices, same shipping. I aim to reply within two business days.

How I tested

I ran axe-core across 16 page types, at a phone size and a desktop size, against the full WCAG 2.2 AA rule set. Then I checked what a tool can’t judge on its own:

• Tabbing through pages to confirm focus stays visible, never gets stuck, and never ends up hidden behind the header.
• Narrowing the window to 320px, the smallest width the standard covers.
• Doubling the text size, and separately applying the text-spacing overrides the standard asks a site to survive.
• Reading the accessibility tree, which is what a screen reader is actually handed, to confirm every control has a name and a role.
• The criteria added in WCAG 2.2: target sizes, focus not obscured, dragging alternatives, consistent help, no redundant entry at checkout, and no cognitive puzzle standing between you and your account.

The first run found nine problems, five of them failures against the standard. All nine were fixed the same day and the assessment re-run clean. It now returns nothing on either screen size, and it runs again before anything ships.

What that means in practice

• Keyboard. Every menu, filter, gallery and cart control works without a mouse. Focus is always visible with a high-contrast outline, nothing traps you, and nothing hides behind the sticky header when it takes focus. Menus and dialogs close on Escape and report their state to assistive tech.
• Screen readers. Every control has a name and a role. Headings form a real outline, one main heading per page. Landmarks are labelled, so you can jump between regions. Product images carry alt text naming the miniature.
• Voice control. Where a control has a spoken label, it matches what you see on screen, so saying the words on the button works.
• Colour contrast. Every text and interface colour pair is measured rather than eyeballed. All meet AA and most clear the stricter AAA level.
• Touch and pointer. Every button, link and checkbox is at least 24 by 24 pixels. Nothing needs a drag to operate.
• Small screens and big text. The site fits a 320px phone with no sideways scrolling, and doubling the text size doesn’t break the layout.
• Reduced motion. If your system asks for less animation, the drifting embers stop, hover effects hold still and transitions switch off.
• Forms. Every field has a real label, not placeholder text in the box. Checkout fields tell your browser what they’re for, so autofill and password managers work. Errors are announced to assistive tech rather than signalled only by turning something red. You’re never asked for the same thing twice.
• No interruptions. Nothing covers the page uninvited, nothing autoplays, there’s no carousel on a timer, and there’s no video or audio anywhere on the site.

What this statement covers

It covers yellowimp.com as it stood on the date below. It doesn’t cover content served by someone else, such as a payment provider’s checkout window, because that isn’t my code. I keep third-party content to a minimum on purpose.

An assessment is a snapshot. I re-run the full check before any change goes live, but if something slips between runs, the email route above is how you get around it and how I find out.

Tell me if something’s wrong

If something here blocked you or made it harder than it should have been, send me a message. Tell me what you were trying to do, what page you were on, and what browser or assistive tech you were using if you know it. It comes to me, not a ticket queue.

I aim to reply within two business days, and I’ll tell you either when it’s fixed or why it’ll take longer. If I’ve not come back to you, send it again and say so. I’d rather be chased than let it sit.

You shouldn’t have to fight a website to give someone money.

Assessed 21 August 2026 against WCAG 2.2 Level AA. Re-checked before every release.