Handling long tables (with accessibility features)

PilcrowandStanza · 11-10-2024, 08:04 AM

So, I'm working on a book that has a few fairly long tables. Each is broken into sections with keep options, and ideally the header should automatically appear at the top of each section.

However, the epub is breaking them onto new pages for each section, and leaving the main header behind (see attached)

In the current published version they are included as rasterized images (set within a text box), and they displayed great, but I'm trying to figure out how best to arrange them so screen readers can handle them.

Is there anyway to make the header repeat with each section?
Or would I have to create separate tables for each instead of one long one? (or a couple together based on the number of lines that should fit on a page)

Later in this book there's a wide table with several columns. Would I need to break that down into more manageable chunks?

Any advice, explainers, or examples welcome.

Thanks

Turtle91 · 11-10-2024, 08:47 AM

Try looking through this post/thread.

Turtle91 · 11-10-2024, 09:00 AM

As for headers repeating across pages… good question. That mostly depends on the device and how they choose to support things like “display: table-header-group” or like some kindles allow viewing large tables in a pop out.

There’s not much you can do except follow table best practices and use the <thead> to identify your column headers.

11-10-2024, 08:04 AM	#1
PilcrowandStanza Member Posts: 12 Karma: 10 Join Date: Dec 2023 Device: none	Handling long tables (with accessibility features) So, I'm working on a book that has a few fairly long tables. Each is broken into sections with keep options, and ideally the header should automatically appear at the top of each section. However, the epub is breaking them onto new pages for each section, and leaving the main header behind (see attached) In the current published version they are included as rasterized images (set within a text box), and they displayed great, but I'm trying to figure out how best to arrange them so screen readers can handle them. Is there anyway to make the header repeat with each section? Or would I have to create separate tables for each instead of one long one? (or a couple together based on the number of lines that should fit on a page) Later in this book there's a wide table with several columns. Would I need to break that down into more manageable chunks? Any advice, explainers, or examples welcome. Thanks Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre wants to access Accessibility features on Mac?	rosalita	Calibre	4	08-27-2020 11:07 PM
Calibre on Mojave "would like to control this computer using accessibility features"	sparker	Calibre	1	10-09-2018 11:58 PM
Calibre 2.0 Viewer link handling: underlines too long	Katsunami	Calibre	2	08-22-2014 03:23 PM
Amazon Bringing New Accessibility Features to Free Kindle Reading Apps	Loosheesh	News	13	05-03-2013 02:18 PM
KFHD - Silk browser removed key accessibility features	goggin	Kindle Fire	1	09-15-2012 12:08 PM

11-10-2024, 08:47 AM	#2
Turtle91 A Hairy Wizard Posts: 3,291 Karma: 20171067 Join Date: Dec 2012 Location: Charleston, SC today Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire	Try looking through this post/thread.

11-10-2024, 09:00 AM	#3
Turtle91 A Hairy Wizard Posts: 3,291 Karma: 20171067 Join Date: Dec 2012 Location: Charleston, SC today Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire	As for headers repeating across pages… good question. That mostly depends on the device and how they choose to support things like “display: table-header-group” or like some kindles allow viewing large tables in a pop out. There’s not much you can do except follow table best practices and use the <thead> to identify your column headers.

Advert