Ensuring an accessible and pleasant experience for all users is a key element within our Territorium platform. Our LifeJourney platform was built using the most modern HTML and CSS technologies and is committed to W3C’s Web Accessibility Initiative and Section 508 guidelines.

The Voluntary Product Accessibility Template, or VPAT, is a tool that administrators and decision-makers can use to evaluate Territorium’s conformance with the accessibility standards under Section 508 of the Rehabilitation Act.

General accessibility design guidelines can be found in the General Accessibility Design Guidelines document.


Each Territorium feature and release is manually tested with the following screen reader and browser combinations:

  • JAWS (latest version for Chrome/Firefox on Windows)
  • NVDA (latest version for Chrome/Firefox on Windows)
  • VoiceOver (latest version for Safari/Chrome on MacOS and iOS mobile)
  • Talkback (latest version for Android mobile)

Browser and screen reader pairing is selected based on current screen reader and browser usage statistics, ensuring that preferred combinations are always maintained for the widest range of LifeJourney users. As preferences shift and stabilize over time, our Quality Assurance testing and support shift to match them.

Territorium and our LifeJourney application are designed so that screen reader users can confidently utilize their preferred screen reader and browser. However, the variety of browser and screen reader combinations means that only the above-listed combinations are tested and confirmed to work well in LifeJourney. If you experience issues using your preferred browser and screen reader combination, please review and utilize the officially supported combinations listed above. If you experience issues with the officially supported screen reader and browser combinations, please report your experience to our Success Team.


Windows 10 & 11 (64-bit)- excluding ‘S Mode’

macOS 10.15 and above – excluding beta versions


iOS and Android


Territorium makes extensive use of ARIA landmark regions. Accessible Rich Internet Applications (ARIA) define ways to make web content and web applications more accessible to people with disabilities. Therefore, the best way to get around in Territorium’s LifeJourney is to navigate via regions. Within regions, Territorium uses HTML headings, so navigating between headings can be helpful.


Several LifeJourney features have been specifically improved for accessibility. Other features may be limited at this time. This section highlights several feature areas and accessibility behaviors.

Font Sizing: The LifeJourney interface uses rem sizing for fonts, so any typography will zoom when the browser is zoomed and will scale if a custom browser-sized font is chosen or set from a browser’s setting.

Assessments: Our Assessments allow instructors/administrators to moderate an assessment for an extended time.

Rich Content Editor: The Rich Content Editor supports multiple accessibility features for easy creation of accessible content:

  • The Rich Content Editor includes an accessibility tool that checks common accessibility errors within the editor. This tool can help you design course content while considering accessibility attributes and is in the Rich Content Editor menu bar.
  • Alt text should be added when embedding external images.
  • Headings for table columns and rows can be changed in either the Rich Content Editor or the HTML Editor view.

User Settings: The User Settings page hosts two feature options to enhance accessibility. Learn how to change user settings.

  • High Contrast UI: When enabled, this feature offers higher contrast in buttons, tabs, and other areas throughout LifeJourney.
  • Underline Links: When enabled, this feature underlines hyperlinks in navigation menus, the Dashboard, and page sidebars.


Territorium offers many optional LTI app integrations as part of our commitment to open education. When we review new integration tools, accessibility features are always an important consideration. Unfortunately, as integrations are created by third-party developers and offered to Territorium clients as an optional service, we cannot always ensure that these integrations meet the same standards that we hold for core Territorium. Therefore, if an institution wants to incorporate an integration where additional features may be required, we recommend that the institution contact the developer directly with any specific concerns.