El año pasado, Jared Smith de WebAIM realizó una graciosa crítica de los carruseles con el sitio web Should I use a carousel?
En la entrevista que le hicieron, Accessibility expert warns: stop using carousels, explicaba los problemas que tienen los carruseles o slides:
Beyond usability frustrations caused by carousels for all users, there are several distinct issues for users with disabilities. For auto-playing carousels, having content automatically disappear can cause loss of focus for screen reader and keyboard users that are reading or have keyboard focus on that content when it animates away. This can force the user back to the top of the page.He encontrado dos sitios web que hacen un buen uso del carrusel. No es una coincidencia... El primero es el sitio web de TAW, la famosa herramienta de evaluación automática de la accesibilidad:
There also is no easy way to semantically or programmatically associate the controls for a carousel—often just numbers or dots—with the carousel content. This is especially difficult for users that cannot see the interface. The cognitive load and distraction caused by carousels can be especially difficult for some users with cognitive and learning disabilities.
If, after all this, you decide to implement a carousel, we recommend not having it automatically advance. Give control of the content presentation to the user. If it does auto-advance, provide a pause link or button, and ensure that the carousel pauses if the user hovers their mouse over or sets keyboard focus to the carousel or its controls.
El segundo sitio es de la Fundación CTIC, los creadores de TAW:
En los dos casos, la página posee un carrusel, pero el carrusel dispone de un botón para pararlo y se puede acceder directamente a cualquiera de los contenidos que se muestran en el carrusel.
