Archive index

A11y Slackers Gitter Channel Archive 3rd of October 2016

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Oct 03 08:26
    [miwayha] I’m having a bit of a voiceover problem: I’ve added tabindex=-1 to a <nav> element, and I’m using scripting to manually set the focus to that element. However, it seems like voiceover is setting focus to the end of the <nav>. I would expect VO+right arrow to proceed to the first focusable item within the nav, but instead it proceeds to the first focusable item after the nav. VO+left does move to the last focusable item within the nav.
  2. [miwayha] Has anyone else had this problem? Know of any fixes?
  3. Fiona Holder
    @FionaHolder
    Oct 03 08:35
    Maybe just set focus to the first element in the <nav> rather than the element itself?
  4. Srinivas Yedhuri
    @sri429
    Oct 03 10:38
    Did anyone face this issue, screenreader reading the entire value in the href? there is a title for the anchor tag. But Narrator still reads the entire href. How do we fix this?
  5. Thierry Koblentz
    @thierryk
    Oct 03 10:39
    @sri429 there is no content inside the link?
  6. Srinivas Yedhuri
    @sri429
    Oct 03 10:40
    there is content
  7. Thierry Koblentz
    @thierryk
    Oct 03 10:40
    what's the markup?
  8. Srinivas Yedhuri
    @sri429
    Oct 03 10:41
    <a title="foo is great" href="http://www.foo.com">Foo </a>
  9. <a href="http://www.foo.com">foo one </a>
  10. <a href="#dfgfdg">foo two </a>
  11. Thierry Koblentz
    @thierryk
    Oct 03 10:41
    no weird styling for this?
  12. Srinivas Yedhuri
    @sri429
    Oct 03 10:42
    nope its an isolated sample with just that in the html body
  13. narrator reads <content> title <title> value is <href value>
  14. Thierry Koblentz
    @thierryk
    Oct 03 10:44
    sorry, no clue then. markup's fine
  15. Srinivas Yedhuri
    @sri429
    Oct 03 10:45
    so general standard is to give anchor tag title for making screen readers not reading the href value right?
  16. Thierry Koblentz
    @thierryk
    Oct 03 10:46
    @sri429 are you running IE11?
  17. Srinivas Yedhuri
    @sri429
    Oct 03 10:46
    on FF
  18. Thierry Koblentz
    @thierryk
    Oct 03 10:46
    ok, because this discusses the incorrect reading of links https://support.microsoft.com/en-us/kb/2925446
  19. but it says it applies to Internet Explorer 11 - no mention of FF
  20. as far as I know, as long as there is content in the link (unless image with no alternative text) SR should not read href value. No need for title (which is often redundant and no accessible to sighted keyboard users)
  21. Srinivas Yedhuri
    @sri429
    Oct 03 10:53
    thanks @thierryk for clarifying. looks like some issue with narrator.
  22. I think title is used for giving extra information when the entire information cannot be given in the actual content.
  23. Thierry Koblentz
    @thierryk
    Oct 03 11:05
    For what it is worth, I don't think title should be used that way. I may be wrong but I think it is not a sure thing because it depends on SR user settings. Not accessible at all to sighted keyboard users. Vaguely accessible to pointing device users (the more curious ones). And I don't think the size of the text in those "tooltips" change according to user style sheet (custom font-size).
  24. Srinivas Yedhuri
    @sri429
    Oct 03 11:09
    valid point. but then whats the use case of a title
  25. Thierry Koblentz
    @thierryk
    Oct 03 11:10
    This may help: https://www.paciellogroup.com/blog/2012/01/html5-accessibility-chops-title-attribute-use-and-abuse/
  26. zakim-robot
    @zakim-robot
    Oct 03 12:20
    [emplums] @car thank you so much! It's just an 1.5 hour workshop!
  27. zakim-robot
    @zakim-robot
    Oct 03 13:52
    [car] @emplums Wow 1.5 hours. Sorry - I figured it was longer. It's going to be tough fitting everything in that you want to show! Good luck! Let us know how it goes! :)
  28. zakim-robot
    @zakim-robot
    Oct 03 16:28
    [emplums] @car: will do!
  29. zakim-robot
    @zakim-robot
    Oct 03 17:46
    [bkardell] @alice whoops I missed your summoning a few days ago re: @jpdevries' https://web-a11y.slack.com/archives/general/p1475103712002371
  30. [bkardell] did you talk some more?
  31. zakim-robot
    @zakim-robot
    Oct 03 17:52
    [jiatyan] Would someone share a good example of an accessible progress bar/indicator?
  32. zakim-robot
    @zakim-robot
    Oct 03 18:20
    [marcysutton] ooh that Accessibility Preference page is pretty rad
  33. zakim-robot
    @zakim-robot
    Oct 03 18:50

    [miwayha] @jiatyan I don’t always love w3schools, but http://www.w3schools.com/bootstrap/bootstrap_progressbars.asp is pretty great.

    http://oaa-accessibility.org/examplep/progressbar1/ is also good.

    http://foundation.zurb.com/sites/docs/progress-bar.html also seems consistent

  34. zakim-robot
    @zakim-robot
    Oct 03 18:58
    [jiatyan] Thanks, @miwayha. Looks like they are all using ARIA progressbar. Guess that's the way to go.
  35. zakim-robot
    @zakim-robot
    Oct 03 19:23
    [jpdevries] @bkardell haven’t chatted about the a11y preferences yet but I’m always up to! I’ve been enjoying experimenting with localStorage web components like that to enhance accessibility with JS (since I spend enough time ranting about using JS for bad a11y)
  36. zakim-robot
    @zakim-robot
    Oct 03 20:12
    [bkardell] yeah we've basically cooked up something similar which is I think why @alice summoned me
  37. zakim-robot
    @zakim-robot
    Oct 03 20:20
    [michiel] hides from bkardell
  38. [bkardell] I am presuming @michiel is hiding because he didn't review that gist? :)
  39. [michiel] Yeap
  40. [michiel] I’ll get to it.
  41. zakim-robot
    @zakim-robot
    Oct 03 21:06
    [lefthandev] What's the easiest way to make a proposal to the aria spec? @michiel
  42. [michiel] lefthandev: GitHub issues :)
  43. [michiel] https://github.com/w3c/aria/
  44. [lefthandev] Thanks :ok_hand:
  45. [michiel] :+1
  46. [michiel] thumbsup emoji
  47. zakim-robot
    @zakim-robot
    Oct 03 23:14
    [jiatyan] Is there a best practice for accessible multiple menus? I'm looking at a CMS with a top nav, side chapter nav, and page nav. They all make hierarchical sense, but that's a lot of nav for the screed reader, especially when there could be 24 chapters and numerous pages.
  48. [jiatyan] All these navs are just lists in "nav" groups.
  49. [caesar] Just give each region a distinctive name?
  50. luis garcia
    @garcialo
    Oct 03 23:18
    Or if they're one after the other in the DOM, why not just combine them into one region and give them unique headings?
  51. zakim-robot
    @zakim-robot
    Oct 03 23:28
    [jiatyan] Ah, I hear a clue. Sounds like they should be implemented as regions?
  52. [jiatyan] is there a difference between region and landmark?
  53. [karlgroves] Basically, a region isn’t a landmark unless it has a label
  54. [jiatyan] got it. landmark == region + label. thanks, @karlgroves
  55. zakim-robot
    @zakim-robot
    Oct 03 23:33
    [karlgroves] yeah. landmarks are basically regions with a pre-defined label. Of course you can label landmarks, too.

  56. [karlgroves] Possible use case:

    <section role=“region” aria-label=“Search Results”>