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
{{ message }}
This repository was archived by the owner on Jul 31, 2018. It is now read-only.
#. Add a note in the W3C Editor's Draft itself on how to submit comments, e.g send email to , [email protected],
#. Define all acronyms, such as "AAPI", which I assume means "Accessibility API, Application Programming interface". Why are there A-APIs and not just API's?
#. Add the end users responsibility for settings and configurations to the list, such as "...describes how technologies, content authoring, user agents and end user settings work together ...".
#. Add example of each checkpoint, such as from HTML 5.1, CSS or some web technology to which the checkpoint is referring.
#. Love the acronym of the doc - FAST.
#. Change "Authors can ..." to "Technology specification provides for ..." in the Document semantics section.
#. Merge sections on Visual Media with Audio.
#. Add "Alternative user input modalities" to User Input section, such as Sign Language video input as an alternative to text keyboard, or gesture alternative to mouse clicks, etc.
The text was updated successfully, but these errors were encountered:
https://lists.w3.org/Archives/Public/public-apa/2017Feb/0029.html
Some initial quick comments:
#. Add a note in the W3C Editor's Draft itself on how to submit comments, e.g send email to , [email protected],
#. Define all acronyms, such as "AAPI", which I assume means "Accessibility API, Application Programming interface". Why are there A-APIs and not just API's?
#. Add the end users responsibility for settings and configurations to the list, such as "...describes how technologies, content authoring, user agents and end user settings work together ...".
#. Add example of each checkpoint, such as from HTML 5.1, CSS or some web technology to which the checkpoint is referring.
#. Love the acronym of the doc - FAST.
#. Change "Authors can ..." to "Technology specification provides for ..." in the Document semantics section.
#. Merge sections on Visual Media with Audio.
#. Add "Alternative user input modalities" to User Input section, such as Sign Language video input as an alternative to text keyboard, or gesture alternative to mouse clicks, etc.
The text was updated successfully, but these errors were encountered: