Accessibility

This statement covers two separate things: this documentation website, and the filter bar the Filter My Blog app places on a merchant's storefront. Both are built with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA as the target standard.

This website

• Every page has a single, descriptive heading and a logical heading structure.
• All interactive elements are reachable and operable by keyboard, with a visible focus indicator that is never removed.
• A "skip to content" link is provided on every page.
• Colour is never the only way information is conveyed; status and state changes are also described in text.
• The search dialog and mobile menu are built on native, accessible browser primitives (<dialog>, <details>) rather than custom re-implementations, so focus handling and keyboard behaviour follow platform conventions.
• Motion is reduced or removed for visitors who set a reduced-motion preference in their operating system.

The storefront filter bar

The block a merchant adds to their blog is built to remain usable without relying on any single sense or input method:

• Every tag is a real link with a visible focus state, operable entirely by keyboard, and works with JavaScript disabled. See How filtering works on the storefront.
• Screen reader labels are provided for the filter bar, the search box, and result counts, and are among the wording a merchant can customise. See Wording and translations.
• Content updates made without a page reload (instant filtering and search, where a theme supports it) are announced to assistive technology so a result count change isn't silent.
• Merchants control every colour used in the bar, which puts the final responsibility for sufficient colour contrast in merchant hands. The app doesn't enforce a specific palette, since matching a theme's own colours is often the point.

Feedback

If you encounter an accessibility barrier on this site or on a storefront using the filter bar, we want to know. Please use the contact form, naming the page or feature involved, and we'll look into it.