How to Fix Accessible Names in Rise 360

Overview

Most Rise blocks build an accessible name for you automatically from their visible text, a Button block's label, a link's text. The gap shows up in two places: markers inside interactive blocks like Labeled Graphic, Process, or Timeline, which need their own label text set explicitly, and Embed blocks, where you've pasted in custom HTML or an iframe that Rise has no control over. A marker with no label, or an embedded icon button with no name, is just as invisible to a screen reader as if it wasn't there.

Step-by-step instructions

1. 1

   For a Labeled Graphic, Process, Timeline, or Sorting block: click each marker or item.

2. 2

   Check the text label field for that marker, if it's blank or just says something like "Marker 1," give it a real, descriptive name.

3. 3

   Write the label as if the learner can't see the image at all, "Engine temperature gauge," not "Icon 3."

4. 4

   For an Embed block with custom HTML: open the embedded code and look for buttons, links, or icons without visible or `aria-label` text.

5. 5

   Add clear label text directly in the embedded HTML, this has to be fixed in the source you pasted in, Rise can't add it for you.

6. 6

   Preview the block and turn on a screen reader (or the Screen Reader Simulation in this report) to confirm every control now announces something meaningful.

Screenshots

Tips

• If a marker or button's label would only make sense to someone already looking at the graphic, it's not descriptive enough yet.
• Two markers on the same graphic should never share an identical label, if a learner can't tell them apart by ear, make the wording more specific.
• For embeds, ask whoever built the original widget for accessible markup before pasting it in, it's much faster than patching it after the fact.

Common mistakes

• Interactive block markers left with their default placeholder label instead of real, descriptive text.
• Embed blocks built from third-party code that was never checked for accessible names in the first place.
• Assuming an icon is self-explanatory just because its meaning is obvious to a sighted author.

Why it matters

A screen reader announces a control by its name alone. If that name is missing, generic, or just an icon, the learner has no idea what it does.