VCOSH — Virtual Center of Occupational Safety and Health Services
Pre-launch draft — accessibility audit in progress

Legal

Accessibility statement

vCosh is built so every employee in your workforce can use it — regardless of language, ability, or assistive technology. We target WCAG 2.2 Level AA conformance across every public and authenticated surface.

Last updated: 14 May 2026

Visual

High-contrast palette (AA on all body text, AAA on headlines). Resizable text up to 200% without loss of content. No motion-only signals.

Auditory

Captions on every video. Transcripts available for all training content. Audio cues paired with visual feedback.

Motor

Full keyboard navigation with visible focus rings. Touch targets at least 44×44 px. Drag interactions always have a non-drag alternative.

Cognitive

Plain-language copy in 9 languages. Consistent layout patterns. Clear error messages with recovery paths. No hidden time limits.

1. Standards we follow

We design and build vCosh to conform with:

  • WCAG 2.2 Level AA across the web app, PWA, and the Client Admin Portal.
  • ARIA Authoring Practices Guide for interactive widgets (menus, dialogs, tabs, accordions).
  • EN 301 549 for procurement-grade conformance with our enterprise customers.

2. What we have implemented

  • Semantic HTML5 landmarks (header, nav, main, footer) on every page.
  • Skip-to-content link as the first focusable element on each page.
  • Form fields have explicit labels, helper text, and inline error messages linked via aria-describedby.
  • Focus order is logical and matches reading order in both LTR and RTL.
  • Colour is never the only signal of state — icons or text accompany every status.
  • Animations honour prefers-reduced-motion.
  • Live-region announcements for asynchronous events (toast notifications, content loaded).
  • Right-to-left layouts use logical properties so margins, padding, and icon placement flip correctly.
  • Video player supports captions in 9 languages, transcript download, and speed control without mouse.

3. Languages supported

The interface is available in Arabic, English, Hindi, Bengali, Filipino, Bahasa Indonesia, Sinhala, Amharic, and Urdu. Each language uses a script-appropriate font stack tuned for legibility (Inter, IBM Plex Sans Arabic, Noto Nastaliq Urdu, Noto Sans Devanagari, Noto Sans Bengali, Noto Sans Sinhala, Noto Sans Ethiopic). Two right-to-left scripts (Arabic, Urdu) are first-class.

4. Known limitations

Our current self-audit has identified the following gaps. We are actively working on them:

  • The community feed’s emoji picker is not yet keyboard-navigable.
  • Some specialist-consult diagnostic preview screens lack alternative text for diagnostic images. Specialists currently provide a written description in the post-session notes.
  • The AI assistant’s streaming response indicator does not yet announce to screen readers in real time; a final summary announcement fires when streaming completes.

We track these in our public roadmap and will update this page as each is resolved.

5. How we test

  • Automated axe-core scans on every pull request.
  • Manual keyboard-only run-through of every primary flow.
  • Screen-reader testing with NVDA, JAWS, VoiceOver, and TalkBack.
  • Quarterly third-party WCAG audit by a registered accessibility consultancy.
  • Feedback channels open to every user (see below).

6. Tell us if something is broken

If you encounter an accessibility barrier in vCosh — anything from a tiny hard-to-read label to a flow you cannot complete — please tell us. Email accessibility@vcosh.sa with a description and we will reply within five business days. If you need a faster response, ask your administrator to escalate via their Customer Success channel.

We treat accessibility reports as bugs, not feature requests.