Swiper Keyboard Navigation Focus Management When Touch is Disabled

Accessibility Trade-off: Keyboard Focus Indicators vs. Touch-Disabled State

Swiper's keyboard navigation implementation allows arrow key control independent of touch event handling, but the accessibility implications of this separation are unclear. When touch events are disabled through configuration, keyboard listeners remain active and functional, yet the visual focus management during slide transitions lacks standardized behavior across implementations.

The core constraint involves ensuring screen reader compatibility while maintaining keyboard operability in touch-disabled scenarios. Swiper's a11y module provides basic ARIA attributes but does not automatically manage focus ring visibility or announce slide changes to assistive technologies without additional configuration.

This creates a decision point for developers: whether to implement custom focus management overlays or rely on Swiper's built-in keyboard handling when touch is disabled. The uncertainty centers on whether the current implementation adequately supports WCAG 2.1 compliance for keyboard-only users in mobile contexts.

• Does Swiper's keyboard navigation properly maintain focus visibility when touch events are disabled?
• Should developers implement custom focus indicators or can the default behavior be trusted for accessibility compliance?
• How should slide change announcements be configured to work seamlessly with keyboard navigation in touch-disabled mode?