- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Thu, 12 May 2016 13:38:00 +0200
- To: Shawn Henry <Shawn@w3.org>, "Bakken, Brent" <brent.bakken@pearson.com>, "Halter, Adina" <adina_halter@cable.comcast.com>
- Cc: wai-eo-editors <wai-eo-editors@w3.org>, Wilco Fiers <wilco.fiers@deque.com>, Katie Haritos-Shea <ryladog@earthlink.net>
[+Katie +Wilco if you are interested following yesterday's discussion] Hi Adina, Brent, and Shawn, Thank you for your reviews. I think most issues are editorial ones that do not need discussion. There are only few issues related to the "Learn more" section but hopefully we can resolve these by email so that we do not need a teleconference call tomorrow: # Expanding "WCAG" - All acronyms should be expanded or an explanation should be provided - We should do that for "WCAG" since it is a new term for our audience - Expanding it as suggested makes the section hard to read - example: http://w3c.github.io/wai-showcase-examples/customizable.html#resources - Option 1: Keep it expanded as-is in the example - Option 2: Replace order to read "Web Content Accessibility Guidelines (WCAG 2.0)" and make only "WCAG 2.0" a link - Option 3: Drop "Web Content Accessibility Guidelines" altogether and only keep "WCAG 2.0" as a link (the linked resource explains the term) - Option 4: other ideas? # Adding UAAG - UAAG has been added to "Customizable Text", which makes sense there: http://w3c.github.io/wai-showcase-examples/customizable.html#resources - But there are also other topics that relate to UAAG, such as Keyboard - UAAG and its SC links also seem too technical for the target audience - Option 1: Keep UAAG in "Customizable Text" for now and revisit later - Option 2: Remove UAAG altogether for now and revisit later - Option 3: Add UAAG throughout before publication (lots of effort!) - Option 4: Add UAAG only (without the SCs) for now and revisit later - Option 5: other ideas? # "Learn more" - The recent changes have added content and verbosity (sub-lists) to this section, making it quite daunting and overwhelming for newbies - Option 1: It is fine for now but let's revisit after publication - Option 2: My suggested solutions for the previous two questions on Expanding "WCAG" and Adding UAAG will revert some of these problems - Option 3: Use expand/collapse (this is not meant as a joke!) - Option 4: I have some presentation or styling suggestions to help - Option 5: other ideas? Best, Shadi -- Shadi Abou-Zahra - http://www.w3.org/People/shadi/ Activity Lead, WAI International Program Office W3C Web Accessibility Initiative (WAI)
Received on Thursday, 12 May 2016 11:38:17 UTC