Skip to main content

Index

Milestone Accessibility Overview

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

Milestone follows a standard visual 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
  • When present, H1 headings indicate the page you’re currently on. For example, H1 will be the name of your institution on the landing page.

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

  • H3 headings are used to indicate actions that you can perform.

Structure by regions and landmarks

Milestone 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 and landmarks in Milestone include:

  • Breadcrumb navigation

  • Banner

  • Main

  • Content information

The Milestone home page has breadcrumb navigation at the top left, with a banner beneath that has navigation options. The main area of the page is the institution that Milestone is being used for. Content information is at the bottom of the page.
Keyboard navigation

The Milestone 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. Keyboard-only and screen reader users can avoid repeated content and navigate through the page faster.

Users can tab until the keyboard focuses on the Skip to main content link that goes directly to the main content of the page. A screen reader can also present a list of links. While Skip to sub-navigation and Skip to main navigation links are available, these currently don't function and will be implemented in the future.

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.