Carousel (accordion) is different from previous versions

[TeD TeD]

Hello everybody,

A big thanks to everyone involved for the 2.9.2 release that solves a lot of issues for us!

Having said that, the Carousel view in the new 2.9.x series is very different from what is displayed in the help files and has less functionality when compared to previous versions.

So for example, see here. There is a visual difference from what is shown in the manual, but more importantly, one can no longer browse the images with the mouse wheel (as before) and has to CLICK the left/right arrow images instead (left/right keyboard buttons don't work either).

Is this an intentional change and if so, Is there a way to revert back to the older display/functionality?

Kind regards,
Theodoros Theodoropoulos

[Dan Gillean]

Hi Theodoros, 

The original ImageFlow library that was previously used in the Bootstrap 2.x theme (here), as you will see, has not been maintained - the last commit to update it was in 2010. Our Maintainers are constantly working hard to try to keep AtoM and its underlying dependencies as up to date as possible, to ensure the application's ongoing security and viability. It is therefore unlikely they will be reverting AtoM to use this unmaintained library, unfortunately. 

Tab navigation will work on carousel user interface elements (i.e. you can tab to either the dot navigation guides or the errors, and press enter to interact with them), making this reader actually better for users employing assistive devices like screen readers in navigating AtoM, even if it is slightly less convenient for conventional users. In fact, we specifically sought out a library that incorporated accessibility into its carousel design, and ultimately ended up using the accessible-slick carousel library. Nevertheless, I am sure that both usability and accessibility improvements could still be made to improve this implementation overall, and I'm sorry that not all previous behavior could easily be preserved. 

I am sure that the Maintainers would welcome pull requests that improve the current implementation, or even an issue ticket being filed to track the loss of usability. 

Cheers, 

Dan Gillean, MAS, MLIS
Business & User Experience Analyst
Artefactual Systems, Inc.
604-527-2056

he / him

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/61de8a2e-e41a-40fc-8e12-1fb0554a2f87n%40googlegroups.com.

[Dan Gillean]

Quick update to say that the Maintainers are in fact keeping an eye on discussions in this forum, and they have already filed an issue about the loss of mouse wheel scrolling in the BS5 carousel following your post - here: 

• https://github.com/artefactual/atom/issues/2076

Dan Gillean, MAS, MLIS
Business & User Experience Analyst
Artefactual Systems, Inc.
604-527-2056

he / him

[TeD TeD]

Thank you Dan for the feedback and to the dev team for the github issue!
Let's hope that it's all a matter handling mouse wheel events (and/or left-right arrow buttons) in JS and feeding them to slick slider previous/next functions.
If so, getting a 2.10 tag is not a far-fetched scenario!

Cheers,
Theodoros