Company Logo

Accessibility

TRUZH is committed to being usable by everyone. We build to WCAG 2.1 AA standards and treat accessibility as an ongoing practice, not a checkbox.

Back

Our accessibility statement

We believe everyone deserves access to a safe, trusted marketplace regardless of disability, device, or circumstance. Accessibility is not a feature we add at the end. It is part of how we design and build every part of TRUZH. We audit our platform regularly and fix issues as quickly as we can.

Standards

Standards we follow

WCAG 2.1 Level AA

Our design and engineering target for all new features.

Target compliance

WCAG 2.1 Level AAA

We meet AAA criteria where feasible without impacting usability.

Partial

EN 301 549

EU accessibility standard for public sector ICT, applied where applicable.

In progress
Our commitments

What we are doing

Our current accessibility commitments across the TRUZH platform.

Keyboard navigation

All core flows: browsing, listing, messaging, and checkout are fully usable with a keyboard alone. Every interactive element has a clear, visible focus indicator.

Sufficient colour contrast

Text and interactive elements meet or exceed WCAG 2.1 AA contrast requirements (4.5:1 for normal text, 3:1 for large text) across both light and dark themes.

Screen reader support

We use semantic HTML, ARIA labels, and live regions to ensure TRUZH works well with NVDA, JAWS, VoiceOver, and TalkBack. Images have descriptive alt text.

Touch and pointer accessibility

Touch targets are at minimum 44x44px. The app works with pointer devices, styluses, and switch access. Swipe gestures have alternative keyboard and button equivalents.

Responsive and zoom-friendly

Content reflows correctly at up to 400% zoom without horizontal scrolling. All layouts are responsive and tested from 320px screens to 4K displays.

Mobile accessibility

The web app is tested with iOS VoiceOver and Android TalkBack. Dynamic type and large text modes are respected throughout the interface.

Clear error handling

Form errors are identified clearly with text descriptions, not colour alone. Error messages are linked to the field they relate to and suggest how to fix the problem.

Plain language

We write in plain language wherever possible. UI copy, error messages, and help content aim for a reading level accessible to the widest possible audience.

Report an accessibility issue

If you encounter a barrier using TRUZH, please tell us. We take every report seriously and commit to acknowledging reports within 2 business days and providing a resolution timeline.

accessibility@truzh.com

Please include:

  • What you were trying to do and what happened
  • Your device, operating system, and browser
  • The assistive technology you were using (if any)
  • A URL or screenshot of the affected page