Accessibility statement
We want Fancy Pet to be usable by everyone. Here's where we are and where we're going.
Last updated · 2026-06-01
Our commitment
Fancy Pet is committed to making fancy.pet accessible to people with disabilities. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We don't claim to be perfectly conformant today, but we treat accessibility issues as bugs and fix them.
What works well
- Semantic HTML throughout. Proper headings, landmarks (
<main>,<nav>,<footer>), and form labels. - Keyboard navigable across the purchase flow. Buttons, links, inputs, and the currency picker are all reachable via Tab and operable with Enter/Space.
- High-contrast text on the primary cream/ink palette. On the main pages, coral buttons and small coral text use a deeper coral that meets the 4.5:1 contrast ratio; the bright coral is kept for large headings and decoration.
- All form inputs have associated labels (visible or screen-reader only). The pet-name input announces validation errors via
aria-describedbyandrole="alert". - Image alt text on generated portraits and product mockups describes the content; decorative images use empty alt to skip screen-reader announcement.
- Modal dialogs (size guide, download unlock) trap focus and close on Escape.
Known issues we're working on
We're honest about where we're not yet at AA. If you hit anything below or anything else, please tell us, we'll fix it.
- The colour-swatch buttons on product pages are 38×38 px on mobile, slightly below the WCAG 2.5.5 target-size recommendation of 44×44. We're increasing this next release.
- The homepage, the looks and our landing pages honour
prefers-reduced-motion; a few transitions on the gallery and product pages don't yet. We're working through them. - The polaroid-tilt visual on the gallery and reveal pages uses CSS transform; it has appropriate ARIA but the tilt itself can't currently be disabled. Reduced-motion users see the rotation regardless.
What we design for
- Screen readers: VoiceOver (macOS, iOS) and NVDA (Windows)
- Keyboard-only use, with a visible focus outline
- Browser zoom up to 200%, and text of at least 16px on phones
- Buttons at least 44px tall, so they're easy to tap
- Your device's “reduce motion” setting: moving pictures stop
How to report issues
If you encounter an accessibility barrier, email us at accessibility@fancy.pet. Please describe the page, what you were trying to do, and what assistive technology (if any) you were using. We respond within five working days and aim to fix verified issues within 30 days, faster for critical blockers.
If you're a customer who couldn't complete a purchase because of an accessibility issue, contact us at the email above and we'll help you place the order directly.
Standards and formal assessment
We perform automated accessibility scans on every deploy using axe-core and address violations as they appear. We have not yet commissioned an independent third-party audit; we plan to once feature velocity slows post-launch.