-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Making Tables Accessible in FXL #41
Comments
You can provide an extended description for a table using either The advantage of The Linking out to the table in a reflowable document is a good option. If you're using an image of the table, you could put the link on the image to let users click to open it. The EPUB working group currently has a task force looking at techniques for making fixed layouts more accessible right now, so I expect there will be more discussion of this in the near future. |
Thanks Matt! I am in the working group, so this is helpful information. I was curious about how well the Aria roles worked for tables, and I thank you for the information! |
I am researching how to create accessible tables in FXL layout, and the only options I can come up with are to create the table directly in the HTML with the correct markup (as already described on the Knowledge Base,) or use Alt-text (with complex description depending on the table.) Descriptions could follow recommendations for summaries starting with describing the header and rows and then breaking down the data in reading order. If the description was too long for Alt-text we could use a link to go to another location of the book with the full description or HTML table, or we could put the description in a hidden aside tag below the table and make note of the longer description in the Alt-text. Would this work for fixed layout?
There was another post here about complex image descriptions that recommended tiling for complex images, but to me that seems too much for tables and would break up the data and make it harder to follow.
Thoughts?
The text was updated successfully, but these errors were encountered: