Page tree
Skip to end of metadata
Go to start of metadata

Web Content Accessibility

Theoretically, accessibility covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these.


Experitest Cloud supports following accessibility guidelines in its Web Interface,

GuidelineDescriptionManualAutomation
Text Alternatives Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols, or simpler language.SupportedNot Supported
Time-based MediaProvide alternatives for time-based media.SupportedNot Supported
AdaptableCreate content that can be presented in different ways (for example simpler layout) without losing information or structureSupportedSupported via visual testing
DistinguishableMake it easier for users to see and hear content including separating foreground from background.SupportedPartial Support using visual testing
Keyboard AccessibleMake all functionality available from a keyboardSupportedSupported
Enough TimeProvide users enough time to read and use contentSupportedSupported
SeizuresDo not design content in a way that is known to cause seizuresSupportedPartial
NavigableProvide ways to help users navigate, find content, and determine where they areSupportedSupported
ReadableMake text content readable and understandable.SupportedSupported
PredictableMake Web pages appear and operate in predictable waysSupportedSupported
Input AssistanceHelp users avoid and correct mistakesSupportedSupported
CompatibleMaximize compatibility with current and future user agents, including assistive technologiesSupportedNot Supported

Accessibility Tests

The system provides four types of accessibility tests:

  1. Visual Testing - Test how a visually impaired user sees the application by allowing to apply one of the following filters on the application view: shrink, color-blind and blur.
  2. Accessibility Inspector Testing  for iOS
  3. Accessibility Label/Hint Testing - Test if the application was developed with sufficient labels/hints for visually impaired users.
  4. Voice Assisted Accessibility Testing - Test how the application behaves when the voice-assisted accessibility service in the mobile OS (like Android TalkBack and iOS VoiceOver) is activated.

Visual Testing

Open the device and Press the Accessibility tab.

Select any of the filter checkboxes. This will change the real-time view of the device accordingly.

Accessibility Inspector Testing

This is available only in IOS devices.

  1. Choose an application to inspect
  2. Click on "start inspector"

This will open the chosen application in the device and start the inspect - the inspect shown with a green rectangle over the selected element.

3. All selected element properties are shown on the screen.

4. The buttons "Next" and "Previous" allow moving between elements on the application.

5. "Preform" button simulate click action.

Accessibility Label/Hint Testing

This is only available under STAW.

Press the Object-Spy button under the Automation Tab. This will open the Object-Spy view.

To see which elements in the applications were designed for accessibility, press the Accessibility toggle button on the top-left corner.

The Object Spy view will only display elements that were designed for accessibility (i.e., contain the contentDescription property in Android or accessibilityLabel under iOS).

Click any element and you will see in the properties pane the element properties.


Voice Assisted Accessibility Testing

Enable the Android TalkBack and iOS VoiceOver service in the device and use the Cloud Audio-Out capabilities to test the application behavior.


  • No labels