Price lists and timetables screen readers can actually read
Short answer: Price lists, opening hours, size charts, comparison grids and spec sheets are easy for sighted visitors to scan, but a screen reader only understands a table if its HTML says which cells are headers. Use a real <table> with <th> for header cells and <td> for data, add scope="col" or scope="row" where the header direction isn't obvious, give the table a <caption>, avoid merged cells where you can, and never build tables out of images or layout grids. Then test it with a screen reader for five minutes.
Why table markup matters
MDN's guide to table accessibility explains that screen readers identify all headers and use them to make programmatic associations between headers and the cells they relate to, so that a blind user hears, for example, "Saturday, Opens, 9:00" rather than a meaningless string of times. The W3C's Web Accessibility Initiative tutorial on tables says the same thing from the author's side: accessible tables need markup that indicates header cells and data cells and defines their relationship, header cells must be marked up with <th> and data cells with <td>, and complex tables may need explicit associations with scope, id and headers.
Without that markup, a visitor using a screen reader hears numbers and words with no context. On a business site that can mean they can't tell your prices, sizes or hours apart.
Where small business sites use tables
- Opening hours by day
- Price lists for services or packages
- Size charts on clothing and shoe shops
- Product comparison grids
- Delivery cost tables by area or weight
- Technical specifications
- Class or event timetables
All of these are data tables, so all need proper markup.
The basic recipe
- Use a real HTML table. Not an image of a table, not a PDF, not a set of
divs styled to look like rows. - Mark header cells with
<th>. Column headings across the top, and row headings down the side if there are any. - Add
scopewhen direction isn't obvious. The WAI tutorial recommendsscope="col"orscope="row"for tables with unclear header directions. - Add a
<caption>. The tutorial describes a caption as identifying the overall topic of a table, useful in most situations, for example "Opening hours from 1 December". - Group sections with
<thead>,<tbody>and<tfoot>, which MDN covers as better table structuring.
A simple opening hours table would have a caption, a header row with "Day", "Opens" and "Closes", and each row starting with a <th scope="row"> for the day name.
Avoid the hard cases if you can
Tables with cells spanning several rows or columns are the hardest for assistive technology. The WAI tutorial explains that irregular headers need column and row groups, and multi-level headers need id and headers attributes on every cell. Before going there, ask whether the table can be simplified:
- Split one large table into two smaller ones with their own captions.
- Repeat a value in each row instead of merging cells vertically.
- Move notes out of the table into text below it.
Simpler tables are also easier to read on phones.
Don't use tables for layout
The WAI tutorial notes that tables aren't meant for layout and that CSS should handle visual presentation. Old themes and some email-style page builders still use tables to position content. Screen readers may then announce "table with 3 columns" around ordinary text, which is confusing. If your page builder does this, check whether it has a modern layout option.
Page builders and CMS editors
Most CMS editors include a table block. Check:
- Whether it lets you mark the first row and first column as headers. Many have a "header row" toggle.
- Whether it supports a caption.
- Whether it outputs real
<table>markup. Inspect the page to confirm.
For plugins that build pricing tables or comparison grids, look at the output too. Some produce attractive cards without any table semantics, which is fine if each card is a clear self-contained list, but poor if the design implies a grid of comparable values.
Test it quickly
- With a screen reader: VoiceOver on Mac and iPhone and NVDA on Windows are free. Navigate into the table and move cell by cell; you should hear the header announced with each value.
- With the browser's accessibility tree: developer tools show whether cells have header relationships.
- On a phone: check that the table scrolls sideways in its own box or reflows, rather than breaking the page.
Make the content work for everyone
Good markup doesn't fix a confusing table. Keep header labels short and specific ("Price per hour", not "Info"), put units in headers rather than repeating them in every cell, use text rather than colour alone to mark things like "fully booked", and write out abbreviations that a screen reader would mispronounce. If a table has footnote symbols, explain them in text right below it. These small choices help sighted visitors on phones as much as screen reader users, and they make the table easier for you to maintain.
An illustrative example
A hypothetical Ottawa dance studio published its class timetable as an image exported from a design tool. A parent using a screen reader couldn't find class times and called instead. The studio rebuilt it as an HTML table with a caption naming the term, days as column headers, class times as row headers with scope="row", and no merged cells. The timetable now updates in the CMS, reads correctly in VoiceOver and NVDA, and can be found by search engines.
FAQ
Is a list better than a table?
If the data has only one dimension, yes. Use a table when values are compared across rows and columns.
Does scope matter for simple tables?
Screen readers often guess correctly for simple tables, but adding scope removes the guesswork.
Can I use an image of the table with alt text?
Long alt text for a table is hard to use. Provide a real table instead.
Do tables need to be responsive?
Yes. Let them scroll horizontally in a container or reflow on small screens.
If you'd like your price lists, timetables or size charts checked for screen reader access, send us the page links.