Accessibility Statement
Salaaz is built to be usable by people with the broadest range of abilities. WCAG 2.2 AA is our target; this page records where we meet it, where we know we fall short, and how to tell us when we have.
Effective May 22, 2026.
1. The commitment
Salaaz Marketplace Inc. is committed to providing a platform that meets the WCAG 2.2 Level AA success criteria. Accessibility is not a bolt-on; the brand spec itself bakes the contrast bar in (the affordance vocabulary used across every page is calibrated so that interactive state changes meet WCAG 1.4.11's 3:1 minimum). When we make a design decision that has accessibility consequences, we document the reasoning in our design system.
2. What works today
- Keyboard navigation. Every interactive control is reachable and operable from the keyboard alone. Focus is visible (a 3px leaf-green ring) on every focusable element.
- Screen-reader landmarks. The platform uses semantic HTML (
main,nav,article,aside) so assistive technology can navigate by region. - Text contrast. Body text meets AA at minimum and AAA for primary text (ink-1 on paper-1 reads at 14.8:1). The brand spec rules out colour combinations that would not meet the bar.
- Reduced-motion respect. All animation honours the
prefers-reduced-motionmedia query; brand motion (the loader emblem, hover transitions, page fades) is suppressed when the system signal is set. - Touch targets. Mobile interactive surfaces are at least 44×44px (WCAG 2.5.5); desktop targets are at least 36×36px.
- Image alt text. Product images carry vendor-supplied alt text; editorial images carry captions per the brand spec's imagery policy.
- Form validation. Errors are announced to screen readers via
aria-live; required fields are marked both visually and in the accessible name. - Language declaration. The interface language is declared in the
langattribute and updates when you switch.
3. Known limitations
We are honest about what we have not yet finished. The following areas do not currently meet our target; they are tracked and have owners:
- Vendor-supplied imagery alt text is sometimes thin or missing. Our submission flow now requires alt text on new uploads, but historical uploads are being backfilled.
- The mobile mega-menu uses a drawer pattern that has been audited but not yet re-tested with screen readers under iOS 17 Safari. Re-test scheduled.
- Third-party embeds we rely on each have their own accessibility posture: the authentication surface (Clerk), the payment surface (Square Web SDK), and the newsletter signup (Beehiiv). We have replaced the iframe-style Beehiiv subscribe with a native form; Clerk and Square are being driven through their accessibility certifications.
- Editorial article inline tables are accessible but not yet keyboard-resizable; long tables on small screens require horizontal scroll.
- Right-to-left layout support is in progress; Arabic and Persian users currently get a partially-flipped layout. Full RTL parity is a v3 commitment.
4. Standards we test against
- WCAG 2.2 Level AA, all success criteria.
- EN 301 549 (European harmonized standard for ICT accessibility).
- Section 508 (US federal procurement standard, harmonized with WCAG 2.0 AA and the supplemental criteria in WCAG 2.1/2.2 we elect to honour).
- AODA Integrated Accessibility Standards Regulation (Ontario), §14.
5. Assistive technology we test with
We test on a rotating combination of: VoiceOver (macOS Safari, iOS Safari), NVDA (Windows Firefox and Chrome), JAWS (Windows Chrome), TalkBack (Android Chrome), keyboard-only navigation, and at zoom levels up to 200%. Not every release passes every combination; we record the gaps in section 3 above.
6. How to report a barrier
If a part of the platform is not usable for you, please tell us. We treat accessibility reports as higher-priority than feature requests, and we acknowledge every report within two business days. Include (if you can): the page or surface, what you were trying to do, the assistive technology and browser you were using, and what happened.
Accessibility contact
general@salaaz.com
7. Statutory channels
If you would prefer to escalate outside Salaaz, the following channels apply by jurisdiction:
- Ontario, Canada: the Accessibility Directorate of Ontario, under the AODA.
- Other Canadian provinces: the provincial human-rights commission with jurisdiction over goods, services, and accommodation.
- United States: the Department of Justice (ADA Title III) for places of public accommodation.
- EU/EEA member states: the body designated under your member state's transposition of the European Accessibility Act.
8. Updates to this statement
We update this statement when our conformance posture meaningfully changes: when known limitations are fixed, when new ones are discovered, or when a new release substantially affects the accessibility surface. The effective date at the top reflects the current version.