Last updated: May 21, 2020 10:57
The following sections list the areas that Accessibility Inspector and Accessibility Scanner analyze to find opportunities for improvements, including sample reports. Click a tool to view details.
- Labels: Used by assistive technologies, such as VoiceOver or TalkBack, to help vision-impaired users navigate the interface. Labels should be descriptive, human-readable, and localized into the target language. Accessibility Inspector alerts you when a label seems to be missing or may not be descriptive enough or readable, thus rendering the UI element inaccessible. Labels should be implemented via the accessibility API.
- Text contrast: The contrast ratio between text or images and background color (or foreground and background color) must be at least 3.0 or greater for large text or 4.5 or greater for small text. Anything lower triggers an entry in the audit report.
- Dynamic font size: An option for users to adjust the font size to fit their needs. If an app uses custom font types, it may not support dynamic resizing unless you introduce a
UIFontMetricsobject. Dynamic font sizes for labels, buttons, and other UI elements require that the
adjustsFontForContentSizeCategoryproperty be set to
true. Accessibility Inspector alerts you when it detects that a user will not be able to change the font size of an element.
- Hit area size: The area designated for user interaction, for example the clickable area around a button. If this area is too small, users may have trouble interacting with the screen. Accessibility Inspector alerts you when an area is too small and recommends a better size. For buttons, for example, the recommended size is 48dp.
Perfecto uses Accessibility Inspector default settings.
Example audit results | iOS
You can view an example of audit results produced by Accessibility Inspector by downloading the attached auditAccecibility.html and opening it in a browser.
To download the sample audit report:
- Open the report in a preview.
- In the previewer, at the top right, click the download icon .
- Double-click the downloaded file to open it in the browser.
- Labels: Used by assistive technologies, such as VoiceOver or TalkBack, to help vision-impaired users navigate the interface. Labels should be descriptive, human-readable, and localized into the target language. Accessibility Scanner alerts you when a label is missing, has a redundant description, a duplicate description, or is not informative enough.
- Text contrast: The contrast ratio between text or images and background color (or foreground and background color) must be at least 3.0 or greater. Anything lower triggers an entry in the audit report.
- View hierarchy: The hierarchy of UI and control elements that determines how a user navigates the app. Accessibility Scanner alerts you when it finds implementations that could make it difficult for users with motor impairments to interact with the app. Examples are clickable links that are not easily identified as such; more than one clickable link in the same location; editable items, such as text fields, that are not implemented in a way that clearly identifies their purpose; item types that are unidentified, unknown to, or not supported by accessibility services via the AccessibilityNodeInfo class in the Android API; or view hierarchy that does not reflect the logical structure of the app, thus hindering the navigation with screen readers.
- Touch target size: Same as or similar to hit area size on iOS devices. The area designated for user interaction, for example the clickable area around a button. Accessibility Scanner alerts you when the size of a touch target is too small.
Perfecto uses Accessibility Scanner default settings.
Example audit results | Android
Following is an example of audit results produced by Accessibility Scanner. The results come in text format (
.json). Starting with the Perfecto 20.6 release, a
.png copy of the audited screen, as shown in the following image, will also be available.
Watch this short video to see how you can enrich your test reports with audit results produced by Accessibility Inspector or Accessibility Scanner.
For each screen to audit, add the
mobile:checkAccessibility:audit function to your test script, as follows:
<tag-name> is a descriptive string to be used as the name of the audit result file. Best practice is to use the name of the audited screen as the tag name.
- In the Perfecto UI at <your-cloud>.app.perfectomobile.com (where your-cloud is your actual cloud name, such as mobilecloud), click ANALYZE REPORTS.
- In the Test Analysis view, on the Report Library tab, click the report to which you attached the accessibility results.
The report opens.
- At the top right, click the download icon .
- From the download menu, select Accessibility. If more than one accessibility audit is available, select the required report.
- When the report has finished downloading, open it by double-clicking.
Accessibility testing is currently not supported with iOS 10.