- From: Janina Sajka <janina@rednote.net>
- Date: Fri, 30 May 2025 20:31:15 -0400
- To: Accessibility at the Edge <public-a11yedge@w3.org>
Colleagues: The edits agreed and logged in [https://www.w3.org/2025/05/28-a11yedge-minutes.html](minutes of our telecon on 28 May) are now applied to Capabilities. PLEASE REVIEW!! Your Editor has made a few additional tweaks! 1.) Dyslexia Friendly Fonts https://A11yEdge.github.io/capabilities/#dyslexiafont Trade-Offs Switching to dyslexia-friendly fonts may slightly alter the visual appeal or branding of the site. Designers and stakeholders may wish to approve font changes. However, most application of this feature will be user, and not source authorized. Benefit Using dyslexia-friendly fonts reduces cognitive load and improves the reading experience for some, possibly even many users living with dyslexia, making the site more inclusive. Automatability In some cases—Automated tools can interchange instances of inaccessible typefaces for dyslexia-friendly equivilants. 2.) Shadow and Outline https://A11yEdge.github.io/capabilities/#shadowout We discussed, but minutes lack any disposition for editing other than the capital S in Automatability. Thehe Capital letter following the mdash is correct and conforms to our convention throughout this document. 3.) Forms Validation https://A11yEdge.github.io/capabilities/#formvalid Source Too often forms are not fully tested for accessibility support such as input timing, focus management, programmatically associated field and form control labeling, and clear visual and screen reader friendly error notification. Also, frequently forms originate from third-party service providers and provide the web site owner little or no ability to remedy such failures at source. Trade-Offs post-source remediation may be the only viable option, especially with inprocess third party forms. Benefit Post-source accessibility Support can make forms interaction more efficient, especially for users who require enhanced support particularly in situations where the enhanced content is not intended for all page visitors, but for certain audiences only, such as screen reader users for certain users living with cognitive or learning disabilities. Automatability In some cases--Automated tools can detect form validation errors and announce them via assistive technologies, but verifying usability across different screen readers and ensuring appropriate messaging still requires human testing. 4.) All instances of "This is not a redundant capability" are now removed. As ever our document is available here: https://A11yEdge.github.io/capabilities/ Best, Janina -- Janina Sajka (she/her/hers) Accessibility Consultant https://linkedin.com/in/jsajka The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa Linux Foundation Fellow https://www.linuxfoundation.org/board-of-directors-2/
Received on Saturday, 31 May 2025 00:31:20 UTC