Skip to main content

Player Accessibility

Use keyboard navigation, screen readers, captions, and larger text in the We Are Player.

The We Are Player includes accessibility settings that help learners navigate a Story without a mouse, use a screen reader, show captions, and make text larger. These settings are available to learners and do not need to be enabled by the Creator.


Play a Story with a keyboard

  1. Open the Story in the Player.

  2. Press Tab to move through the available controls. A visible focus ring shows which control is selected.

  3. Press Enter to open a Hotspot or select a button.

  4. Continue using Tab and Enter to move through the Story.

Expected result: You can play the Story from start to finish without using a mouse.


Use a screen reader

Open the Story in the Player with your screen reader running. The screen reader reads the content and available controls as you move through the Story.

Hotspot names are read aloud, so Creators should replace general names such as “Hotspot 1” with short, descriptive names.


Turn on captions

  1. Open the Story in the Player.

  2. Open the caption control in the Player controls.

  3. Turn captions on.

Expected result: Captions appear even when the Story was set to hide them by default.


Make text larger

Increase Font Size enlarges text throughout the Story by 25%. It works on Stories that are already published, so the Creator does not need to publish the Story again.

  1. Open the Story in the Player.

  2. Open the settings in the Player control bar.

  3. Turn on Increase Font Size.

Expected result: Text becomes larger in Pages, Posters, Quizzes, Hotspots, captions, response choices, End nodes, and the Player controls. Turn the setting off to return the text to its original size.


Current limitations

  • Code node content does not become larger because it uses the customer’s own HTML.

  • Loading and error screens shown before a Story starts are not affected by Increase Font Size.

  • Hotspot and Poster images cannot currently include alt text.

  • Keyboard and screen-reader behaviour has not yet been confirmed for Stories opened inside an LMS or another embedded context.

  • Testing has not yet been confirmed for VoiceOver, NVDA, or mobile Safari.

  • We have not yet confirmed whether a learner’s caption choice is kept for the rest of the Story.

Did this answer your question?