Connect & Get help from 6000+ developers on our Discord community.
Ask the Community
Ask the Community
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 Success Criteria | Impact | Supported Platform |
|---|---|---|---|
|
Button element accessibility label capitalization Identifies the need for descriptive labels on buttons, which helps users relying on screen readers or voice commands understand and interact with the button. |
- 2.1 - 3.1.6 (AAA) - 2.2 - 3.1.6 (AAA) |
Minor |  |
|
Checkbox element accessibility label Recognizes the need for labels on checkbox elements, ensuring users, particularly those using screen readers, can interact with forms effectively. |
- 2.1 - 1.3.1 (A) - 2.2 - 1.3.1 (A) |
Critical |  |
|
Content Description in Editable Elements Ensures that editable elements do not have a content description property, allowing screen readers to accurately read the text entered by users without interference. |
- 2.1 - 4.1.2 (A) - 2.2 - 4.1.2 (A) |
Serious | |
|
Duplicate accessibility label Points out the issue of duplicate labels on a single screen, which can create confusion, especially for users who might struggle with ambiguous labels. |
- 2.1 - 4.1.2 (A) - 2.2 - 4.1.2 (A) |
Critical | |
|
Duplicate state info in spoken output Highlights the need to clearly indicate the current state of views (e.g., expanded or collapsed), helping users navigate and understand content structure. |
- 2.1 - 1.3.1 (A) - 2.2 - 1.3.1 (A) |
Moderate | |
|
Duplicate type info in spoken output Suggests to include the control type name in the accessibility label of UI elements. |
Best Practice | Moderate | |
|
Editable element accessibility label Emphasizes the necessity of labeling editable text fields to assist users relying on assistive technologies in identifying and interacting with these fields. |
- 2.1 - 1.3.1 (A) - 2.1 - 4.1.2 (A) - 2.2 - 1.3.1 (A) - 2.2 - 4.1.2 (A) |
Critical | |
|
Interactive element accessibility label 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. |
- 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) |
Critical | |
|
Label at front Suggests placing labels at the front of the element’s content to enhance accessibility for users relying on screen readers or voice commands. |
Best Practice | Minor | |
|
Label in name Stresses the importance of including the label name in the accessible name of elements, ensuring consistency and clarity for users using assistive technologies. |
- 2.1 - 2.5.3 (A) - 2.2 - 2.5.3 (A) |
Serious | |
|
Link text purpose Clarifies the requirement for clear, descriptive labels on links to help users, including those with cognitive disabilities, understand their purpose and destination. |
- 2.1 - 2.4.4 (A) - 2.2 - 2.4.4 (A) |
Moderate | |
|
Missing view type in spoken output Ensures that all interactive elements expose the correct role or type to screen readers, which helps users comprehend and interact with the interface effectively. |
- 2.1 - 4.1.2 (A) - 2.2 - 4.1.2 (A) |
Serious | |
|
Special-character element accessibility label Notes the potential confusion caused by special characters in labels, particularly for users with cognitive challenges, making content harder to understand. |
Best Practice | Minor | |
|
Switch element accessibility label Underlines the importance of labeling switch elements, so users can easily understand their state (on/off) and function, especially when using assistive technologies. |
- 2.1 - 1.3.1 (A) - 2.2 - 1.3.1 (A) |
Critical | |
Accessible elements
| Rule Name | WCAG Success Criteria | Impact | Supported Platform |
|---|---|---|---|
|
Interactive elements with unsupported type Ensures that custom interactive elements provide a supported class name (or the platform equivalent) to accessibility services. |
- 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 | |
Accessible images
| Rule Name | WCAG Success Criteria | Impact | Supported Platform |
|---|---|---|---|
|
Images with text Ensures that text is not embedded within images unless absolutely necessary. |
- 2.1 - 1.4.5 (AA) - 2.2 - 1.4.5 (AA) |
Serious | |
|
ImageView element accessibility label Highlights the importance of providing descriptive labels for ImageView elements, aiding users with visual impairments in understanding image content. |
- 2.1 - 1.1.1 (A) - 2.2 - 1.1.1 (A) |
Critical | |
Color contrast
| Rule Name | WCAG Success Criteria | Impact | Supported Platform |
|---|---|---|---|
|
Text element color contrast (Minimum) Checks if text elements have sufficient color contrast between text and background colors for readability. |
- 2.1 - 1.4.3 (AA) - 2.2 - 1.4.3 (AA) |
Serious | |
|
Non-text color contrast Checks if non-text elements have sufficient color contrast between these elements and background colors for readability. |
- 2.1 - 1.4.3 (AA) - 2.2 - 1.4.3 (AA) |
Serious | |
Display orientation
| Rule Name | WCAG Success Criteria | Impact | Supported Platform |
|---|---|---|---|
|
App & Screen orientation lock Ensures that all app screens are usable in all orientations when users rely on assistive technologies. |
- 2.1 - 1.3.4 (AA) - 2.2 - 1.3.4 (AA) |
Critical | |
Focus and navigation
| Rule Name | WCAG Success Criteria | Impact | Supported Platform |
|---|---|---|---|
|
Keyboard focus for interactive elements Ensure all interactive elements in the app are reachable and operable using an external keyboard. |
- 2.1 - 2.1.1 (A) - 2.2 - 2.1.1 (A) |
Critical | |
|
Meaningful reading order Checks the layout and focus traversal order of the app content to ensure it follows a logical flow. |
- 2.1 - 1.3.2 (A) - 2.1 - 2.4.3 (A) - 2.2 - 1.3.2 (A) - 2.2 - 2.4.3 (A) |
Serious | |
|
Meaningful visual order Checks the visual layout and focus traversal order of the app content to ensure it follows a logical flow. |
- 2.1 - 1.3.2 (A) - 2.2 - 1.3.2 (A) |
Serious | |
|
Overlapping Interactive Elements Checks the interactive elements in the app to ensure they do not overlap. |
- 2.1 - 1.3.2 (A) - 2.1 - 1.4.10 (AA) - 2.1 - 2.1.1 (A) - 2.1 - 2.4.3 (A) - 2.2 - 1.3.2 (A) - 2.2 - 1.4.10 (AA) - 2.2 - 2.1.1 (A) - 2.2 - 2.4.3 (A) - 2.2 - 2.4.11 (AA) - 2.2 - 2.5.8 (AA) |
Serious | |
|
Screen Reader Focus for Interactive Elements Ensures all interactive elements accessible through touch exploration are also reachable during linear navigation with screen readers. |
- 2.1 - 2.4.3 (A) - 2.2 - 2.4.3 (A) |
Critical | |
|
Traversal Order Checks if the displayed content is easily and correctly navigable in the logical order using touch and assistive technologies. |
- 2.1 - 2.4.3 (A) - 2.2 - 2.4.3 (A) |
Critical | |
Input purpose
| Rule Name | WCAG Success Criteria | Impact | Supported Platform |
|---|---|---|---|
|
Accessible input field labels Ensures that every input field has a visible and persistent label that describes the purpose of the input field and the expected input. |
- 2.1 - 1.3.5 (AA) - 2.1 - 2.4.6 (AA) - 2.1 - 3.3.2 (A) - 2.2 - 1.3.5 (AA) - 2.2 - 2.4.6 (AA) - 2.2 - 3.3.2 (A) |
Serious | |
|
Input type for input fields Ensures that input fields have the correct input type assigned to make data entry easier for all users, including those relying on assistive technologies. |
- 2.1 - 1.3.5 (AA) - 2.2 - 1.3.5 (AA) |
Moderate | |
Readable text and layout
| Rule Name | WCAG Success Criteria | Impact | Supported Platform |
|---|---|---|---|
|
Font magnification support Ensures that users can enlarge or zoom in on the text according to the user’s selected font size. |
- 2.1 - 1.4.4 (AA) - 2.2 - 1.4.4 (AA) |
Critical | |
|
Responsive containers Ensures that containers maintain responsiveness and adaptability across different devices, screen sizes, and orientations. |
- 2.1 - 1.4.10 (AA) - 2.2 - 1.4.10 (AA) |
Serious | |
|
Text truncation 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. |
- 2.1 - 1.4.4 (AA) - 2.2 - 1.4.4 (AA) |
Critical | |
|
Text spacing Checks if there is enough space between paragraphs, lines, and words to enhance readability. |
- 2.1 - 1.4.12 (AA) - 2.2 - 1.4.12 (AA) |
Moderate | |
|
Two-dimensional scrolling Checks if content remains accessible, readable, and functional without requiring two-dimensional scrolling on small screens. |
- 2.1 - 1.4.10 (AA) - 2.2 - 1.4.10 (AA) |
Serious | |
Touch target size and spacing
| Rule Name | WCAG Success Criteria | Impact | Supported Platform |
|---|---|---|---|
|
Text touch target size Checks to verify if touch targets are large enough for easy interaction by all users. |
- 2.1 - 2.5.5 (AAA) - 2.2 - 2.5.5 (AAA) |
Serious | |
|
Text touch target size and spacing Checks to verify if minimum touch target size of 24dp x 24dp for easy interaction by all users. |
- 2.2 - 2.5.8 (AAA) | Serious | |
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!