What works, and what we know does not

We aim to meet Web Content Accessibility Guidelines 2.2 at level AA across this website, the checkout, and the customer account area.

We treat that as a target we are working towards and testing against, not a badge. This page says where we are, and we update it when that changes.

• Semantic HTML with a single logical heading order per page, and landmarks for navigation, main content and footer
• Every interactive control reachable and operable by keyboard alone, in a sensible order, with a visible focus indicator that meets the 3:1 contrast requirement
• Text contrast of at least 4.5:1, and 3:1 for large text and interface components, checked against the palette rather than assumed
• Form fields with real labels, errors announced in text next to the field rather than by colour alone, and no reliance on placeholder text as a label
• Dialogs and menus built on tested primitives that manage focus, trap it while open, restore it on close and respond to Escape
• Content that reflows to a 320 pixel viewport without horizontal scrolling, and remains usable at 200 per cent zoom
• Motion limited to short transitions, and reduced or removed for visitors whose system requests reduced motion
• No content conveyed by colour alone, and no auto-playing audio or video

The product itself includes a full transcript for every call, which means voice interactions have a text equivalent by design rather than as an add-on.

We would rather list these than let you discover them.

• Formal audit — this statement is based on our own testing with keyboard, screen reader and zoom, not on an independent third-party audit. We have not yet commissioned one.
• Analytics charts — dashboard charts convey trends visually. Each has an accessible data table, but the charts themselves are not fully described to a screen reader.
• Complex data tables — some admin tables scroll horizontally on narrow viewports, which is usable but not comfortable.
• Product documentation — hosted documentation has had less accessibility attention than the site and checkout.
• PDF invoices — generated invoices are not tagged for accessibility. If you need an accessible version of any invoice, ask and we will send the same data as HTML or CSV.

Nothing in this list blocks buying, using or cancelling the product by keyboard or screen reader. If you find something that does, that is a fault and we will treat it as one.

Email billy@falconneststore.com with the page, what you were trying to do, and the assistive technology and browser you were using if you know them.

We acknowledge within two business days and tell you either when it will be fixed or what the workaround is in the meantime. If something blocks you from completing a purchase, cancellation or data request, contact us and we will complete it for you while the fix is in progress — you should not have to wait on our backlog to exercise a right.

If you are not satisfied with our response, you can contact the Equality Advisory and Support Service, which advises on rights under the Equality Act 2010.

This site is built with modern HTML, CSS and JavaScript and relies on WAI-ARIA where native semantics are insufficient. It is tested in current versions of Chrome, Firefox, Safari and Edge, with NVDA and VoiceOver, and by keyboard only.

JavaScript is required for checkout and the account area. Content pages, including every legal page, render and are readable without it.