Accessibility at SlapSwap

We want SlapSwap to be usable by as many collectors as possible, including people who navigate with a keyboard, use a screen reader, rely on larger text, or prefer reduced motion. We build toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as our working standard for new work.

Accessibility is ongoing, not a finish line. This page describes what is in place today and, just as importantly, where we know we fall short, so you can tell what to expect and hold us to it.

Across the product, we build to these practices:

• Keyboard operability. Interactive controls are reachable and operable with the keyboard, with a visible focus outline. Dialogs trap focus while open and return it to the control that opened them when they close.
• Semantic structure. Pages use real landmarks and a single, ordered heading outline so screen-reader users can navigate by region and heading.
• Reduced motion. When your system asks for reduced motion, our animations collapse to an instant state change, and smooth-scrolling is turned off. app-wide, not screen by screen.
• Text and layout. Layouts are responsive and reflow when text is enlarged. tap targets on primary actions are sized for touch.
• Forms and labels. Form fields carry labels, and errors are shown in text, not by colour alone.
• Colour and contrast. Our palette targets AA contrast for body text and essential UI.

We would rather name these than imply the product is finished. Known limitations as of the last review:

• We have not yet had an independent accessibility audit, and there is no formal conformance report (VPAT) yet.
• Member-supplied content, including listing photos, avatars, and posts, may lack complete alternative text where a member didn't provide it.
• Some image- and camera-heavy surfaces (the scanning flow and the visual binder) are still being reviewed for full AA behaviour with assistive technology.
• We can't warrant the accessibility of third-party content we link out to, or documents produced by external services.

New surfaces are built to the practices above by default. Keyboard operability, visible focus, managed focus in dialogs, reduced-motion support, and a checked heading outline are considered from the start rather than retrofitted later. When we find a gap, we treat it as a defect to fix, not a preference.

If something on SlapSwap is hard or impossible to use with your setup, we want to know. It helps us prioritise the fix. Please reach us through Share feedback and tell us the page, what you were trying to do, and the assistive technology or setting you use.

We read every report. We won't promise a turnaround we haven't committed to, but accessibility barriers are triaged as defects.