After you scan a single page in the browser extension, the scan results will load in the extension. If you don’t want to send the results to the platform, you can review them on the spot. Just remember that if you don’t send results to the platform, they won’t be saved.
On this page:
Issue categories
The extension lists accessibility issues in the following categories:
| Issue category | Description |
|---|---|
|
|
Issues that need to be corrected. |
|
|
Issues that are possible violations. They need to be reviewed to determine if they create an accessibility problem. |
|
|
Issues that are potential opportunities to apply best practices. |
Issue views
You can view the list of issues by requirements, element roles, or rules.
Requirements correspond to WCAG 2.1 success criteria. This tab groups issues by the success criteria they’re most closely associated with.
Element roles organize issues in the hierarchical structure defined by the WAI-ARIA roles of the DOM elements. This tab shows both implicit and explicit roles. It does not show element names. This view is ideal for exploring the issues within a specific element and its children.
Rules explain how to make website elements accessible. This tab groups issues by the rule they might violate.
Review individual issue details
To learn more about individual issues (why the issue is important, who it affects, its location, and how to remediate), open the issue details pane.
To open the issue details pane:
- After you run a scan with the browser extension, expand the requirement.
- Choose the issue you want to know more about.
- Select Locate element to find the exact location of the element with this issue. The extension will highlight the issue on the page using a border.
Note: In some instances findings from scan results may not highlight the element properly.
Comments
0 comments
Article is closed for comments.