Question: Accessibility

[freddi301]

Hi, this component is exactly what I need. But is it accessible?

[richardscarrott]

Hi @freddi301 -- react-snap-carousel has a few advantages re: accessibility.

1. It's headless so you can markup the content however you see fit.
2. It uses native scrolling which most (all?) assistive technology should be comfortable navigating.

Personally I've only ever tested using VoiceOver for macOS which is more than capable of navigating the content in the carousel.

I've found it's best to simply hide the controls from screen readers as they aren't essential to navigation -- a user can just scroll using whatever input they prefer (mouse, trackpad, touch, screen reader etc.) -- in fact, without additional markup they just confuse screen readers in my experience.

e.g.

<div aria-hidden>
  <PrevButton />
  <Pagination />
  <NextButton />
</div>

[freddi301]

would you add an accessibility tips section to the readme? just copy pasting your answer is enough IMHO.
I agree contents are already accessible. from a brief analysis making controls accessible has not really a meaning: scroll controls are not useful for a screen reader, and this use case does not map to traditional pagination.
The only other thing that bothers me if the user uses tab to navigate the pagination controls, when he goes back to the content, it would scroll him to the beginning.
Feel free to close the issue if you don't think these are worth addressing.
Great work, best regards