Mobile Studio - Accessibility
Web Content Accessibility
Theoretically, accessibility covers a wide range of recommendations for making Web content more accessible. Following these guidelines makes 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.
Digital.ai Continuous Testing Cloud supports following accessibility guidelines in its Web Interface.
| Guideline | Description | Manual | Automation |
|---|---|---|---|
| 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. | Supported | Not Supported |
| Time-based Media | Provide alternatives for time-based media. | Supported | Not Supported |
| Adaptable | Create content that can be presented in different ways (for example simpler layout) without losing information or structure | Supported | Supported via visual testing |
| Distinguishable | Make it easier for users to see and hear content including separating foreground from background. | Supported | Partial Support using visual testing |
| Keyboard Accessible | Make all functionality available from a keyboard | Supported | Supported |
| Enough Time | Provide users enough time to read and use content | Supported | Supported |
| Seizures | Do not design content in a way that is known to cause seizures | Supported | Partial |
| Navigable | Provide ways to help users navigate, find content, and determine where they are | Supported | Supported |
| Readable | Make text content readable and understandable. | Supported | Supported |
| Predictable | Make Web pages appear and operate in predictable ways | Supported | Supported |
| Input Assistance | Help users avoid and correct mistakes | Supported | Supported |
| Compatible | Maximize compatibility with current and future user agents, including assistive technologies | Supported | Not Supported |
Accessibility Tests
The system provides these types of accessibility tests:
- 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.
- Accessibility Inspector Testing for iOS and Android
- Accessibility Label/Hint Testing - Test if the application was developed with sufficient labels/hints for visually impaired users.
- 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, then click the Accessibility tab.
-
Select any of the filter checkboxes. This changes the real-time view of the device accordingly.
Accessibility Inspector Testing
- Choose an application to inspect.
- Click Inspect.
This opens the chosen application in the device and start the inspection. The inspection is shown with a green rectangle over the selected element.
The inspection is performed from the element on the top to the one on the bottom. During the inspection, the subsequent actions take place.
- All selected element properties are shown on the screen.
- The Perform button simulates a click action.
- A red indication is shown on the Accessibility icon.
Voice Assisted Accessibility Testing
- Enable the Android TalkBack or iOS VoiceOver service in the device.
- Use the Cloud Audio-Out capabilities to test the application behavior.
Text-to-Speech Overlay for Android devices
To enable TTS overlay while using accessibility testing, the property ct.android.accessibility-enable-text-to-speech should be set to true in the cloud server's application.properties followed by restarting the cloudserver.