What A11yCheck looks for in Rise 360
A11yCheck reviews your published Rise course against WCAG 2.1 Level AA — the standard required by Section 508, EN 301 549, and most UK and EU accessibility laws. Here are some of the issues it finds:
How the Rise 360 checker works
Publish to Review 360
In Rise, click Share and publish your course to Articulate Review 360. Copy the Review link from the sharing screen.
Paste your link
Paste the Review 360 link into A11yCheck and click Scan. No Articulate login required — the scanner works from the public Review link.
Get your report
In under two minutes, you receive a full report across accessibility, course engagement, and course quality for Rise 360. Accessibility and course quality findings are prioritised by severity with step-by-step fix instructions; course engagement findings include research-based context instead.
Why Rise 360 courses still need an accessibility check
Rise 360's block-based structure produces cleaner HTML than many eLearning tools — heading structure, keyboard navigation, and semantic markup are mostly handled for you. But that does not mean Rise courses pass accessibility audits automatically.
The most common failures in Rise come from content, not code. Images added without alt text. Videos embedded without captions. Brand colours applied through Theme settings that fail contrast checks. Custom HTML blocks added without testing keyboard navigation. Audio blocks with no transcript.
In regulated industries, none of this is optional. Section 508, EN 301 549, and the Equality Act all require accessible digital training — and an audit failure in a Rise course carries the same consequences as one in a Storyline course.
Frequently asked questions about Rise 360 accessibility
What is a Rise 360 accessibility checker?
A Rise 360 accessibility checker reviews your published Rise course for WCAG 2.1 compliance failures — things like missing alt text, colour contrast issues, missing captions, and keyboard navigation problems. A11yCheck scans your Review 360 link and produces a prioritised report with step-by-step fixes for Rise 360 specifically.
Is Articulate Rise 360 accessible by default?
Rise 360 is better than many eLearning tools at accessibility out of the box — its blocks follow semantic HTML patterns and keyboard navigation is largely handled for you. However, issues still appear when images lack alt text, videos have no captions, custom HTML blocks are added, or brand colours fail contrast checks.
How do I check a Rise 360 course for WCAG compliance?
Publish your Rise course to Articulate Review 360, copy the Review link, and paste it into A11yCheck. The scanner checks your course against WCAG 2.1 Level AA and returns a full report — with specific Rise 360 fix instructions for each issue.
Does A11yCheck support Rise 360 custom blocks?
Yes. A11yCheck checks custom HTML blocks in Rise for common accessibility failures including missing labels, focus management issues, and contrast problems introduced by custom styles.
Which WCAG level does A11yCheck test Rise courses against?
WCAG 2.1 Level AA — the standard required by Section 508, EN 301 549, and most organisational accessibility policies.
How is Rise 360 different from Storyline 360 for accessibility?
Rise uses a block-based structure that naturally produces better semantic HTML than Storyline's slide-based approach. Tab order, heading structure, and keyboard navigation are generally better handled automatically. The main risks in Rise are content gaps — missing alt text, absent captions, and low-contrast brand colours applied through theme settings.
Ready to check your Rise course?
Free during beta. No credit card. Paste your Review 360 link and get results in under two minutes.
Start scanning — it's freeRelated resources
Rise Accessibility Guide (free PDF) →
The full guide behind every check on this page
Rise Quick Checklist (free PDF) →
A fast, printable pass before you publish
Storyline 360 Accessibility Checker →
Check your Storyline 360 courses for the same WCAG issues
eLearning Accessibility Issue Library →
Browse every issue with plain-English fix guides