A simulation platform for everyone.

We want students and instructors to be able to run a business simulation whatever their ability. This page is our accessibility statement: what the simulations conform to today, the few criteria still open, how they are tested and how to reach us when something blocks you.

Accessibility Conformance Report
Standards covered by the Sage Hubro Accessibility Conformance Report and the conformance levels included for each.
Standard Included in report
WCAG 2.0 Level A and AA
WCAG 2.1 Level A and AA
WCAG 2.2 Level A and AA
Revised Section 508 Yes
EN 301 549 V3.1.1 and V3.2.1
VPAT 2.5 International Edition, updated June 2026

Hubro Business Simulation, the Hubro Marketing simulations and our other simulation products are partially conformant with WCAG 2.2 level AA.

The Web Content Accessibility Guidelines define three levels of conformance: A, AA and AAA. Partially conformant means that some parts of the content do not fully conform to the standard. Four of the Level A and AA success criteria in our conformance report are partially supported; the rest are supported or not applicable. All four are listed below.

Accessibility documentation

Everything a procurement team or a disability services office needs to review the simulations.

Conformance report (VPAT)

The full report for Sage Hubro: every WCAG 2.2 Level A and AA success criterion, the functional performance criteria and the EN 301 549 chapters, each with the conformance level and the evaluator's remarks.

Download the VPAT (PDF)

Alternative formats

Sage can supply this documentation in an alternative format, and holds conformance reports for the other platforms we publish. Ask the Sage online accessibility team.

[email protected]

What conforms today

The June 2026 report walks every WCAG 2.2 Level A and AA success criterion. All but four are recorded as supported or not applicable. This is what that covers.

Screen readers

  • Images, controls and status messages carry text alternatives.
  • Headings, labels and relationships are marked up correctly.
  • Name, role and value are exposed for interactive elements.
  • Page titles and link purpose read correctly in context.
  • Content follows a meaningful reading sequence.

Keyboard and focus

  • No keyboard traps anywhere in the product.
  • Focus order follows the reading order.
  • A focus indicator is shown, and focus is never obscured.
  • Targets meet the minimum size requirement.
  • No character key shortcuts to collide with assistive technology.

Low vision and zoom

  • Browser text resizing and zoom are both supported.
  • Pages reflow at 320 pixels and at 400% zoom without horizontal scrolling.
  • Text spacing can be overridden.
  • Colour alone is never used to carry meaning.
  • Anything shown on hover or focus can be dismissed.

Forms and errors

  • Fields carry labels and instructions, and declare their purpose.
  • Errors are identified in text, with a suggested correction.
  • Submissions that commit data can be reviewed or reversed.
  • Password managers and pasting work at sign-in.
  • Nothing has to be entered twice in the same process.

Navigation

  • There is more than one way to reach any page.
  • Navigation stays in the same place across the product.
  • Components that do the same thing are named the same way.
  • Help sits in the page header on every screen.
  • The page language is declared, and content is not locked to one orientation.

Timing, motion and media

  • Time limits can be adjusted.
  • Moving content can be paused or stopped.
  • Nothing flashes above the seizure threshold.
  • No multipoint or path-based gestures, and pointer actions can be cancelled.
  • No audio or video content, so captions and audio description do not apply.

The four we are still working on

  • 2.1.1 Keyboard A number of tooltips only open on mouseover.
  • 2.4.1 Bypass Blocks The skip link does not work on every page.
  • 1.4.3 Contrast (Minimum) A small number of text elements are below the required ratio.
  • 1.4.11 Non-text Contrast Some control borders and focus indicators are below the required ratio.

All four are partial supports rather than failures: the rest of the product meets the criterion. Page titles, form labels, and name, role and value were open in earlier statements and are supported in this one. Tell us if one of these blocks you and we will prioritise it.

How the simulations are assessed

The conformance report is produced from six passes over the product, including screen reader testing by an evaluator who is legally blind.

Technical analysis

An accessibility expert inspects every screen in Chrome with the WAVE and aXe toolbars, and reads the markup in browser developer tools.

Keyboard only

The platform is navigated from end to end without a mouse, to find what mobility impaired users cannot reach.

Captions

Any audio content is checked for correct captioning for deaf and hard of hearing users.

Low vision

Three passes: the magnification, palette and contrast controls of the operating system, font resizing in the browser, and Color Contrast Analyzer.

Screen readers

An evaluator who is legally blind works through the pages with JAWS and NVDA in Chrome, to find the barriers blind users actually meet.

Usability notes

Usability problems met during the passes above are recorded alongside the technical findings, whether or not a success criterion covers them.

We assess by both self-evaluation and external evaluation. The report has been updated in April 2024, September 2024, January 2025, October 2025 and June 2026.

Browsers and assistive technology

Designed to work with

The combinations the simulations are built and tested against.

  • Google Chrome
  • Firefox
  • Safari
  • NVDA
  • JAWS

Not supported

The simulations are not designed for these, and we do not test them.

  • Mobile browsers
  • Internet Explorer

Accessibility relies on these technologies working with your browser and any assistive technology installed. They are relied upon for conformance with the standards used, WAI-ARIA included.

HTML WAI-ARIA CSS JavaScript

Measures we take

Hubro Simulations, part of Sage Publishing, takes these measures to keep the simulations accessible.

  • Accessibility is part of our mission statement.
  • Accessibility runs through our internal policies.
  • We appoint an accessibility officer and ombudsperson.
  • Our staff receive continual accessibility training.
  • Accessibility goals and responsibilities are assigned.
  • We employ formal accessibility quality assurance methods.
  • We test and review yearly to keep conformance current.

Tell us what blocks you

If you meet an accessibility barrier in one of our simulations, we want to hear about it. We try to respond within one business day.

This statement is from Hubro Simulations, part of Sage Publishing, and covers Hubro Business Simulation, the Hubro Marketing simulations and our other simulation products. It was created on 16 September 2025 and last updated on 27 August 2026 using the W3C Accessibility Statement Generator Tool.

Accessibility in your procurement review?

Send us the questions from your accessibility or disability services team. We answer them against the conformance report and tell you exactly where the product stands.