Improve features carousel accessibility

[sameersharmadev]

Fixes #1094

• Added contrasting backgrounds to carousel arrows for better visibility
• Improved credits text contrast
• Added autoplay to showcase carousel with pause/resume button
• Includes pagination dot indicators for better navigation

Production edit:

Enregistrement.d.ecran.le.2025-07-07.a.11.13.42.mov

[JohnVeness]

Thanks for doing this. It sounds good from the description. Can you supply any screenshots/video, or a demo site, of the changes?

Also, it might be better to not change formatting in files (e.g. adding new lines) in the same PR, to make your functional code changes easier to spot.

[sameersharmadev]

@JohnVeness I tried deploying it for a demo site but I couldn't make it work, so here's a video. Let me know if you need anything else

features_accessiblity_fix.mp4

Also noted on the formatting, I’ll keep that in mind for future!

[JohnVeness]

Looks excellent :). The only thing I would like would be a rollover highlight effect for the arrows/circles, like you have already for the play/pause button.

[sameersharmadev]

Thanks! I added the hover highlight effect on the arrows, matching the style of the play/pause button.

(left one is normal state, right one is hovered state, pause button is on hovered state too)
If you have any more feedback, just lmk

[JohnVeness]

Thanks, looks good to me. I'm not in charge here, though, so I'll let someone else review.

[sameersharmadev]

Also, while working on this, I noticed that the carousel allows users to flip through the showcase images without waiting for the sliding animation to end. This causes some visual glitches when clicking rapidly.

This behavior already exists on the live site, and you can reproduce it by clicking the carousel arrows quickly. Since this wasn’t part of the original issue, I left it out for now, but I wanted to check: would you prefer I open a new issue for this, or fix it in this pr?

[JohnVeness]

Ah yes, I see the glitches you mention on the live site. I think it would be great to fix that in this PR - I don't think we insist on an issue for each PR, in this repo anyway.

[sameersharmadev]

@JohnVeness fixed :D

[adamscott]

Here's my comments at first glance. I assess the nature of the PR by itself, it's more something @coppolaemilio can do.

[sameersharmadev]

I committed all the suggestions, thanks!