Archive index

A11y Slackers Gitter Channel Archive 15th of March 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Mar 15 09:39
    [kevmarmo] Not sure if others here have seen this but a nice new tool from IBM for automated/browser A11y testing
  2. zakim-robot
    @zakim-robot
    Mar 15 11:41
    [dylanb] yeah, you need to register an IBM ID in order to use it - yuck
  3. stevefaulkner
    @stevefaulkner
    Mar 15 11:43
    @kevmarmo it has some good features for an in browser tool - export results as html/csv/json
  4. zakim-robot
    @zakim-robot
    Mar 15 11:45
    [kevmarmo] @stevef as with all these tools i see it as a good pointer
  5. [kevmarmo] to identify issues
  6. [kevmarmo] but in no way a golden bullet
  7. [kevmarmo] it should be supported by knowledge and (where in budget) user testing
  8. stevefaulkner
    @stevefaulkner
    Mar 15 12:04

    @kevmarmo

    but in no way a golden bullet

    auto tools never are, but the output from IBM tools looks useful and solid

  9. zakim-robot
    @zakim-robot
    Mar 15 12:05
    [kevmarmo] @stevef it's a good starter, good and good for catching regressions on new work
  10. zakim-robot
    @zakim-robot
    Mar 15 14:22
    [brambro] title
  11. zakim-robot
    @zakim-robot
    Mar 15 16:36
    [kevmarmo] can anyone help on this
  12. [kevmarmo] i'm getting an error thrown over this mark up (NVDA/FF)
  13. [kevmarmo] Untitled
  14. zakim-robot
    @zakim-robot
    Mar 15 16:58
    [karlgroves] Kevin: What do you mean by “getting an error thrown”?
  15. [kevmarmo] @karlgroves it's bugging out over tabindex
  16. [juliettepiazza] Hello! I just joined the group :) I am Juliette from Inclusight and I connect user researchers with people with disabilities or/and access needs. I am currently connecting these 2 worlds for face to face testing in London. However, my plan is to develop an online platform that allows participants with disabilities to do remote testing :) I am looking for user researchers happy to share with me their experience in terms of testing with people with disabilities.
  17. [karlgroves] Kevin: “Bugging out” isn’t a clear description.
  18. [kevmarmo] sorry i'll paste the error
  19. [kevmarmo] >>> Widget with role of link must have at least one tabbable element
  20. [karlgroves] Where did that error come from?
    Also, which portion of that template file is it pointing to?
  21. zakim-robot
    @zakim-robot
    Mar 15 17:03
    [kevmarmo] it's pointing to the nested links
  22. [karlgroves] What line in the above paste?
  23. [kevmarmo] bear with
  24. [kevmarmo] it's actually any place where an anchor tag exists
  25. zakim-robot
    @zakim-robot
    Mar 15 17:16
    [karlgroves] What tool is giving you this error?
  26. zakim-robot
    @zakim-robot
    Mar 15 17:25
    [karlgroves] @kevmarmo What tool is giving you that error?
  27. zakim-robot
    @zakim-robot
    Mar 15 18:08
    [kevmarmo] @karlgroves it's the IBM tool above
  28. zakim-robot
    @zakim-robot
    Mar 15 18:25

    [karlgroves] "Widget with role of link must have at least one tabbable element”

    So weird. This message makes no sense at all. I mean, first, you don’t have anything with a “role” of “link”. You have anchors, which it is probably referring to, but to say that links have to have at least one tabbable element makes zero sense unless they’re referring to the links themselves.

    Now, on line 12 of your code, you do have tabindex=”-1” on a link. Is that one of the lines it is complaining about?

    Overall, this does look like sort of a mess.

  29. [karlgroves] For instance, why have tabindex on the <li> and not the link?
  30. zakim-robot
    @zakim-robot
    Mar 15 19:52
    [marcysutton] I saw one link without any text in it in that example above–though that would be a different failure than tabindex.
  31. zakim-robot
    @zakim-robot
    Mar 15 20:24
    [backwardok] seems like the tool is rightly complaining about having links that can’t be accessed via the keyboard because of tabindex=”-1”
  32. zakim-robot
    @zakim-robot
    Mar 15 20:29
    [herin] The tools complains of all the interactive elements
  33. [herin] <input autocomplete="off" class="yui-ac-input" id="title2" value="" size="50" maxlength="200" name="title" type="text">
  34. [herin] Widget with role of textbox must have at least one tabbable element.
  35. [herin] Looks like a tool issue
  36. zakim-robot
    @zakim-robot
    Mar 15 23:19
    [caesar] Hi I've created the #training channel to discuss acquiring and propagating the skills of accessibility practitioners. Just wanted to ask a question, but hopefully there will be more use for it!
  37. James Nurthen
    @jnurthen
    Mar 15 23:37
    @backwardok not all links need to be tabbable. Sometimes we use redundant links and deliberately remove 1 or more from the tab sequence to improve efficiency.
  38. zakim-robot
    @zakim-robot
    Mar 15 23:38
    [backwardok] true, but i’d assume that an intentional link is tab-able
  39. [backwardok] err, not intentional, meaningful/valuable? not sure how to phrase that one :)
  40. [backwardok] but i would say in the given example, that a shouldn’t have had tabindex=-1