When tables are not structured accessibly, the data they contain can quickly become a meaningless sea of numbers, facts and figures to someone moving through them a cell at a time. Readers who cannot see the table cannot use visual cheats like checking the alignment and scanning back to the top headings to orient themselves as they go. Equivalent information needs to be encoded into the table to facilitate comprehension.
Tables are meant to be used for tabular information (data). Tables should never be used to lay out documents. When editing a book, recreate charts and tables using the default functionality of the software (i.e. the
Insert Table tool).
Tables have a logical reading order from left to right and top to bottom. Screenreader users can easily navigate to and examine data in tables. There are specific keyboard controls for reading tables that differ to the controls for reading regular text. When non-tabular text is rendered with tables, the reading controls are incorrect. This can make it confusing and difficult to read the document with a screenreader.
Do not present non-tabular information in a table format even if it presented as such in a book (i.e. a grocery list with two columns). Present such information as a list in two columns (see Formatting Columns).
normaldepending on the context. If you are unsure please contact the Production Coordinator.
Keep your tables simple without any extra modifications.
Captions come with the table (they’re provided by the publisher.) Descriptions, or Alt-text, is usually not provided by the publisher, and that’s what we add in. Just like with images, you will need to reinsert the captions. See below for more details.
A description should always be included to give context to a table. Never rely on the surrounding text to explain the presence of a table, especially when the table is offset from the content.
Descriptions should answer the question: “What is the table’s purpose and how is it organized?”
"A sample order form with separate columns for the item name, price and quantity."
Remember to keep the description short and direct. A good guideline it to keep it around 140 words. See the Alt-Text page for more information.
Captions are provided by the publisher, and are treated the same way as we would a caption for an image with one small difference–the caption goes above the table as opposed to below it.
For more information on Captions in general go to Captions page.
Table cells should be marked as table headers or header rows when they serve as labels to help interpret the other cells in the table. Correctly identified headers provide metadata that the reader can call up as needed as they navigate the data points.
Header Rowcheck box.
This ensures the header row is repeated across pages. Do this even if the table does not go over multiple pages:
Repeat as header row at the top of each page
Header Rowcheck box.
This ensures the header row is repeated across pages. Do this even if the table does not go over multiple pages so the screen reader can identify the header row from the rest of the table:
Repeat Header Rowbutton (it should be located to the far left of the ribbon menu)
Repeat as header row at the top of each page' ====EnsureAllow row to break across pages
is unchecked=== * Do not use split or merged cells in a Table. Screenreaders can’t handle it. * In Table Properties, under the Row tab, ensureAllow row to break across pages'' is unchecked (make sure to uncheck this for each row by clicking on Next Row then unchecking, etc.).
How to Convert a Table to Normal Text
Tips for Fitting Large Tables Within Page Margins
Q: I am editing a book that has very long tables that are images. I obviously need to convert them to readable tables in Word, but my question is should I create on very large table, or should I cut it down into smaller tables?
A: In this case you can break the sub-sections down into their own tables with each disorder its own table. You can caption each table with the name of the disorder.
Q: In Theomatics, instead of creating tables the author has used images. Should I put a producers note in for each 'table'?
A: Images of tables need to be presented as tables, just as images of text should be presented as text. You can see how to make accessible tables here:Tables. If you have questions about creating tables, let us know! We may need to add in a short alt description if the table is not sufficiently described in the surrounding text.
Q: Theomatics uses tables-A LOT-but it seems like they are not necessary. It appears that tables are used for formatting spacing, as opposed to actually creating a table. For example; the Chapter headings are in tables (which I remove.) But what should I do with the other 'tables'? There are instances in the book where similar information is presented as a list, and not a table. Should I just remove the tables and have the information formatted as 'Normal' with paragraph breaks between each line? I have included a screen shout of a page from the .doc file and the .epub file as examples. UPDATE: I have been thinking more about this as I move through editing other parts of the book. These sections could work as bulleted lists. If you need more examples I can give you other page numbers, or just open the epub yourself. There are oh so many.
A: You've got that right - none of the tables in this book should be there (as far as I can tell). As you say, they've been used for formatting purposes, a big no-no. All the tables should be converted to text within the narrative flow. I don't think these are true lists (a list of items); I would format these as normal paragraph text.