You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a defined way for a non-visual rendering to be created. Does not apply; this specification is about the fonts used to create the visual rendering from the content, and not the content itself (which will define how to create non-visual rendering such as text to speech)
Content can be resized. Yes, the font can be used to render text at different sizes
Luminosity and hue contrast can adapt to user requirements. Does not apply; the CSS or whatever is requesting the font controls this, not the font.
Text presentation attributes can be changed. Does not apply; the CSS or whatever is requesting the font controls this, not the font.
Visual presentation of pointers and cursors can be adjusted. Does not apply; the CSS or whatever is requesting the font controls this, not the font.
Changing content presentation does not render it unreadable. Does not apply; the CSS or whatever is requesting the font controls this, not the font.
Technology does not allow blinking or flashing of content, or provides a feature for users to quickly turn it off or permanently disable it. Does not apply; the CSS or whatever is requesting the font controls this, not the font.
It is possible to make navigation order correspond to the visual presentation. Does not apply; the CSS or whatever is requesting the font controls this, not the font.
If technology defines an API
If the API can be used for structured content, it provides features to represent all aspects of the content including hidden accessibility features. Does not apply; this API transfers just the fonts, not the structured content
If the API relies on user agents to generate a user interface, the specification provides guidance about accessibility requirements needed to enable full interaction with the API. Does not apply; this API does not require a user interface
The text was updated successfully, but these errors were encountered:
svgeesus
added
the
a11y-tracker
Group bringing to attention of a11y, or tracked by the a11y Group but not needing response.
label
Sep 14, 2021
Regarding the question: "Changing content presentation does not render it unreadable"
Missing a font a can make content presentation unreadable, if the particular missing font supports a character set not supported by any other fonts available. In this regard, IFT will effectively be a prevention mechanism, an aid that ensures the content is always readable.
The following sections of the FAST checklist seem to apply to the Incremental Font Transfer specification:
If technology allows visual rendering of content
If technology defines an API
The text was updated successfully, but these errors were encountered: