Forum Discussion
Table with row headings
Hello,
Creating accessible tables with both column and row headings is essential for ensuring 508 compliance. Let’s explore how you can achieve this in both Storyline 360 and Rise 360:
Storyline 360:
In Storyline 360, you can create tables and designate the top row as a header row. Here’s how:
Select the table you’ve inserted into your slide.
Go to the Table Tools—Design tab on the ribbon.
Check the Header Row box to identify the top row as the header row. This will make it stand out and be recognized as the column headings.
You can also turn off the header row by unchecking the same box if needed.
While Storyline focuses on column headings, you can still provide context for row headings within the cell content. For example, include the row heading information in the first cell of each row.
Rise 360:
Rise 360 supports Revised Section 508 accessibility standards, including screen readers, keyboard navigation, and visible focus indicators.
Unfortunately, Rise 360 doesn’t natively support row headings in tables. However, you can work around this limitation:
Use a labeled graphic block: Labeled graphic blocks allow you to add visual flair to your courses while letting learners explore at their own pace. You can create a labeled graphic that visually represents your table and provides the necessary context for both column and row headings. Then, use alt text to describe the table in detail.
In the labeled graphic, include the column headings and row headings as labels. Describe the relationship between them in the alt text.
While this approach involves using an image, the alt text will provide the necessary information for screen readers and ensure 508 compliance.
I followed the directions given here and JAWS still doesn't announce the row headers with the data cells when moving from one row to another. Has anyone found a solution in the past 2 years?
Thanks for following up here, BelindaSpohn, and I’m really glad you shared what you’re seeing with JAWS!
You’re right, even when using the recommended approaches today, screen readers don’t consistently announce row headers with their associated data cells in Storyline or Rise. That’s a known limitation, and at the moment, there isn’t a way to make tables with both row and column headings behave as fully semantic, accessible tables for screen readers.
This is valuable feedback, especially coming from real-world testing with assistive technology. I’ve shared this specific scenario with our product team as accessibility feedback, since proper support for both row and column headers is an important requirement for 508 and WCAG compliance, not just a workaround situation.
I appreciate you revisiting this and calling it out again. These follow-ups help us better understand where the current tools fall short and where improvements would have the biggest impact for authors and learners alike.
