Accessibility

Our target

We aim to meet WCAG 2.2 Level AA. That is the standard we design and test against, and we treat a failure against it as a defect rather than a nice-to-have.

What is in place

• Text size. Body text starts at roughly 17px and grows with the viewport. Nothing prevents you from zooming, and the layout reflows to 400% zoom without a horizontal scrollbar.
• Contrast. Every text and background pairing used on the site is checked against WCAG contrast ratios by an automated test that must pass before any change is merged into the live site. Most pairings exceed AA and reach AAA.
• Keyboard. Everything that can be clicked can be reached and operated with a keyboard, in a sensible order, with a clearly visible focus outline. A “skip to main content” link is the first thing you reach on every page.
• Structure. Pages use real landmarks — header, navigation, main, footer — and headings that descend in order without skipping levels, so a screen reader can navigate by structure.
• Images. Decorative artwork is hidden from assistive technology rather than described pointlessly. Images that carry meaning have text alternatives.
• Links. Link text describes its destination. Links that leave the site say where they go.
• Motion. There is very little animation, and what exists is switched off when your system asks for reduced motion.
• Targets. Buttons, menu items and form controls are at least 44 × 44 pixels.

How we test

• Automated checks with axe-core run against every built page in our continuous integration; a failure blocks the change from being merged.
• A contrast test asserts every color pairing in the design system before the site builds.
• Manual keyboard-only passes and responsive review at phone, tablet and desktop widths, plus 400% zoom.

What we know is not perfect

• We have not yet completed a full manual audit with screen-reader users on VoiceOver, NVDA and JAWS. That is planned rather than done, and we would rather say so than imply a level of testing we have not reached.
• External stores, such as Etsy, are outside our control, and we cannot make claims about their accessibility.
• Our downloadable kits are separate files, not part of this website, and they are not covered by the automated checks that run on it. If one is hard to use with your setup, tell us.

Telling us about a barrier

If something on this site is hard or impossible to use, please tell us. A one-line email is enough — what page, and what happened. We treat these as bug reports and reply.

Email support@fayzainmedia.com, or see our contact page.

If it is easier, describe the problem in whatever way suits you. You do not need to know the name of the standard it breaks.