Skip to content
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

Supporting different table layouts #236

Open
jasonjgw opened this issue Aug 1, 2024 · 2 comments
Open

Supporting different table layouts #236

jasonjgw opened this issue Aug 1, 2024 · 2 comments

Comments

@jasonjgw
Copy link

jasonjgw commented Aug 1, 2024

In embossed braille, tables that exceed the line length are typically linearized. However, this may or may not be the desired outcome for braille display users, who may in some cases prefer to pan the display to the right in order to read subsequent table columns.

How can both scenarios be supported, particularly in view of the potentially different needs of embossed and displayed braille?

CSS media queries could presumably be written to give different layouts depending on line length, but if a braille display is used, the user may need to override the line length-conditional formatting, ideally without creating a custom style sheet.

What is the best way to support embossed and dynamically displayed scenarios in the eBraille format?

@bertfrees
Copy link
Member

I think media queries are indeed the answer. I can imagine there would be a user preference setting for allowing tables and other wide content to overflow the viewport. eBraille publications could then use the overflow-inline media feature to query this information and style tables accordingly.

Having end users create custom style sheets is something that is probably best to be avoided, and it doesn't seem necessary for this use case.

@jasonjgw
Copy link
Author

jasonjgw commented Aug 3, 2024

Support for appropriate media features and the associated user configuration options (for this use case and others) is presumably an eBraille reading system requirement that should be specified somewhere. I think we want it to be implemented consistently among reading systems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants