Why this matters
When a screen reader reaches a button, it reads the label out loud. If the label is missing, it says "Button". If the label is "Click here" or "Next", the learner still has no idea what will happen. WCAG 4.1.2 requires every interactive element to have a name that clearly communicates its purpose — not just to sighted users, but in a form assistive technology can announce.
Storyline 360 example
A Storyline slide has a button made from a right-arrow icon graphic. No alt text is set and no accessible name is provided in the Accessibility panel. Screen readers announce "Button" — nothing else.
Rise 360 example
A Rise lesson uses a custom-styled Continue button where the visible text is hidden via CSS. No accessible name is provided to replace it.
How to fix it
- 1Go through every button, link, and clickable element in your course
- 2Give each one a unique, descriptive label that explains what it does
- 3Avoid vague labels — "Next" is better than "Click here", but "Next: Safety Procedures" is better still
- 4For icon-only buttons, add a descriptive accessible name even though no visible text is shown
- 5Do not use the same label for two buttons that do different things
Fix in Storyline 360
- 1Click the button or interactive element
- 2Open Size and Position > Accessibility
- 3Type a descriptive name — for an arrow button, write something like "Go to next slide"
- 4Avoid duplicating labels across different actions
Fix in Rise 360
- 1In Rise, the button label is whatever text you type — make it descriptive
- 2Avoid icon-only buttons in custom HTML blocks unless you add an aria-label
- 3Review all action links and confirm each label explains exactly where it goes or what it does
Common questions
What makes a good button label in eLearning?
A good label describes the action and what happens next. "Start Module 1" beats "Start". "Download the Safety Guide" beats "Download". Write labels as though the learner cannot see the page around them — because screen reader users cannot.
How do I add an accessible name to an icon button in Storyline?
Click the button, open the Size and Position panel, go to the Accessibility tab, and type a name. That name is what screen readers announce — it does not need to match any visible text.
Are duplicate button labels a problem?
Yes. If two buttons both say "Download", screen reader users cannot tell them apart. Rethink the labels: "Download the Module 1 Worksheet" and "Download the Module 2 Worksheet" leave no room for confusion.
Does WCAG require buttons to have visible text?
WCAG requires programmatic names — labels that assistive technology can read. Visible text is not mandatory, but WCAG 2.5.3 says the accessible name must include whatever visible text is shown. An icon button needs an accessible name even with no visible text.
Check your course for this issue automatically
Paste your Storyline 360 or Rise 360 Review link and A11yCheck scans for this and 80+ other issues in under two minutes.
Start scanning — it's free