In this Article:
Setting the Issues Filter
When creating a profile for a new user, there is an option called Issues Filter.
This field allows you to filter issues this user sees to a smaller results set for Accessibility and Best Practice issues and some Policy results.
Selecting the Issues Filter dropdown reveals two options:
See all issues (default)
See issues relevant to content editors
The option See issues relevant to content editors, is available for all role types.
Accessibility Checks Shown to Content Editors
A default DubBot site with nothing ignored and no Custom Policies added by the client has 27 accessibility checks shown when the Content Editor Issues Filter is enabled:
Links with the same name must have a similar purpose
Styled <p> elements must not be used as headings
Image buttons must have alternate text
Frames must have an accessible name
Links must be distinguishable without relying on color
<marquee> elements are deprecated and must not be used
Link does not have readable (discernible) link text
Buttons must have discernible text
Form field must not have multiple label elements
<svg> elements with an img role must have an alternative text
Input buttons must have discernible text
Elements must meet minimum color contrast ratio thresholds
Frames must have a unique title attribute
Data or header cells must not be used to give caption to a data table.
Documents must have <title> element to aid in navigation
[role="img"] elements must have an alternative text
<object> elements must have alternate text
<video> elements must have captions
Images must have alternate text
Active <area> elements must have alternate text
Table headers in a data table must refer to data cells
Table cells that use the headers attribute must only refer to cells in the same table
Select element must have an accessible name
autocomplete attribute must be used correctly
Form elements must have labels
Non-empty <td> elements in larger <table> must have an associated table header
<video> or <audio> elements must not play automatically
Best Practices Checks Shown to Content Editors
For a default DubBot site with nothing ignored and no Custom Policies added by the client, there are 8 Best Practices checks when the Content Editor Issues Filter is enabled:
Page should contain a level-one heading
Heading levels should only increase by one
Table header text should not be empty
Headings should not be empty
Tables should not have the same summary and caption
Ensure elements marked as presentational are consistently ignored
Alternative text of images should not be repeated as text
Form elements should have a visible label
Review the full listing of Best Practices Checks.
If you have questions, please contact our DubBot Support team via email at help@dubbot.com or via the blue chat bubble in the lower right corner of your screen. We are here to help!