Skip to main content

Engage

Accessibility

Overview

We employ a proactive, multifaceted accessibility strategy that includes a shared accountability model for accessibility grounded in community feedback. We leverage an international team of accessibility specialists to mentor product teams in integrating accessibility and inclusivity best practices. In keeping with our strong tradition of leadership around accessibility, our products are designed and developed with internationally recognized Web Content Accessibility Guidelines (WCAG) in mind.

Semantic structure and navigation

Engage follows a standard layout to ensure familiarity as users navigate through the platform. The application is structured logically by headings and regions in JAWS. Regions are known as landmarks in NVDA. This gives users the ability to quickly understand the structure of any page in the application and easily move to the appropriate section of the page or content item.

Structure by headings

  • H1 headings indicate the current page.

  • H2 headings are used to indicate major sections of a page.

  • H3 headings are used to enter a selection under a major section of a page.

Structure by regions and landmarks

Engage has defined sections on each page using HTML and ARIA regions that allow users of assistive technologies to navigate the page more efficiently. With regions, users can quickly understand the structure of any page in the application and easily move to the appropriate section of the page.

Regions in Engage are:

  • Banner

  • Navigation

  • Main

The home page of Engage has a banner at the top left, navigation options to the left beneath the banner, and the main area in the center features links to campus events and student interests.
Keyboard navigation

Engage’s product team continuously implement operable features using the industry standard keyboard interactions. We consider the requirements for each component so users can perceive and operate the functionality correctly.

Keyboard navigation patterns differ between browsers (Microsoft Edge, Firefox, Safari, Chrome), but the interactions within any particular browser are common and consistent.

Skip to content

Across the platform, a skip link mechanism is available to bypass blocks of content that are repeated on multiple pages, such as the header or course navigation. This allows users to jump directly to the main content area. Keyboard-only and screen reader users can avoid repeated content and navigate faster through the page.

Users can tab until the keyboard focuses on the Skip to content link that goes directly to the main content. A screen reader can also pull a list of links and select Skip to content.

Focus order

Users can navigate the application sequentially using the keyboard. Interactive elements receive focus in the order content is visually arranged, preserving meaning and operability.

Visual presentation

  • The visual presentation of text, graphic elements, and user interface components and states have appropriate color contrast.

  • Users can define alternative text for images.

  • Interface buttons have an accessible name or label allowing assistive technology users to understand their purpose.

Assistive technology compatibility

For the best experience with screen readers, we recommend these combinations:

Screen reader

Operating system

Browser

JAWS

Windows

Firefox or Google Chrome

NVDA

Windows

Firefox or Google Chrome

VoiceOver

Mac OS

Safari, Firefox, or Google Chrome

Basic Keyboard Shortcuts JAWS, NVDA and VoiceOver provides commands for navigating web pages according to the type of screen reader.