W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2019

RE: AGWG Meeting Minutes for Tuesday, May 28, 2019

From: Abma, J.D. (Jake) <Jake.Abma@ing.com>
Date: Wed, 29 May 2019 06:59:39 +0000
To: 'Detlev Fischer' <detlev.fischer@testkreis.de>, Alastair Campbell <acampbell@nomensa.com>
CC: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <2c7084883d96446c82e43178ccd145dd@SU8000007192.ad.ing.net>

If the RESOLUTION is the RESOLUTION as discussed yesterday I think what we need is a very clear view on what is covered right now, and what scenarios are not covered. (even for us we're not smoothly aligned easily)

Otherwise this would never be understood by the majority of people and we still leave out interactive components /  user needs (while this is the main reason we make the SC).

 John Foliot also suggested a table of some sort yesterday and I mentioned I added an Github issue already at https://github.com/w3c/wcag/issues/744 

We may do a try out for this for 2.5.1 and what is not covered suggest a new SC for 2.2

-----Original Message-----
From: Detlev Fischer [mailto:detlev.fischer@testkreis.de] 
Sent: woensdag 29 mei 2019 7:48
To: Alastair Campbell <acampbell@nomensa.com>
Cc: Patrick H. Lauke <redux@splintered.co.uk>; w3c-wai-gl@w3.org
Subject: Re: AGWG Meeting Minutes for Tuesday, May 28, 2019

I think we had assumed this was covered by the requirement for single point activation for both drag and swipe as this split had not yet appeared then. (But even then there are gaps as in the slider example with active groove - which focusable as a whole would not help to set a value with pointer/AT). 
In my view, it would be much better to cover this in 2.5.1 rather than creating an extra 2.2 SC for single point activation, but the gap and need is clearly there.
If the exclusion of dragging is decided (not quite sure whether it already is, as of yesterday's telco), we need to clarify how we define ‚directional‘ and what we do with situations where stuff can be BOTH swiped into view and dragged without requiring directionality, as in many content sliders (often only in mobile UAs). And with stuff like slide-to -reveal controls (remember the Oracle implementation) where the gesture is complex (different things happen depending on how far you drag) but essentially there is no required directionality (you can pick up, go also up and down, only one coord is evaluated).

If the decision stands to exclude swipe

> Am 29.05.2019 um 00:11 schrieb Alastair Campbell <acampbell@nomensa.com>:
>> this is one of the scenarios I clearly remember discussing in the Mobile A11y TF because it meant that touch+AT users would be unable to operate this carousel 
> I had a recollection of that scenario as well, but there was no mention of that in the understanding doc. Does anyone know when/why that didn't make it?
> -Alastair

The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.
Received on Wednesday, 29 May 2019 07:00:08 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:30 UTC