Accessibility

We build My Card Wizard to meet WCAG 2.1 Level AA.

We do not claim that we fully meet it. No third-party audit has been done. This page says what has been checked and by whom, so you can judge it for yourself.

Checked on 17 September 2026 against the live app, by reading the code and by using the pages in a browser.

Colour contrast. Body text runs at 16.8 to 1 against the page background. The lowest-contrast text colour in the app is the green that marks a good result, at 6.0 to 1, so every text colour clears the 4.5 to 1 floor and large text clears its own 3 to 1 floor. Where text sits on a gradient, the whole sweep is measured rather than the midpoint.

Images. Every image carries alternative text, and a build check fails on one that does not. An image that only decorates carries empty alternative text, so a screen reader passes over it.

Keyboard. Every page starts with a Skip to content link. Focus is always visible, and it is a ring rather than a colour change alone.

Structure. Headings, lists, navigation and main content are real HTML landmarks, so a screen reader can move by structure. Anything that reads as a table announces as a table, including its sort state.

Motion. Animation stops for anyone whose system asks for reduced motion, and that is enforced in the components rather than only in a stylesheet.

Language. Every page declares that it is in English.

No formal audit. Nothing here has been verified by an accessibility specialist or tested with people who rely on assistive technology.

The card intake flow has not been walked end to end with a screen reader. It is the longest and most interactive part of the app, and it is the next thing we will check.

Form errors are shown visually and marked as alerts, but we have not confirmed that every one is announced at the moment it appears.

Focus handling inside dialogs has not been fully verified. A dialog should hold focus while it is open and return it to the control that opened it.

The batch review screen is dense, because it is built for someone working several hundred cards in one sitting. We have not yet settled where the line between density and clarity should sit.

Email support@mycardwizard.com. Say what page you were on, what you were trying to do, and what happened instead. If you use a screen reader, a magnifier, voice control or anything else, tell us which one and which browser.

You do not need to know the standard or use the right words for it. A plain description of what you could not do is the most useful report there is.

We read every one and we tell you what we found. There is also a Feedback tab inside the app, which reaches the same people.

Two of the claims in section 2 are pinned by automated tests that run before every release. A page that ships without a Skip to content link fails the build, and so does an image with no alternative text.

The rest of section 2 was checked by hand on the date it names. Section 3 is updated whenever one of its items is fixed or a new one is found.