Select an accessibility level to control which issues are included in accessFlow for you to resolve. This setting helps you decide how strict your accessibility auditing should be. Changing the accessibility level takes effect after the next audit and may impact your site accessibility score.
Accessibility level options
WCAG guidelines plus accessiBe best practices
This option includes:
- Issues required to conform to Web Content Accessibility Guidelines (WCAG)
- Additional issues based on accessiBe best practices that are not required for WCAG conformance, but they help improve usability and the overall experience for people with disabilities.
Switching to this option may increase the number of issues.
WCAG guidelines only
This option includes:
- Only issues required to conform to WCAG guidelines.
Switching to this option will remove all issues related to accessiBe best practices from accessFlow and may reduce the number of issues.
To change your accessibility level
- Go to Settings > Accessibility level.
- Select your preferred option:
- WCAG guidelines only, or
- WCAG guidelines + accessiBe best practices
- Select Save Changes.
- Select Change Level. The update will apply after the next audit and may change your accessibility score.
What are accessiBe best practices?
accessiBe best practices are not required to conform to WCAG guideline, but addressing them can improve accessibility and usability to create a more inclusive experience.
| Best Practice | Description |
| Redundant Aria labels | Aria label is redundant when it has the same value as the content. |
| Title misuse | Title attributes should not be used to deliver information. |
| Broken submenu indication | Submenu indication should only be on the nav item’s link/button tag and should not exist if sub menu doesn’t exist. |
| Article setup | Article tags that aren’t articles should remove their article role. |
| Figure setup | Figure elements should receive text description or remove figure role. |
| Aria label misuse | Aria labels should not be used on elements that have no roles. |
| Nested navigation | Avoid using nested navigation structure. |
| Iframe labeling | Iframe elements should be labeled properly for assistive technology. |
| New window links | Links should indicate to assistive technology if they open a new tab. |
| Non-interactive Tabindex | Non-interactive elements should not be keyboard navigable. |
| Load Autofocus | Avoid using autofocus. |
| Broken aria labels | Aria labels should not override or replace proper content. |
| Misused Nav Tagging | A non-navigation element is improperly tagged as such. |
| Missing Nav Items | Always use a button or link and not only text nodes for navigation items. |
| Broken Nav Tagging | Avoid using role menu/menubar for navigation elements. |
| Incorrect Main Landmark | The main landmark is different than the tagged one. |
| Live Carousels | Carousels should not be tagged as live regions. |
| Role Applications | Avoid using role applications. |