Not accessibility friendly

[natashad]

Doesn't work well with screen readers, nor can you really tab between the buttons

[rykener]

better late than never...

in my steps I'm doing:

 when: {
     show: makeAccessible()
}                      

And I have a makeAccessible function that inserts basic aria attrs

// one of the things it does:
$(".shepherd-next").not("attr[aria-role]").attr("aria-label", "go to the next step in the guided tour")
    .attr("title", "go to the next step in the guided tour").attr("href", "#")
    .attr("onclick", "return false;");

and scss styling helps give it focus

.shepherd-step {
  z-index: 10000;
}

.shepherd-target {
  &.shepherd-enabled {
    z-index: 1000;
  }
}

we chose this library specifically because we thought it was the most accessible friendly option

[FranDias]

Hey, really interested in this—

I think the original qualm was being able to tab through the buttons on a Shepard element. I have a question about how someone gets to that situation (asking the question in a very basic way).

I am curious about being taken through what the ideal user experience would be for someone who is using an assistive device. Are they tabbing through elements? Does it take focus? How should we provide context for the element the tour is describing?