Archive index

A11y Slackers Gitter Channel Archive 9th of January 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jan 09 14:13
    [car] If I had a spare bucket of time (or a clone! ;) ) then I would love to help, but alas, I am swamped. Hopefully someone will take up your challenge - it sounds like fun, and it would save you time moving forward. :)
  2. [karlgroves] Especially given the recent, massive uptick. :(
  3. zakim-robot
    @zakim-robot
    Jan 09 15:27
    [spell] Happy New Year, Slackers! Quick question regarding links. I have a page with several of them that say, "Learn More". In the past, I have seen various automation tools flag them for contextual issues. Same text, different links, which makes a ton on sense. Just looking for best advice/practices on how to make such things more friendly to all, especially assistive tech. Do I need to change the text in the link to make them more contextual or will screen reader user be able to understand the difference if, say, the immediate surrounding text is different and provides good context? Thanks in advance!
  4. zakim-robot
    @zakim-robot
    Jan 09 15:38

    [karlgroves] WCAG references links in context and links out of context.
    Links in context is AA
    Links out of context is AAA.

    That being said, I think it is easy enough - and wise for SEO purposes - to have links make sense out of context. So, ideally, the link text (or, more accurately, the accessible name of the link) would be unique per destination.

    However, if that’s not feasible, some good ways to add context is to provide wise groupings. Something like

    ```<h2>Foo header</h2>

    <p>Foo Stuff and things <a href=”…”>Learn more</a></p>

    <h2>Bar header</h2>

    <p>Foo Stuff and things <a href=”…”>Learn more</a></p>

     Other things provide context, too, depending on the nature of the content.  Something else I’ve done is use aria-described by to add additional info  ```<h2 id=”foo”>Foo heading</h2> <p>Foo Stuff and things <a href=”…” aria-describedby=”foo”>Learn More</a></p>
    
  5. zakim-robot
    @zakim-robot
    Jan 09 16:20
    [stefanjudis] I recently came across an example like that
  6. [stefanjudis] ```

    <h2>Foo header</h2>

    <p>Foo Stuff and things <a href="…">Learn more <span class="visuallyHidden">about Foo heading</span></a></p>
    ```

  7. [stefanjudis] which sticks to design and should work fine with screenreaders.
  8. [stefanjudis] opinions on that?
  9. Job van Achterberg
    @jkva
    Jan 09 16:24
    I like seeing the full context, also makes it easier to work with tools like Dragon
  10. zakim-robot
    @zakim-robot
    Jan 09 17:09
    [melsumner] @stefanjudis: maybe I'm missing something, but couldn't you put the span with the visually hidden text into an aria-label instead?
  11. zakim-robot
    @zakim-robot
    Jan 09 17:15
    [spell] @karlgroves Nice touch using ARIA to associate things. Thank you.
  12. [karlgroves] @stefanjudis yeah, that visually hidden approach was the go-to before ARIA.

    I agree with @jkva in that the full context being visible is the most universally usable part.

    @melsumner that would only work on the link itself:

    `\<a href=”…” aria-label=”The actual stuff" >Read more</a>

    The problem is, voice dictation users will expect that the link’s label is “Read More"

  13. [melsumner] If that's the constraint then I'd probably make all of it visible.
  14. [melsumner] that's a bit frustrating though, I often put more detailed context into aria-label.
  15. [karlgroves] aria-label is meant to win over everything else.
  16. zakim-robot
    @zakim-robot
    Jan 09 17:27
    [spell] Yeah, that is way I lean, too @jkva. I tell colleagues, often, that if we need to do one thing for accessibility, that perhaps it is not a bad idea to do for all. However, on occasion, it is not always possible, so it's nice to have some options here. Thanks, folks!
  17. [spell] @karlgroves On occasion I work with companies a11y testers and they are rather insistent that some text is visually hidden. I'll have to educate them on the benefits of ARIA. :)
  18. zakim-robot
    @zakim-robot
    Jan 09 17:32
    [quidkid] Can you make an interactive map website accessible? I’m looking through website inspiration sites and while all these sites are so beautiful, i have no idea how to make them accessible
  19. [quidkid] theoretically speaking
  20. [quidkid] none of them are tab friendly
  21. [karlgroves] @quidkid here’s an awesome example from Simply Accessible http://examples.simplyaccessible.com/svg-maps/
  22. [quidkid] wow that’s pretty awesome but what if a designer comes up with a custom design of the map?
  23. [quidkid] like how would i make something like this accessible: http://www.therefugeeproject.org/#/2015
  24. zakim-robot
    @zakim-robot
    Jan 09 17:40
    [quidkid] probs a lot of aria-live regions? XD
  25. zakim-robot
    @zakim-robot
    Jan 09 17:46
    [klara] Based on something I've seen a colleague build, I would also guess that you could have an expandable sidebar that could be optionally opened by the year controls at the bottom that listed out all the data points on the map by metadata (eg. world refugees info currently seen on the left), would perhaps give form options for sort order or search, and allowed you to navigate through the sidebar list by keyboard. It wouldn't solve the data aggregation that you can visually infer from the map though.
  26. [stefanjudis] @karlgroves thanks. makes sense
  27. [stefanjudis] :)
  28. [melsumner] The svg map is neat but NVDA is reading out the abbreviation instead of the title. Any ideas why?
  29. zakim-robot
    @zakim-robot
    Jan 09 19:46
    [karlgroves] @melsumner I’d have to look but it is probably reading the abbreviation because that’s the only thing in the text node of each SVG element.
  30. [melsumner] Yes, I think it is, after peeking at the code.
  31. [karlgroves] Everyone:

    https://www.access-board.gov/attachments/article/1877/ict-rule.pdf

    That’s the text of the Final Rule of the Section 508 Refresh. If you do any work for the US Federal Government you should read it. There are very important and numerous changes in there from the old 508. Read the narrative stuff to read what’s been changed and why.

  32. zakim-robot
    @zakim-robot
    Jan 09 20:55
    [jiatyan] I was given a tip to start reading from Chapter 7, skipping all the preambles.
  33. zakim-robot
    @zakim-robot
    Jan 09 21:05
    [johnkmcnabb] @jiatyan Which page is that?
  34. [jiatyan] 65
  35. [jiatyan] I think. My first time with this doc. OMG.
  36. zakim-robot
    @zakim-robot
    Jan 09 21:13
    [johnkmcnabb] Thanks!