- From: Joshue O Connor <joconnor@w3.org>
- Date: Tue, 30 Jun 2020 14:54:48 +0100
- To: public-a11y-functional-needs@w3.org
- Cc: Shadi Abou-Zahra <shadi@w3.org>
Hi, [+ Shadi on cc] After discussion with Michael, he asked me to send my thoughts on the FAST checklist content to this list. [1] Please see below - I have a bunch and will send more in separate mails but this first round is mainly editorial but could be helpful. Each of the 'Feature' points should remove the 'If technology allows' part it is repetitive - that can be in the explanation - so the table can be re-written as follows: Feature 1: Visual rendering of content A goal is for the spec to be light weight, understandable - quickly - and be usable by people reviewing specs without having a deep knowledge of accessibility in the related subject. A new suggested format for the current checklist (as is): Feature #1: Visual rendering of content Feature #2: Provides author control over colour Feature #3: Provides features to accept user input Feature #4: Provides user interaction features Feature #5: Defines document semantics Feature #6: Provides time-based visual media (see also the Media Accessibility Checklist) Feature #7: Provides Audio () Feature #8: Allows Time limits Feature #9: Allows Text content Feature #10: Provides content fallback mechanisms, whether text or other formats Feature #11: Provides visual graphics Feature #12: Provides internationalization support Feature #13: Provides content directly for end-users Feature #14: Defines an API Feature #15: Defines a transmission protocol. [1] https://w3c.github.io/apa/fast/checklist.html Ideas welcome! Thanks Josh -- Emerging Web Technology Specialist/Accessibility (WAI/W3C)
Received on Tuesday, 30 June 2020 13:54:54 UTC