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

FAST Checklist review for IFT #32

Closed
1 of 10 tasks
svgeesus opened this issue Sep 14, 2021 · 3 comments
Closed
1 of 10 tasks

FAST Checklist review for IFT #32

svgeesus opened this issue Sep 14, 2021 · 3 comments
Labels
a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response.

Comments

@svgeesus
Copy link
Contributor

svgeesus commented Sep 14, 2021

The following sections of the FAST checklist seem to apply to the Incremental Font Transfer specification:

If technology allows visual rendering of content

  • 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
@svgeesus 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
@vlevantovsky
Copy link
Contributor

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.

@svgeesus
Copy link
Contributor Author

Closing as A11y review concluded with no issues

@svgeesus
Copy link
Contributor Author

The above checklist is also correct for the 9 July 2024 IFT WD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response.
Projects
None yet
Development

No branches or pull requests

2 participants