- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Mon, 22 Dec 2025 10:05:08 -0500
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: w3c-wai-ig@w3.org
- Message-ID: <CAJi9Cqqx=xMZbFS3xs-xNeU5ELh8sHudptdR7GFXrLh0BKKkMw@mail.gmail.com>
In a sense, as stated in Understanding SC 2.2.1, there is a dependency with SC 2.2.2 Pause, Stop, Hide in the matter of carousels for instance. So if those controls do not work as expected, they fail SC 2.2.2 and result in a failure of SC 2.2.1 too. Thanks, Sailesh Panchang Principal Accessibility Consultant Email: sailesh.panchang@deque.com Deque Systems Inc | - Accessibility for Good | www.deque.com On Fri, Dec 19, 2025 at 9:10 AM Patrick H. Lauke <redux@splintered.co.uk> wrote: > > > On 19/12/2025 11:18, Ms J wrote: > > 2.2.1 explicitly says it excludes carousels, this feels wrong? > > It excludes them if the user has the ability/control to navigate the > carousel. > > "so long as the information and data is adjustable or otherwise under > the control of the end user." (from > https://www.w3.org/WAI/WCAG22/Understanding/timing-adjustable.html) > > If it still auto-advances when the user explicitly moved the carousel > slide to the one they wanted though (i.e. it doesn't stop auto-advancing > when the user is actively interacting with it), then 2.2.1 does apply in > my view. > > P > -- > Patrick H. Lauke > > * https://www.splintered.co.uk/ > * https://github.com/patrickhlauke > * https://flickr.com/photos/redux/ > * https://mastodon.social/@patrick_h_lauke > > >
Received on Monday, 22 December 2025 15:05:24 UTC