W3C home > Mailing lists > Public > public-eo-plan@w3.org > July to September 2017

Re: WAI Mobile Resources proposal

From: Bakken, Brent <brent.bakken@pearson.com>
Date: Tue, 29 Aug 2017 10:18:29 -0500
Message-ID: <CAE6qf-EMv9m57y0eFVN-UJXurp5Vu8W5UU32=c-5M4xcN2Y0dw@mail.gmail.com>
To: Susan Hewitt <susan.hewitt@deque.com>, public-eo-plan@w3.org
Cc: Sharron Rush <srush@knowbility.org>, "Wise, Charlotte" <cwise@visa.com>
[adding plan team email address]

Thank you for sending Susan and Charlotte.
Planning team will look over your plan of attack and provide feedback so
you can get started. Give us a couple of days to respond.

Thanks,
Brent



Brent A. Bakken
Director, Accessibility Strategy & Education Services
Pearson

512 202 1087
brent.bakken@pearson.com

Learn more at pearson.com

[image: Pearson]


On Tue, Aug 29, 2017 at 9:30 AM, Susan Hewitt <susan.hewitt@deque.com>
wrote:

> Brent, Sharron, please share this with the planning group. Thanks!
>
>
> --
>
>
> Hi folks,
>
>
>
> Charlotte and I have reviewed and discussed the existing WAI mobile pages
> and propose the following changes:
>
>
>
> 1.      The first two sections of the Web Accessibility Developer Intros
> created  (Mobile Concepts <https://w3c.github.io/wai-mobile-intro/mobile/>
>  andWAI Guidance
> <https://w3c.github.io/wai-mobile-intro/mobile/wai-guidance/>) have a
> broader application than as a tutorial for developers. They serve as an
> introduction and overview to all audiences. We have two options for
> addressing this content:
>
> ·         The best option would be to move this content into the broader
> WAI mobile section, replacing the current overview page (
> https://www.w3.org/WAI/mobile/) entirely.
>
> ·         An alternative would be to duplicate much of this content on
> our overview page(s).
>
>
> In either scenario, the tutorials themselves would be prominently linked
> to and described.
>
>
> 2.      As for the other two existing mobile pages, we recommend
> completely removing them. Some of the more general concepts and information
> on those pages are covered in the Developer Intro content. In our draft,
> we'll clearly note where the content that is still relevant has been
> included in new drafts but we believe the bulk of the content is either
> unneeded at this point or is a replication of content elsewhere on the WAI
> site.
>
> 3.      We need to add much more specific language and information about
> native applications. How WCAG addresses and applies to accessibility for
> native apps is not addressed clearly enough in our existing content,
> including in the new Web Developer's guide. We do a good job with Web for
> mobile but must do more to help all audiences with native apps. That's
> absolutely a topic visitors will look for.
>
>
> We will reach out to members of the MATF as well for input.
>
>
> Thanks,
>
> Susan and Charlotte
>
> --
> Susan Hewitt, CPACC
> Senior Accessibility Consultant
> Deque Systems, Inc
> deque.com
>
>
Received on Tuesday, 29 August 2017 15:18:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 29 August 2017 15:18:56 UTC