Contrast auditing
Every colour token is checked against WCAG contrast ratios. If it fails, it doesn’t ship.
Accessibility
Accessibility at LoveSync.
We aim for WCAG 2.1 AA across every surface we ship. This page describes what that means in practice, what’s working, and where we’re still improving.
Our commitment
A living commitment, not a badge.
The people who most need a home for love are often the people the internet has been rudest to. That includes people using screen readers, magnification, keyboard-only navigation, captions, alternative input devices, and dozens of quieter adaptations. Accessibility isn’t a compliance line item for us — it’s the way we reach the members we most want to serve.
Our standard across web and mobile is WCAG 2.1 AA. We test with real assistive tech, not just automated tools. We audit contrast on every ship. We honour reduced-motion. We never convey status by colour alone. Focus is always visible and never lost.
We publish honest status below — including the places we’re not yet where we want to be. If something breaks for you, please tell us. We prioritise fixes over PR.
Where we stand
Honest status, updated as we ship.
Green means live and audited. Amber means work in progress with a real plan.
- 01Live
WCAG 2.1 AA on web
Web surfaces are audited against WCAG 2.1 AA on every release. New components go through an accessibility review before ship.
- 02Live
WCAG 2.1 AA on mobile
iOS and Android builds honour platform accessibility APIs — VoiceOver, TalkBack, Dynamic Type, larger touch targets — and are tested on real devices.
- 03Continuous
Screen-reader testing
We test with VoiceOver on iOS and macOS, TalkBack on Android, and NVDA and JAWS on Windows. Screen-reader-only issues get their own severity track.
- 04Supported
200% zoom & dynamic type
Web scales to 200% without loss of content or function. Mobile honours OS text-size and display-scale settings without capping.
- 05Supported
Reduced-motion honoured
Every animation on the site respects prefers-reduced-motion. Essential information is never conveyed by motion alone.
- 06Never used alone
Colour-only status
Status is always paired with a text label or an icon. This includes verified badges, live indicators, and every semantic dot.
- 07In progress
Captions & transcripts
New audio and video content ships with captions and transcripts. We’re working through the older library to add captions to material recorded before this became standard.
- 08Case-by-case
Third-party embeds
We vet third-party embeds for accessibility before shipping. Where a partner falls short, we work with them, provide alternative access, or replace the embed.
- 09Roadmap
Audio-described video
Audio description is planned for our video series in the coming year. Until then, transcripts describe visual content in full.
How we work
The practices that keep us honest.
Semantic HTML first
Headings, landmarks, lists, and buttons — used for their meaning, not their styling. No div-only interfaces.
Focus never lost
Focus is always visible, always logical, and always managed after modal open, close, and navigation.
Motion never mandatory
Every animation has a reduced-motion fallback. No information is conveyed only by movement.
The practices
What we actually do before we ship.
Keyboard-only testing
Every new flow is walked through with keyboard alone. If it can’t be done without a mouse, it doesn’t ship.
Screen-reader testing schedule
New components are tested with at least two screen readers before ship. Full-app screen-reader audits run each quarter.
Colour-contrast pipeline
Tokens and utility classes are checked against WCAG 2.1 AA ratios in CI. Failing combinations block the build.
Accessibility review before ship
Design and code reviews include an accessibility checklist. Ownership sits with the whole team — not a lone specialist.
Assistive tech we test with
Real devices, real settings.
Screen readers: VoiceOver on iOS and macOS, TalkBack on Android, NVDA and JAWS on Windows. Each screen reader gets its own bug track — issues that only surface in one aren’t hidden inside a general “accessibility” bucket.
Adaptations: iOS Dynamic Type, Android Font Size, browser zoom to 200% and beyond, high-contrast display modes, reduced-motion and reduced-transparency system settings, keyboard-only navigation, and switch control on iOS where possible.
Tell us
Reach us directly.
Report an accessibility issue
Broken keyboard flow, missing labels, low contrast, screen-reader confusion, anything. We prioritise fixes over PR.
[email protected]
Request an alternative format
Need a document or article in a different format — plain text, larger type, described audio? Write and we’ll arrange it.
[email protected]
If we’ve missed something
We want to hear.
We’d rather fix a problem than defend a design. If something on LoveSync gets in your way — on any platform, with any adaptation — please tell us. We reply, we act, and we say when we’ve shipped a fix.
We publish an accessibility changelog alongside our product releases so members can see what’s improved and what’s still open. Progress in the open is the only kind we trust.