- From: lisa.seeman <lisa.seeman@zoho.com>
- Date: Mon, 20 Jul 2020 14:05:26 +0300
- To: "public-personalization-tf" <public-personalization-tf@w3.org>
- Message-Id: <1736be48773.c827a9f4226430.3693673067953264975@zoho.com>
Hi Some things seem missing from the abstract, such as use cases for distractions. Does that matter? I also find the first sentences limiting: This specification provides web content authors a standard approach to support web users who are persons with various cognitive and learning disabilities, including users who: I think we want to interest developers for other usecase, such as familiar keys for gaming. So something like This specification provides web content authors a standard approach to ddapt content for the needs and prefrences of the user. For example, to provide support web users who are persons with various cognitive and learning disabilities, including users who: Also I am not sure I agree with the following: Transform the user interface (UI) through the addition, removal, or adaptation of content which otherwise tends to have a negative impact on Augmentative and Alternative Communications (AAC) users; Maybe these are a few points that have been merged, such as : 1. Transform the user interface (UI) through the addition, removal, or adaptation of content to make it more usable and overcome accessibility issues for people with learning and cognitive disabilities 2. Adapt and augment content with familiar symbols for users with Augmentative and Alternative Communications (AAC) so that they can use and share content 3. Remove content that may have a negative impact or distract the user I am also not sure we want to limit ourselves to element-level attributes. Does that work in module 2. All the best Lisa Seeman http://il.linkedin.com/in/lisaseeman/, https://twitter.com/SeemanLisa
Received on Monday, 20 July 2020 11:05:48 UTC