Card <div> receiving focus via tabindex="0" — is disabling accessibility best approach
Author: Ganesh-C-hCreated Jun 18, 2025Updated Jun 18, 2025
Context & Problem: We're using Slick Carousel 1.x and noticed that tabindex="0" is automatically applied to the active slide
.
This behavior fails WCAG 2.1 Success Criterion 2.4.3 (Focus Order), because non-interactive container elements like
should not be focusable unless they serve a clear, interactive purpose.
To avoid this, we tried setting accessibility: false in the Slick configuration, which removes the tabindex from the slide div,
Is disabling accessibility the correct and recommended way to prevent tabindex="0" from being set on slide
s?If so, could Slick support an option to disable tabindex without disabling focus-after-change or keyboard arrow navigation entirely?
Requesting guidance We’re looking to make Slick carousel usage WCAG-compliant without degrading keyboard accessibility. Any insight into recommended practices would be appreciated.
Source: kenwheeler/slick