Archive index

A11y Slackers Gitter Channel Archive 3rd of August 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Aug 03 10:46
    [sri429] Does jaws use MSAA or UIA on internet explorer 11
  2. zakim-robot
    @zakim-robot
    Aug 03 11:31
    [morgan] Hi there, I have many navigations on a page. What is the best way to differentiate them. aria-label on the nav tag?
  3. zakim-robot
    @zakim-robot
    Aug 03 11:54
    [melsumner] @morgan yes
  4. LauraOU
    @LauraOU
    Aug 03 12:08
    @morgan multiple landmarks of the same type need to have distinct labels.
  5. zakim-robot
    @zakim-robot
    Aug 03 12:29
    [morgan] Thank you both. Can navigations be nested?
  6. zakim-robot
    @zakim-robot
    Aug 03 13:49
    [johnbhartley] technically because <nav> allows flow content the answer is yes. From the perspective of using landmarks I'd say no. I'm assuming you mean nested as in nav inside a nav and not two navs in a header element or something along those lines
  7. LauraOU
    @LauraOU
    Aug 03 13:56
    From my experience, with screen reader landmark navigation; if its a landmark, its reported as the type and label.
  8. nesting level isn't something that's reported.
  9. zakim-robot
    @zakim-robot
    Aug 03 14:20
    [goncaloreis] Guys! Its correct to have <div> into <li> element in html? How the screen readers react about this point?
  10. [tink] @goncaloreis that is not a new thing. Screen readers don't have any problem with it that I know of.
  11. zakim-robot
    @zakim-robot
    Aug 03 14:26
    [goncaloreis] Thank you @tink
  12. [tink] NP :)
  13. zakim-robot
    @zakim-robot
    Aug 03 16:27
    [spencer_stark] Hey All, I’ve got a question about link texts and making them descriptive, is this the best place to ask it or a different channel?
  14. [gokatgo] Ugh. Those unwelcome ad page loads are now explained.
  15. zakim-robot
    @zakim-robot
    Aug 03 16:34
    [marcysutton] @goncaloreis do you mean a <div> inside of an <li>? that should be fine as long as <li> is inside of <ul> – the semantics (or lack thereof) for the DIV won't interfere with the list
  16. [goncaloreis] Thank you so much @marcysutton
  17. [goncaloreis] Yes its not good to have <div> inside in <ul<
  18. zakim-robot
    @zakim-robot
    Aug 03 16:42

    [spencer_stark] I’ve got a number of links that read as, <a href="/location/">Learn More</a> and by a number, I mean they’re all over our site. Is it acceptable to do something like the following or should we change our content itself to be more helpful in general.

    <a href="/location/">Learn More<span class="u-hiddenVisually">about the thing we link to</span></a>

    where hiddenVisually is screen reader only style.

  19. zakim-robot
    @zakim-robot
    Aug 03 16:55
    [conley] The hidden text suffices for low-vision users but in terms of cognitive impairments, a bit more visual context is helpful
  20. [spencer_stark] the link almost always accompanies a paragraph giving context to the learn more link.
  21. zakim-robot
    @zakim-robot
    Aug 03 17:16
    [jasonday] For those, I almost always add an aria-label or title (and yes I know that title is seen as a problem, but title gives more context to sighted users as well, and support for title & tabbing is good: https://www.powermapper.com/tests/screen-readers/labelling/a-title/))
  22. zakim-robot
    @zakim-robot
    Aug 03 17:47
    [marcysutton] Keep in mind that hidden labels won't be visible to someone using voice dictation software.
  23. [jasonday] @marcysutton and there's the gotcha. Good point.
  24. [marcysutton] The easiest thing would be to just use more descriptive text for the link. But I understand that can sometimes be an uphill battle, and having descriptive links for screen reader users is better than "learn more" "learn more" "learn more"
  25. zakim-robot
    @zakim-robot
    Aug 03 18:31
    [drtomlins] I still have to push back constantly against 'click here'.. which is so awful on so many levels
  26. [marcysutton] UGH!
  27. zakim-robot
    @zakim-robot
    Aug 03 18:37
    [spencer_stark] @marcysutton I’m not sure I exactly understand what you mean by won’t be visible to someone using voice dictation. Do you mean someone who is able but using a screen reader and they getting some extra content that they don’t see?
  28. [marcysutton] This is a super high-level statement, but there may be a mismatch between how the page looks vs. how you interact with it. If you want to activate a link that says "click here", how would the technology know which one you meant?
  29. [marcysutton] http://webaim.org/discussion/mail_thread?thread=7313
  30. [spencer_stark] I understand now, very valid point
  31. [jasonday] @spencer_stark - voice dictaction such as Dragon Naturally Speaking, etc. allows a user to voice commands such as click on a specific link
  32. [jasonday] when there are many links that have the same text, it becomes harder to navigate the site
  33. [spencer_stark] I gotcha, dictation, not screen readers. I wasn’t thinking about that
  34. [marcysutton] Yes, voice dictation.
  35. zakim-robot
    @zakim-robot
    Aug 03 18:42
    [spencer_stark] Thanks @conley, @jasonday, @marcysutton , your help has been very insightful!!
  36. [conley] thumbsup emoji
  37. zakim-robot
    @zakim-robot
    Aug 03 19:45
    [pweil] People on my team are asking me what to do about abbreviations. I used to be sort of a purist about using the <abbr> tag with title attribute expansions + css speak properites, but eventually gave up for a variety of reasons, including the sense that it neither helped nor mattered much, as well as poor support from screenreaders. What is the current state of thinking or consensus(?) best practice for dealing abbreviations, such as Madison, WI, USA, etc.? How much of a problem do abbreviations pose for AT users?