Successful avoidance of dependency on dragging

Just thought I'd share that I've been working with designers incorporating 
some of the WCAG 2.2 candidates. Wrote a short article on how we overcame 
dragging reliance in a data viz tool. This is just one of many successes 
we're having taking WCAG 2.2 SCs into consideration.
https://medium.com/carbondesign/not-dragging-our-feet-a03ea57150e


PS Medium has no apparent way of pausing animations. There is a small 
animation loop in the middle of the page which I believe will not disrupt 
any technologies or be negatively distracting to users. We decided the 
animation's benefit outweighed what we regarded as its potential negative 
impact, given the small size relative to the overall page content.  I'd 
welcome comments from anyone who runs into issues with it so I can better 
understand unanticipated fallout from what I perceive as a trivial failure 
of Pause, Hide, Stop. 

Michael Gower
Senior Consultant in Accessibility
IBM Design


1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
cellular: (250) 661-0098 *  fax: (250) 220-8034



From:   "Patrick H. Lauke" <redux@splintered.co.uk>
To:     w3c-wai-ig@w3.org
Date:   2021/10/18 10:33 AM
Subject:        [EXTERNAL] Re: Question for form fields on mobile: to 
break out or not?



On 18/10/2021 17:59, Jerri Zhang wrote:
> Hello,
> 
> I've been trying to figure out whether or not it's against 
> recommendations to break forms fields on mobile into separate screens. I 

> think if my readings have been correct, forms ought to stay together on 
> the same screen on desktop UI because a keyboard is often used for 
> navigating through them for completion.
> 
> However, it's unclear whether that is applicable on mobile. Does the 
> same behavior occur? Are there issues with having form fields broken out 

> into multiple screens in a registration flow (ie: one input field per 
> screen) even if there is a progress bar/indicator above? It’s a common 
> pattern I’ve seen in a lot of apps and would like some insight.

I'd move away from thinking about this in terms of "desktop vs mobile" 
(also noting that even on desktop, some users may use a small-ish 
viewport because they're zooming or using screen magnification, and on 
mobile users can/will also use keyboards, so the boundaries are very 
fluid these days). Think about it in terms of "how annoying is it for a 
user to only see one or two form fields at a time, how many sub-steps am 
I forcing the user to take". It's more a usability question, rather than 
an accessibility question.

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