Re: Minutes of Mobile A11y TF teleconference of 31 March 2016

We're in the process of exploring what WCAG.NEXT will look like... one
option is not having extensions, and just going to the next version of
WCAG, which would make the problem go away.

Otherwise what would you call this extension, if you could "name that
child"?
Touch screen and small screen accessibility?

On Fri, Apr 1, 2016 at 3:49 AM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

>
>
> On 01/04/2016 01:05, David MacDonald wrote:
>
>> Mobile seems to be the buzz these days, and the general public has not
>> advanced past ... If we offer a course in Mobile accessibility, and
>> another course in Pointer events accessibility, or touch events
>> accessibility. I think the mobile a11y course will triple the attendance.
>>
>
> Well, you wouldn't market a course just on "Touch events". And even if you
> wanted to, you'd call it something a bit more general such as "Making
> content and applications on touchscreen devices accessible".
>
> In the Microsoft Event this week the keynote the statement was "we are
>> mobile first, meaning users should be able to access their work across
>> all platforms and technologies, that's mobile computing, the user is
>> mobile"
>>
>> But I'm fine with dumping the word mobile, if it interferes with our
>> mission, but we should do so after consulting stakeholders.
>>
>
> "Mobile" as a marketing buzzword is fine. "Mobile" as a categorisation for
> technologies/problems/recommendations which are not exclusive to
> smartphones/tablets is what I take issue with. That is all.
>
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>
>