Accessibility Module

The Accessibility Module implements accessibility features that make the HTML5 Viewer easier to use for people with disabilities. There are two aspects to accessibility support in the HTML5 Viewer that users can use:

Screen Readers: Run a screen reader to vocalize and interpret page content.
Keyboard Shortcuts: Interact with the viewer using only the keyboard.

Screen readers and keyboard shortcuts can be used together.

The Accessibility Module also implements the configurable Accessibility window, which informs users about the accessibility features in the HTML5 Viewer.

In order for a user to use a screen reader with an HTML5 Viewer, the user must have a screen reader installed and running when using the viewer. No additional steps are required. The HTML5 Viewer is tested using the Freedom Scientific JAWS screen reader but other screen readers may also work.

Press TAB repeatedly to navigate to the Identify tool

Configuration Properties

Module

keyboardFocusIndicatorEnabled: To highlight the current UI element with a border, set to true. The default is true.
keyboardFocusIndicatorColor: If the keyboardFocusIndicatorEnabled configuration property is set to true, use this setting to change the highlight color of the current UI element. The default is #550055.
expandedMapKeyboardAccessibility: To allow the user to pan the map with the arrow keys even when the mouse pointer is not hovering over the map, set to true. The default is true.

The user must navigate to the map before panning with the arrow keys.
automaticElementFocusing: To automatically focus on the first interactive element of a newly-activated view, set to true. The default is true.
includeProviders: To enable all of the accessibility providers that read out information to users with screen readers, set to true. The default is true.
providers: An array of accessibility providers. By default, they are MapTextProvider and ViewActivatorProvider:
- MapTextProvider: Provides the ability to read what is currently visible on the map to the user. This provider has the following properties:
  - id: The ID of the provider.
  - type: The provider type.
  - decimalPrecision: The number of decimal places to read out. The default is 4.
  - readAttributionInformation: To have the screen reader read aloud the map attribution information when the map is selected, set to true. The default is false.
  - isEnabled: To enable the provider, set to true. The default is true.
- ViewActivatorProvider: Provides the ability to read out which views have been activated or deactivated. This provider has the following properties:
  - id: The ID of the provider.
  - type: The provider type.
  - isEnabled: To enable the provider, set to true. The default is true.
  - notifications: An object whose properties' names are non-Data-Frame views, and values are text keys or strings representing the name of the view to read out when the view is activated or deactivated.
  - subviewNotifications: An object whose properties' names are Data-Frame views, and values are text keys or strings representing the name of the view to read out when the view is activated or deactivated.

Views

AccessibilityView: No configuration properties
AccessibilityIconView: No configuration properties

View Models

AccessibilityViewModel: No configuration properties
AccessibilityIconViewModel:
- included: To display the Accessibility icon in the Desktop or Tablet interfaces, or the View the Accessibility window option in the I Want To Menu in the Handheld interface, both of which open the Accessibility window, set to true. The default is true.
- content: The encoded HTML content of the Accessibility window.
  
  You can use a valid text key for the content as long as there are no spaces or HTML markup surrounding the text key. For more information on using text keys, see Configure User Interface Text.
- title: The title of the Accessibility window. You can specify a string or a text key. The default is the text key, @language-accessibility-map-title, which reads Accessible Geocortex. For more information on using text keys, see Configure User Interface Text.