RE: MATF Minutes September 24, 2020

Hi Chris,

I see those distinctions, but we are writing guidelines for people who have to cater to both, at the same time.

-Alastair


From: Chris McMeeking <chris.mcmeeking@deque.com>
Sent: 24 September 2020 23:56
To: Alastair Campbell <acampbell@nomensa.com>
Cc: Patrick H. Lauke <redux@splintered.co.uk>; public-mobile-a11y-tf@w3.org
Subject: Re: MATF Minutes September 24, 2020

I don't see the same distinctions as you do. I see:

- users where the default expectation is mouse and keyboad interaction
- users where their hands and a touch screen are the only default expectation

These two distinct user groups are significantly more important than any technical boundaries you wish to fabricate.

The reality is: Web Browsers are themselves native applications, with identical limitations as the platforms they are built around.


Chris

PS: done with this thread. Reach out to me for direct input if you would like. I hate email! :)

On Thu, Sep 24, 2020, 6:43 PM Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
It looks like there are a couple of distinct perspectives here.

Obviously there are differences between mobile app, mobile hybrid & mobile web. And we must create guidelines that apply to web, ideally more. If something doesn't work across both mobile web & desktop web then it doesn't work as a web guideline.

We need to understand the separate conversations but come to one conclusion.

Please be clear about which context your comments are coming from. It wasn't particularly clear from the meeting minutes, but that could just be because it's lacking the context of the call.

Kind regards,

-Alastair


-----Original Message-----
From: Patrick H. Lauke <redux@splintered.co.uk<mailto:redux@splintered.co.uk>>
Sent: 24 September 2020 20:28
To: Chris McMeeking <chris.mcmeeking@deque.com<mailto:chris.mcmeeking@deque.com>>
Cc: public-mobile-a11y-tf@w3.org<mailto:public-mobile-a11y-tf@w3.org>
Subject: Re: MATF Minutes September 24, 2020

On 24/09/2020 20:18, Chris McMeeking wrote:
> @patrick: The naivety is in assuming that the Desktop and the Mobile
> conversation are the same discussion. Different users, different input
> mechanisms, etc. These conversations must be had separately in order
> for them to be comprehensible.

Then who is having the desktop conversation, officially? Because I'm fairly sure that AGWG as a whole is expecting the TF here to usher through the SC in general, not just look at the mobile-specific aspect.
And note that the end result must still be a single SC that applies to all platform, it can't be scoped to "for mobile" or "for touch devices", or even give a "for touch, it must be this, for mouse/stylus, it must be this" as devices inputs can be fluid and change at any moment (e.g. a mouse being paired with a nominally touch-only device; a "desktop"
device with a touchscreen as well as a mouse; etc)

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux

twitter: @patrick_h_lauke | skype: patrick_h_lauke
--
Inclusive Design 24 (#id24) https://inclusivedesign24.org