In looking at the front page slider, I noticed that you can't actually select one of the slides "1,2,3" without a mouse.

I haven't looked into this in any depth, but the links needed to be actual links. <a class="">2</a> isn't good enough unless you are specifically building your JS to work for keyboard-only functionality.

You need the href="#" for most browsers to allow you to access it.

CommentFileSizeAuthor
#3 slide.patch302 bytesmheinke
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mheinke’s picture

mheinke CreditAttribution: mheinke commented
Assigned: Unassigned » mheinke
mheinke’s picture

mheinke CreditAttribution: mheinke commented

hmmm, thats an interesting one.
it seems that in the Out of Box flexslider the code looks like this:

<ul class="flex-direction-nav">
   <li><a class="prev" href="#"><li>

so i will have to do some digging as to where we are modifying that and fix it.

thanks for the issue reporting! if you see any more accessability issues please feel free to post them, id it if i could say this theme is the most accessible drupal theme!

mheinke’s picture

mheinke CreditAttribution: mheinke commented
FileSize
slide.patch302 bytes

this patch allows you to use the arrow keys to move the slider back and fourth.

in js/slide.js:

jQuery(document).ready(function($) {
  $('#slider').flexslider({
    directionNav: false,
    keyboardNav: false,
  });
});

needs to be:

jQuery(document).ready(function($) {
  $('#slider').flexslider({
    directionNav: false,
    keyboardNav: true,
  });
});
mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford commented

Being able to use the arrow keys is good, but discoverability is often a problem with these types of things.

How does one know that they can use the arrow keys to do this? Normally keyboard only users simply tab through the interface jumping between links.

mheinke’s picture

mheinke CreditAttribution: mheinke commented

thats an interesting question...i know some people put hidden text near the controls? i dont know using tabindex wont really work unless i go through an assign every area a number...

mheinke’s picture

mheinke CreditAttribution: mheinke commented

I cant seem to get an answer on how to make it so screen readers can tell users to use the arrow keys. until I can find something im going to close this as "fixed - ready to be ported"

mheinke’s picture

mheinke CreditAttribution: mheinke commented
Status: Active » Patch (to be ported)
mheinke’s picture

mheinke CreditAttribution: mheinke commented

the first patch is in the mainline code...im not sure what else to do about it. so im closing this issue.

mheinke’s picture

mheinke CreditAttribution: mheinke commented
Status: Patch (to be ported) » Closed (fixed)