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

Inference rule for visual adjustments (displayTransformability) #181

Open
HadrienGardeur opened this issue Jan 4, 2025 · 0 comments
Open

Comments

@HadrienGardeur
Copy link
Member

HadrienGardeur commented Jan 4, 2025

Based on our work for parsing HTML/CSS (#180) we'll add a new inference rule for visual adjustments.

For this issue, we'll use a fairly naive approach where the metadata is only inferred if problematic CSS rules (TBD) are completely absent from both external stylesheets and inline styles.

Nonvisual reading ("accessModeSufficient": "textual") is also a pre-requisite to infer this metadata.

For further info, we can check the Daisy KB and the page dedicated to this property:

The displayTransformability value is used to indicate that a publication does not restrict the ability of users to modify the display of textual content (e.g., to change the font family, font size, line height and word spacing).

In order to set this value, all text content must be encoded as text (i.e., there must not be any images of text). In addition, absolute length units must not be used in the styling (e.g., pixels and points).

It is not required that a publication provide the means of transforming the text. It is expected that users who require this feature will have a reading system that with display transform options.

Since this additional inference requires parsing all HTML/CSS resources, it'll be added behind a new optional flag for both rwp manifest and rwp serve.

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

No branches or pull requests

2 participants