Accessible360 / accessible-slick

the last (accessible) carousel you'll ever need.
https://accessible360.github.io/accessible-slick
MIT License
259 stars 47 forks source link

Deprecate focusOnChange and focusOnSelect settings #11

Closed jasonwebb closed 4 years ago

jasonwebb commented 4 years ago

Per WCAG 3.2.2, keyboard focus should not be moved automatically when a user interacts with a UI component (like a prev/next button or slide dot button) unless they have been informed of this behavior ahead of time.

To fulfill the criteria we could add some warning text to tell users about this behavior ahead of time, but this text would need to be visible to be effective for sighted / low-vision keyboard-only and screen reader users. This would annoy a lot of designers, and could be considered a breaking change that would make this package undesirable for real teams, so that doesn't seem like the way to go.

From a usability perspective, real users would not expect their focus to be forcefully moved onto non-actionable elements anyway, so the best solution here is really to eliminate this behavior altogether.

It is critical that these settings are not deprecated in a way that breaks existing configurations. Be sure to thoroughly test that configs that pass these settings in via the init method or data attributes do not cause any errors. Instead they should just be silently ignored.

losmurfs commented 1 year ago

So, as a blind user, after I activate "Next" how do I then have my screen reader read the alt attribute of the img that is now being displayed. Before interacting with "Previous", "Next" or "Pause" I can up arrow and down arrow to get to an img but after interacting with "Next" a/img become invisible to the screen reader and the keyboard navigation. Is there a special "read slide" command? and a special "follow slide navigation" command?