Re: Updating mobile & accessibility resources

Thanks, Peter!

These were written before MWABP. It would be great if we could integrate MWABP some. Do you have specific suggestions on points in MWABP that would fit in <http://www.w3.org/WAI/mobile/experiences>? For example, how would we address 3.5.3 Design for Multiple Interaction Methods ?

~Shawn


On 8/11/2012 3:51 PM, Peter Thiessen wrote:
> Hi Vicki,
>
> I didn't have access to that WIKI page
> (http://www.w3.org/WAI/EO/wiki/Mobile_pages) so I thought I'd just
> email my comments over, especially since they're only minor. My
> comments may need to be elaborated - just let me know if so.
>
>
> 1. http://www.w3.org/WAI/mobile/
> An accurate overview of summarizing the benefit of combining both WCAG
> &  MWBP into the design process. I don't have much to say really.
>
> In the intro the term developer is used. From my experience, this sort
> of wording can be suriprisingly impactful in scaring off
> non-developers. A designer might read the word "developer" and then
> run away screaming. Just my two cents.
>
> Perhaps this bit about "the process more efficient" could be expanded.
> It may be benefical to emphasise the high cost of putting off
> following either WCAG/MWBP until later in a project's life cycle. A
> developer/project planner might read the brief explanation as "Great,
> I'll follow one now and do the other later, since they overlap
> anyways..". I can elaborate if need be. But then again, perhaps for an
> overview this amount of information is perfect.
>
>
> 2. http://www.w3.org/WAI/mobile/experiences
> Looks good. My only comment is about the focus on content. I realise
> content is the focus here but designers/developers may think the
> principles provided only apply to Web sites and not to Web
> applications. Explicitly emphasizing that both content and
> UI/application are covered may help increase the relevancy of this
> page, especially with developers.
>
> It's a shame the MWABP (http://www.w3.org/TR/mwabp/) mainly only
> covers different forms of caching techniques (bandwidth/memory/..), or
> it would be great to put along side MWBP as reference on certain
> crosover points - especially in the Operable section.
> (Well OK there is one crossover point .. "3.5.3 Design for Multiple
> Interaction Methods" :-)
>
>
> cheers,
> +peter
>
...[snip]

Received on Monday, 13 August 2012 13:33:10 UTC