Opening Sa11y
Sa11y is available while editing supported Cascade CMS pages. Once a page has loaded, select the Sa11y button to open the accessibility assistant.
The assistant analyzes the current page and highlights any accessibility issues it detects.
Reviewing your page
As Sa11y scans the page, it identifies potential accessibility concerns and provides guidance for resolving them.
Selecting an issue will move you to the affected content, allowing you to review the problem in context.
Sa11y also explains why an issue was flagged and, in many cases, provides recommendations for correcting it.
Understanding the results
Sa11y groups its findings into different categories based on the type and severity of the issue.
You may encounter:
- Errors – Accessibility issues that should be corrected before publishing.
- Warnings – Items that require review or may need attention depending on the content.
- Informational messages – Helpful recommendations or reminders that improve overall content quality.
Not every warning indicates a problem. Some items require editorial judgment and should be reviewed before deciding whether a change is necessary.
Resolving issues
As you work through the reported issues:
- Review the explanation provided by Sa11y.
- Update the content in Cascade CMS.
- Save your changes.
- Re-run Sa11y or refresh the page to confirm the issue has been resolved.
Continue until all applicable issues have been addressed.
Best Practices
For the best results:
- Review every new page before publishing.
- Run Sa11y after making significant content updates.
- Resolve errors before publishing whenever possible.
- Review warnings carefully before deciding whether action is needed.
- Use Sa11y alongside DubBot as part of your regular quality assurance process.
Related Articles
- Understanding Sa11y Results
- Resolving Missing Alternative Text
- Resolving Empty Links
- Resolving Heading Structure Issues
- DubBot Basics
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article