Skip to main content

Planning

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

Planning 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 called 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 identifies the current page.

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

  • H3 is a selector to open controls.

  • H4 is informational.

Structure by regions and landmarks

Planning has defined sections on each page using HTML and ARIAregions 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 Planning include:

  • Banner

    • Navigation

    • Main Navigation

  • Main

    • Content in formation

The main dashboard for Planning is highlighted in the center, showing Assessment Cycles. The Planning banner in the top left is also highlighted.

Keyboard navigation

The Planning product team works continuously to implement operable features using the industry standard keyboard interactions. We consider the requirements for each component, so users can perceive and operate efficiently.

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

Skip to main content

The platform has a skip button mechanism to bypass blocks of content that are repeated on multiple pages, such as headers and main navigation. This allows users to jump directly to the main content area.

Users can tab until the keyboard focuses on the Skip to main content button that goes directly to the main content of the page.

Focus Order

Users can navigate the application sequentially using the keyboard. Interactive elements receive focus in the order that 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.