Enhance display when JavaScript is unavailable

hmm good question about thumbnailhover. In singleframe it degrades right where it just shows the first image. Probably should hide the thumbnails and enable them in javascript.

I have a similar issue where a views_slideshow pager is enabled using an image field. Slideshow works perfectly with javascript and with a bit of CSS I get the active pager icon appear over the top of the existing pager image to indicate the active node.

When I disable javascript, none of the pager links work and the thumbnail images do not link so effectively the slideshow breaks. There are a few ways this could be fixed but at first glance I would have thought the module should degrade gracefully before having to hack up the CSS to fix?

I'd be interested in any feedback on this.

Thanks in advance.

I was also curious about this. In the past, Drupal and its contrib modules have been way ahead of the pack when it came to accessibility and graceful degradation. It seems like as Drupal's popularity has grown, some of that has fallen by the wayside. (Ironic, considering the proliferation of mobile web access.) My clients are constantly clamoring for slick-looking jQuery functionality such as slideshow effects, and not only to do better work for them, but also as a matter or principle, graceful degradation of slideshows in Drupal 7 is important.

The same client has asked me to develop non javascript version of the slideshow :(
My approach is going to be conditional stylesheet in template.php perhaps.

1. On degrade hide slideshow thumbnail navigation images and show hidden block of both thumbnail nav images and their equivalent hover/active images

We might consider sponsoring this development ONLY if it can be done within the next couple of days to meet our own deadlines.

I have some time funded by Myplanet Digital that I can use on May 4 to take a look at rolling a patch to progressively enhance this project.

If anyone does work before then I'd appreciate seeing it.

@Evertt Zufelt: That sounds awesome, let me know if I can be of any assistance testing etc.

I've installed and looked at the module for the first time. I do see that all content other than the first row is hidden when JS is disabled. What is the desired way to solve this problem?

I can definitely understand that in order to fit into a design, that one desired outcome would be what we have at present, that only the first row be visible.

I can also see that for some implementations a setting may be desirable to indicate that all rows should be visible by default, and then all but the first row hidden on behavior attach.

Been awfully busy sorry for delay in getting back.

Both of your answers are applicable as you say depending on the use.
We have a bottom widget pager set as a content field called thumbnail pager which acts as the navigation menu but is simply a click through to the next slides. We'd like it if when js is not present that you could still click through the content field thumbnail pager but a full page reload is performed to each slide node in effect keeping your slideshow "working" as such at least then we could fix other behaviour with simple conditional css.

Currently the behaviour is: the pager is inactive and the content field pager is inactive so you can't get to the next slide at all.
I have to say the javascript in the views_slideshow module is a little buggy as I get jumpy behaviour transitioning the animated slide even when js is enabled simply by mousing over a couple then moving the mouse out of the slide area. Sometimes it will skip to the next slide very quickly and not consistently, but this is a separate issue.

subscribing ... accessible slideshow important for our clients as well.

This certainly is an area that could use significant improvement. Putting on my todo list although won't get to it for a bit so if anyone wants to take a stab at it, feel free.

Okay, default was improved a *lot* between when this was first opened and now. However it was still displaying controls; which isn't ideal. In many cases, you may want to provide your own styling that will be better for your use case, but this should work better/be improved for most users than otherwise.

EDIT:
sorry, I posted on wrong issue, see follow-up: #2853250: lost pager.