Accessibility

Our commitment

The Collective is built for a disabled community, so accessibility isn’t an afterthought — it’s part of how we design and build every page. We use the WCAG 2.2 AA success criteria as our practical working target, checked and improved by hand rather than through automated certification — so this page describes what’s actually implemented, not a formal compliance claim.

Keyboard navigation

Every link, button, form field and interactive control on this site — including the navigation menu, publication readers and carousels — can be reached and operated using a keyboard alone, with a visible focus outline showing where you are at all times, even against the site’s darker teal sections.

Carousels you can pause

The homepage and Explore carousels rotate automatically, but each has its own play/pause control, and rotation stops automatically while you’re hovering, focused on, or touching it — it never keeps moving underneath you.

Readable contrast

Text and interactive elements are designed to meet strong colour contrast against their backgrounds, and important information — including which page or option is currently selected — is never conveyed by colour alone.

Reduced motion

If your device or browser is set to reduce motion, animations and transitions across the site — including the homepage’s opening welcome and hero carousel — are shortened or removed automatically, rather than played in full.

Responsive and mobile support

The site is designed to work on phones, tablets and desktop screens down to 320px wide, with layouts that adapt to the available width and text size rather than requiring horizontal scrolling.

Reporting a problem

If you come across anything on this site that’s difficult to use or access, please let us know — we’d genuinely like to hear about it. You can get in touch via our Contact page, or email us directly at hello@thecollectivebedsmk.org.uk.

Ongoing work

The Collective is still growing, and this site is a work in progress. We’re continuing to review and improve its accessibility as we build — this page describes our current approach and intentions, rather than a claim of formal compliance with a specific accessibility standard.

Last reviewed: August 2026.