Xoxoday: Accessibility Mode or Alternate Interface

​

Built-In Accessibility, Not a Separate Mode

Xoxoday builds accessibility into its core interface rather than routing users through an alternate experience. There is no “accessibility mode” toggle, no lite version, and no AI-generated overlay that users must activate to navigate the platform. Every page in the application ships with the appropriate WAI-ARIA landmark roles, labels, and attributes so that screen readers and other assistive tools can parse content without requiring a parallel interface. This approach matters for enterprise IT teams because segregated accessibility modes often lag behind the main product in updates and security patches. Xoxoday’s method ensures that all users — regardless of ability — interact with the same tested, maintained, and secured codebase.

​

How ARIA Tags Work in Xoxoday

WAI-ARIA is a W3C specification that tells assistive technologies — screen readers, voice-control software, and refreshable Braille displays — the role, state, and properties of interface elements. Xoxoday annotates its pages with these tags natively, meaning a screen reader querying a rewards dashboard or a recognition feed receives structured, meaningful markup rather than raw HTML. This is distinct from overlay tools or JavaScript widgets that inject accessibility attributes after the page loads. Such overlays introduce additional dependencies, potential conflicts with browser extensions, and inconsistent behavior across devices. Xoxoday avoids this pattern entirely.

​

Plugin and Assistive Technology Support for End Users

While Xoxoday does not bundle its own accessibility plugin, the application is built to work with the plugins end users already have installed. Whether a team member in your organisation uses a screen reader such as NVDA or JAWS, a browser extension for high-contrast display, or a keyboard-navigation enhancement tool, Xoxoday’s ARIA-tagged interface provides the underlying structure those tools depend on. For organisations deploying Xoxoday alongside enterprise platforms such as SAP SuccessFactors, Darwinbox, or Workday, this means IT administrators do not need to configure a separate accessibility environment or maintain a secondary access path. The same interface served to the full user population is the accessible interface.

​

Security and Compliance Alignment

Xoxoday’s accessibility approach is consistent with its broader security and compliance posture. Maintaining a single, audited interface — rather than a branched alternate mode — reduces the attack surface and simplifies the scope of reviews conducted under frameworks such as ISO 27001 and SOC 2 Type II. IT and security teams evaluating Xoxoday can assess one interface and one codebase, without accounting for divergent behavior in a separate accessibility layer. Learn more: Xoxoday Help Centre — IT Requirement