[Ucrfacultyandstaff] UCR Digital Deep Clean Week 9: Data Tables

[UCR Provost]

[image: UC Riverside logo]
The UCR Digital Deep Clean

[image: A disorganized dining room, including a dining table and chairs.]
Week Nine: The Dining Room

We’ve saved you a seat at the table. This week we're headed to the Dining
Room to tidy our data tables. In a physical dining room, a well-set table
makes a meal enjoyable and easy to navigate. In the digital world, the same
rule applies. By using proper table “etiquette,” you prevent confusion and
data errors for your colleagues and students, especially those viewing your
work on mobile devices. However, there is one golden rule to remember: Tables
are for data, not aesthetics!
New Resource

Join the Community of Practice channel on Slack
<https://ucriverside.enterprise.slack.com/archives/C0AP17UCM62>! This is a
collaborative space where Highlanders can share knowledge and best
practices regarding digital accessibility. Discussions here reflect our
community’s collective understanding of federal and UC systemwide
requirements.

Please be reminded that additional guidance and resources can be found on
the Digital Accessibility website
<https://accessibility.ucr.edu/digital-accessibility/siteimprove-training>.
The Weekly Guidance

[image: A formal dinner place setting (white plates and folded napkin
surrounded by silverware).]
Set the Table Properly

Tables should only be used to present data in rows and columns. When we
make too many adjustments to the layout, we create a maze for screen
readers. To make tables accessible, we must ensure they have a clear
"header row." This row acts as the label for everything beneath it,
allowing assistive technology to stay organized as it moves through the
information.
Accessible Spreadsheets

Screen readers navigate a grid linearly, one cell at a time. As a result,
the data must be predictable. An accessible sheet ensures that any user,
regardless of whether they use a mouse, a keyboard, or a screen reader, can:

   -

   Navigate from the start (cell A1) to the finish without getting stuck.
   -

   Understand the relationship between data points and their headers.
   -

   Interpret charts and images through text descriptions rather than just
   sight.

Key Tips:

   -

   Practice the "no-merge" rule. Merging cells breaks the navigation path
   for assistive technology and is the most common accessibility error.
   -

   A1 is the starting point. Always place your title or first data point in
   cell A1. Avoid "padding" your sheet with empty top rows.
   -

   Color doesn’t count. If you use green for "pass" and red for "fail," you
   must also type the words "pass" or "fail" in those cells.
   -

   Name the tabs. "Sheet 1" is a mystery. "Q1_Sales_Data" is a roadmap.
   Rename every tab descriptively.

Resources by Tool:

   -

   Google Sheets <https://support.google.com/docs/answer/6199477>
   -

   Microsoft Excel
   <https://support.microsoft.com/en-us/office/accessibility-best-practices-with-excel-spreadsheets-6cc05fc5-1314-48b5-8eb3-683e49b3e593>
   -

   Apple Numbers <https://support.apple.com/en-us/102031>
   -

   Tables on Websites <https://www.w3.org/WAI/tutorials/tables/>




The Weekly Challenge

[image: A person working on a spreadsheet on a laptop.]

Identify: Identify your public and most-shared files that contain data
tables.

Check the Box: Open the "Table Properties" on the data table and ensure the
"Header Row" box is checked.

Tidy Up: If you find a table that is only used to make text more visually
compelling on a webpage or document, move the text into standard paragraphs
or a bulleted list instead.
Faculty Focus

When building tables in your Canvas modules, simplicity is key.

   -

   Keep it simple. Avoid nested tables (a table inside a table) and
   merged/split cells. These "tangled" layouts are often impossible for screen
   readers to navigate logically.
   -

   Audit using UDOIT. Run UDOIT to scan your course. It will flag tables
   with accessibility issues and provide guidance on how to fix them.

XCITE Guidance on Spreadsheets
<https://teaching.ucr.edu/accessible-spreadsheets>
SDRC Guidance on PowerPoint Tables
<https://sdrc.ucr.edu/accessible-powerpoint-tables>
SDRC Guidance on Word Tables <https://sdrc.ucr.edu/accessible-word-tables>
Use the UDOIT Tool <https://teaching.ucr.edu/udoit-guide>

Website Wranglers
Web Accessibility Tables Tutorial <https://www.w3.org/WAI/tutorials/tables/>
SiteImprove: Table Cell Missing Context
<https://help.siteimprove.com/support/solutions/articles/80001058790-accessibility-rule-table-cell-missing-context-explained>

Data tables are grids used to organize information with logical
connections. To be accessible, they require HTML markup that identifies
header and data cells and defines their relationship, providing essential
context for users of assistive technologies.

   -

   Define the scope. Ensure your header cells are marked with the correct
   "scope" (identifying whether the header is for a column or a row).
   -

   Use Siteimprove. Siteimprove will check your site for "Layout Tables."
   If you’re using a table to position images or text, consider using a
   multi-column layout tool instead. Accessible tables should always have a
   <thead> and <th> tag.

Did You Miss Previous Weeks or Want to Get Ahead?

You can find all of the accessibility guidance and resources provided as
part of the Digital Deep Clean challenge on the Digital Accessibility
webpage!
Visit the Digital Accessibility Webpage to Learn More
<https://accessibility.ucr.edu/digital-accessibility>


Access barrier? Report digital accessibility issues or request remediation
<https://ucrsupport.service-now.com/ucr_portal?id=ucr_accessibility_form_login>
of inaccessible digital content.

University of California, Riverside

900 University Ave.

Riverside, CA 92521

951-827-1012 | ucr.edu <https://www.ucr.edu/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://scotmail.ucr.edu/pipermail/ucrfacultyandstaff/attachments/20260429/38e304d0/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image
Type: image/png
Size: 38168 bytes
Desc: not available
URL: <https://scotmail.ucr.edu/pipermail/ucrfacultyandstaff/attachments/20260429/38e304d0/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image
Type: image/png
Size: 2497940 bytes
Desc: not available
URL: <https://scotmail.ucr.edu/pipermail/ucrfacultyandstaff/attachments/20260429/38e304d0/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image
Type: image/png
Size: 1474069 bytes
Desc: not available
URL: <https://scotmail.ucr.edu/pipermail/ucrfacultyandstaff/attachments/20260429/38e304d0/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image
Type: image/png
Size: 1600588 bytes
Desc: not available
URL: <https://scotmail.ucr.edu/pipermail/ucrfacultyandstaff/attachments/20260429/38e304d0/attachment-0007.png>