Replies: 1 comment 4 replies
-
Mmm, I don't think so. We should place similar controls close. When the keyboard user wants to move focus to the previous arrow from the next one, he/she needs to push |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello! First of all, thanks for this awesome component!
I'm using Splide mainly by the attention given to accessibility on the library and I was wondering if there's a particular reason for the arrow components to be places before the track component.
An approach that I believe could be more intuitive would be to have the previous arrow before the slider track and the next arrow after it. This way the first thing an user that is navigating using assistive technology would focus is the first slide in the list and communicate how many items are in the slider instead of just hearing "Next slide, Button" without having passed trough said slider before.
Did that make sense?
Beta Was this translation helpful? Give feedback.
All reactions