ONSET

ACCESSIBILITY · WCAG 2.1 LEVEL AA TARGET

We build to WCAG 2.1 Level AA — and tell you where we're not there yet.

Most accessibility statements are aspirational. This one is dated and honest. The list of what works comes from the codebase, not from a marketing brief. The list of gaps comes from real reports plus our own audits.

We treat accessibility issues with the same severity as security issues. A reported barrier preempts feature work.

OUR STANDARD

WCAG 2.1 Level AA, applied across both surfaces.

Applied to onset.my and the authenticated app at app.onset.my. We follow the published Success Criteria; we don't pick and choose. Where we currently fail a criterion, it's listed in "Known gaps" below with the quarter we plan to close it.

WHAT WORKS TODAY · 10 ITEMS

The current baseline.

  • Semantic HTML — every section uses native <header>/<nav>/<main>/<article>/<footer> with one <h1> per page

  • Site-wide :focus-visible ring on every interactive element (WCAG 2.4.7)

  • prefers-reduced-motion respected globally — animations clamp to ~0ms when OS preference is set (WCAG 2.3.3)

  • Pinch-zoom permitted — maximum-scale removed from viewport meta (WCAG 1.4.4)

  • html lang="en-MY" on every page. BM, Mandarin and Tamil strings carry inline lang attributes as translations ship

  • Colour contrast on body text ≥ 4.5:1; on UI controls and large text ≥ 3:1 (WCAG 1.4.3)

  • Keyboard navigation across forms, modals, sidebars, and the dashboard tab bar. Tab order matches visual order

  • Focus trapping inside modals; Esc closes any open overlay

  • Form fields paired with their labels via htmlFor/id on the marketing surface (WCAG 1.3.1)

  • Icon-only buttons carry aria-label; decorative icons carry aria-hidden="true"

KNOWN GAPS · 6 OPEN

What we haven't fixed yet — and when we will.

Every gap below is dated with the quarter we're committing to close it. If you hit one of these and need it sooner, email and we'll prioritise.

  • Dashboard form labels not all programmatically linked

    FIX · Q3 2026

    Some authenticated routes (/cold-email/new, parts of /sales/new) carry visible labels without htmlFor.

  • Icon-only buttons in dashboard missing aria-label

    FIX · Q3 2026

    A handful of icons in deep dashboard surfaces need the sweep.

  • No formal screen-reader pass yet

    FIX · Q3 2026

    VoiceOver (iOS/macOS) and NVDA (Windows) walk-throughs scheduled. We'll publish the report on this page when the audit closes.

  • Some chart visualisations lack text alternatives

    FIX · Q4 2026

    Underlying data is available in tables; the chart-only summary is a 1.1.1 gap.

  • Mobile layout on some admin drill-downs needs work

    FIX · Q3 2026

    Forms can require horizontal scroll at 375px width on screens built before March 2026.

  • High-contrast / Windows forced-colors mode

    FIX · Q1 2027

    We pass automated checks but haven't hand-tested.

HOW TO FLAG A BARRIER

If something is hard or impossible for you, tell us.

The fastest path is an email to accessibility@onset.my with a brief description and (if you can) the page URL and a screenshot. We respond within 5 working days; severe blockers jump to the front of the queue.

We also welcome feedback that isn't a complaint — if you use assistive tech and have suggestions, we read every email Reginald gets and respond.

Our commitment.

ONSET should work for blind, low-vision, deaf, hard-of-hearing, motor-impaired, and cognitively-disabled users. Full third-party audit against WCAG 2.1 AA is queued for Q1 2027. The auditor and full report will be linked here when complete.

LAST REVIEWED · 06 July 2026 · NEXT REVIEW · QUARTERLY