BrowserStack App Accessibility Rule Engine
Our proprietary app accessibility rule engine provides unmatched coverage of WCAG standards, ensuring full compliance with the latest accessibility guidelines. It automatically detects accessibility violations that are often difficult or time-consuming to catch through manual testing.
Rules supported by BrowserStack App Accessibility
Accessibility labels
| Rule Name | WCAG SC | Impact | Supported Platform |
|---|---|---|---|
| Button element accessibility label capitalization |
2.1 - 3.1.6 (AAA) 2.2 - 3.1.6 (AAA) |
Minor |  |
| Identifies the need for descriptive labels on buttons, which helps users relying on screen readers or voice commands understand and interact with the button. | |||
| Checkbox element accessibility label |
2.1 - 1.3.1 (A) 2.2 - 1.3.1 (A) |
Serious |  |
| Recognizes the need for labels on checkbox elements, ensuring users, particularly those using screen readers, can interact with forms effectively. | |||
| Duplicate accessibility label |
2.1 - 4.1.2 (A) 2.2 - 4.1.2 (A) |
Serious | |
| Points out the issue of duplicate labels on a single screen, which can create confusion, especially for users who might struggle with ambiguous labels. | |||
| Editable element accessibility label |
2.1 - 1.3.1 (A), 2.1 - 4.1.2 (A) 2.2 - 1.3.1 (A), 2.2 - 4.1.2 (A) |
Serious | |
| Emphasizes the necessity of labeling editable text fields to assist users relying on assistive technologies in identifying and interacting with these fields. | |||
| ImageView element accessibility label |
2.1 - 1.1.1 (A) 2.2 - 1.1.1 (A) |
Serious | |
| Highlights the importance of providing descriptive labels for ImageView elements, aiding users with visual impairments in understanding image content. | |||
| Interactive element accessibility label |
2.1 - 1.3.1 (A), 2.1 - 2.4.6 (AA), 2.1 - 4.1.2 (A) 2.2 - 1.3.1 (A), 2.2 - 2.4.6 (AA), 2.2 - 4.1.2 (A) |
Serious | |
| Recognizes the importance of clear labels on interactive elements, such as buttons and links, to ensure users can interact with them properly using assistive technologies. | |||
| Label at front | Best Practice | Minor | |
| Suggests placing labels at the front of the element’s content to enhance accessibility for users relying on screen readers or voice commands. | |||
| Label in name |
2.1 - 2.5.3 (A) 2.2 - 2.5.3 (A) |
Minor | |
| Stresses the importance of including the label name in the accessible name of elements, ensuring consistency and clarity for users using assistive technologies. | |||
| Link text purpose |
2.1 - 2.4.4 (A) 2.2 - 2.4.4 (A) |
Minor | |
| Clarifies the requirement for clear, descriptive labels on links to help users, including those with cognitive disabilities, understand their purpose and destination. | |||
| Special-character element accessibility label | Best Practice | Minor | |
| Notes the potential confusion caused by special characters in labels, particularly for users with cognitive challenges, making content harder to understand. | |||
| Switch element accessibility label |
2.1 - 1.3.1 (A) 2.2 - 1.3.1 (A) |
Serious | |
| Underlines the importance of labeling switch elements, so users can easily understand their state (on/off) and function, especially when using assistive technologies. | |||
| View state in element accessibility label |
2.1 - 1.3.1 (A) 2.2 - 1.3.1 (A) |
Serious | |
| Highlights the need to clearly indicate the current state of views (e.g., expanded or collapsed), helping users navigate and understand content structure. | |||
| View type in element accessibility label | Best Practice | Minor | |
| Suggests to include the control type name in the accessibility label of UI elements. |
Accessibility elements
| Rule Name | WCAG SC | Impact | Supported Platform |
|---|---|---|---|
| Accessible elements |
2.1 - 1.3.3 (AA), 2.1 - 4.1.2 (A) 2.2 - 1.3.3 (AA), 2.2 - 4.1.2 (A) |
Serious | |
| Notes the potential confusion caused by special characters in labels, particularly for users with cognitive challenges, making content harder to understand. |
Color contrast
| Rule Name | WCAG SC | Impact | Supported Platform |
|---|---|---|---|
| Text element color contrast (Minimum) |
2.1 - 1.4.3 (AA) 2.2 - 1.4.3 (AA) |
Serious | |
| Checks if text elements have sufficient color contrast between text and background colors for readability. | |||
| Non-text color contrast |
2.1 - 1.4.11 (AA) 2.2 - 1.4.11 (AA) |
Serious | |
| Checks if non-text elements have sufficient color contrast between these elements and background colors for readability. |
Display orientation
| Rule Name | WCAG SC | Impact | Supported Platform |
|---|---|---|---|
| App & Screen orientation lock |
2.1 - 1.3.4 (AA) 2.2 - 1.3.4 (AA) |
Serious | |
| Underlines the importance of all screens of an app must be usable in all orientations. when using assistive technologies. |
Resize text
| Rule Name | WCAG SC | Impact | Supported Platform |
|---|---|---|---|
| Font magnification support |
2.1 - 1.4.4 (AA) 2.2 - 1.4.4 (AA) |
Serious | |
| Ensures if users can enlarge or zoom in on the text according to the user’s selected font size. | |||
| Text truncation |
2.1 - 1.4.4 (AA) 2.2 - 1.4.4 (AA) |
Serious | |
| Checks if text does not fit within its container and is cut off or hidden due to insufficient space, particularly when text size is increased. |
Touch target size and spacing
| Rule Name | WCAG SC | Impact | Supported Platform |
|---|---|---|---|
| Text touch target size |
2.1 - 2.5.5 (AAA) 2.2 - 2.5.5 (AAA) |
Serious | |
| Checks to verify if touch targets are large enough for easy interaction by all users. | |||
| Text touch target size and spacing | 2.2 - 2.5.8 (AAA) | Serious | |
| Checks to verify if minimum touch target size of 24dp x 24dp for easy interaction by all users. |
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!