- From: Shawn Henry <shawn@w3.org>
- Date: Thu, 6 Oct 2016 16:56:42 -0500
- To: Susan Hewitt <susan.hewitt@deque.com>
- Cc: wai-eo-editors <wai-eo-editors@w3.org>
On 10/6/2016 3:28 PM, Susan Hewitt wrote: > https://github.com/w3c/wai-eo-mobile/wiki/Requirements-Analysis Great start! Some initial thoughts... Question: Is this RA just for the one page <https://www.w3.org/WAI/mobile/>, or for all the mobile accessibility-related documents? Maybe we need the address both -- overall what are the purpose/objectives of the suite of info, and then specifically what are the goals of the main page? (I'm not really sure the difference between Purpose & Objectives - but no biggie. ;-) Purpose: This seems mostly from our perspective. What do you think about tweaking it to also include from the users' perspective? Also, maybe adding User Tasks to the RA, e.g.: ** We're [updating our website | developing a mobile app] and want to know what we need to do to make it accessible. ** We're writing an RFP for [updating our website | developing a mobile app] and want to include conforming to mobile accessibility guidelines/standards in the RFP. Does WAI have mobile accessibility guidelines? Audience+ Policy makers [this is an important audience in Europe right now] Objectives: For the main page, I think the key objectives include: * People understand that most mobile accessibility issues are already covered in WCAG 2.0. Some are covered in UAAG 2.0. * People know that WAI is working on additional guidance on mobile accessibility, including updates to WCAG -- but *not* separate mobile accessibility guidelines. * People can get to the Mobile Accessibility Task Force info. Re: "Explain how the disabling nature of mobile technology can affect more than just those with people with disabilities." I'm not sure this is an important purpose these days. The initial purpose/objective years ago was a bit different: to show people who wanted to make their content work on a mobile devices that we already cover a lot of those issues through accessibility for people with disabilities! Also, based on previous EOWG discussions, some people are uncomfortable with "disabling nature of mobile technology" without a lot of context around it. Re: "Summarize the applicability of WCAG 2.0 mobile, including native applications." * For the main page, do we summarize it or state it? * For the sub-pages we more than summarize it -- detail it, yes? * Also, UAAG, yes? "Resource and Task Analysis": Consider tweaking to avoid confusion with "User Task Analysis" :-) When you're ready, I think we want EOWG & Judy & probably Mobile Accessibility Task Force to take a look at this... Best, ~Shawn
Received on Thursday, 6 October 2016 21:56:59 UTC