Archive index

A11y Slackers Gitter Channel Archive 7th of July 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jul 07 08:55
    [michiel] tessenate: we have an example in the APG: http://w3c.github.io/aria-practices/examples/checkbox/checkbox-2/checkbox-2.html
  2. [michiel] Who would nested fieldsets be wrong? It’s not like the HTML spec prohibits it.
  3. [michiel] s/Who/Why/
  4. zakim-robot
    @zakim-robot
    Jul 07 09:06
  5. zakim-robot
    @zakim-robot
    Jul 07 15:18

    [m_j_robbins] Does anyone have nay good articles or general advice on when to use role="group" or role="region" ?

    I read this on w3.org

    If a section is significant enough to warrant inclusion in the web page’s table of contents, the author SHOULD assign the section a role of region or a standard landmark role.

    But what would you say is significant enough?

  6. zakim-robot
    @zakim-robot
    Jul 07 15:45
    [michiel] From HTML: Examples of sections would be chapters, the various tabbed pages in a tabbed dialog box, or the numbered sections of a thesis. A Web site's home page could be split into sections for an introduction, news items, and contact information.
  7. [michiel] The APG also has some information about landmarks that you might find interesting: https://www.w3.org/TR/wai-aria-practices-1.1/#aria_landmark
  8. [tink] @m_j_robbins the group role is not intended to be included in the ToC
  9. zakim-robot
    @zakim-robot
    Jul 07 15:50
    [tink] The group role is a document role, not a landmark role.
  10. [tink] The region role is basically equivalent to the <section> element. It's a neutral container for a chunk of ocntent on the page.
  11. [tink] The section element and/or element with role="section" will be included in the ToC (like header, footer, main, etc.). If you give the element an accessible name, then it also becomes a navigable landmark.
  12. [m_j_robbins] Amazing thanks a lot @tink and @michiel
  13. [tink] NP :)
  14. zakim-robot
    @zakim-robot
    Jul 07 15:57
    [michiel] Sure thing thumbsup emoji:skin-tone-2:
  15. zakim-robot
    @zakim-robot
    Jul 07 18:03
    [stevenlambert] if im creating a modal and using the inert polyfill to disable the rest of the page, and the modal has a title and a close button at the top, some content int the middle, and buttons on the bottom to close or perform an action, would it be reasonable to use <header>, <main>, and <footer> elements to denote those sections? at first glance it would seem useful for screen readers to be able to jump to a particular section within the modal using those landmark roles
  16. zakim-robot
    @zakim-robot
    Jul 07 18:19
    [robdodson] hey folks! just rolled out a new a11ycast on labeling stuff in the shadow dom https://twitter.com/rob_dodson/status/883389684281364480
  17. [jasonneel] hi all, my team at work is interested in joining this Slack team. How should they go about this?
  18. zakim-robot
    @zakim-robot
    Jul 07 18:25
    [ghanek] @jasonneel "Invite your friends at: http://web-a11y.herokuapp.com/ "
  19. [jasonneel] Awesome! Thanks
  20. zakim-robot
    @zakim-robot
    Jul 07 19:06
    [marcysutton] Happy friday, a11y friends (coffee emoji)
  21. zakim-robot
    @zakim-robot
    Jul 07 19:12
    [marcysutton] @stevenlambert although you should typically only put one <main> on a page, using inert behind a modal would relax that requirement IMO because the other <main> would be hidden from AT's. It reminds me of heading structure best practices, i.e. "only one h1 per page", which are also relaxed inside a modal to allow another h1 if the background content is hidden from assistive technologies. I heard about that best practice from folks at Deque, who generally know what they're doing. :)
  22. zakim-robot
    @zakim-robot
    Jul 07 19:46
    [stevenlambert] @marcysutton thanks
  23. zakim-robot
    @zakim-robot
    Jul 07 20:22
    [ryan] @marcysutton How do you pronounce Deque? "DQ"? "deek"?
  24. [marcysutton] DQ!
  25. zakim-robot
    @zakim-robot
    Jul 07 20:36
    [jiatyan] Any Mac users here? I've struggling to do a screen reading demo of VoiceOver. Can't get the VO's audio as the input.
  26. zakim-robot
    @zakim-robot
    Jul 07 20:41
    [marcysutton] Yes. I use Screenflow and set it to record computer audio as well as my microphone
  27. zakim-robot
    @zakim-robot
    Jul 07 21:30
    [jiatyan] thanks, @marcysutton I'll go try.
  28. zakim-robot
    @zakim-robot
    Jul 07 21:46
    [seankeegan] @jiatyan One trick I use with the Zoom application is to start a meeting, start the screen-share and enable the audio pass through, and then turn on recording. Video saves as MP4. It’s not the most elegant option, but works fine when trying to demo something for devs.
  29. [jiatyan] @seankeegan does the VO audio come through?
  30. [jiatyan] and the VO subtitles?
  31. [seankeegan] Yes, but have to check Share Computer Sound checkbox.
  32. [jiatyan] (I know, I could try it myself, but you're faster :) )
  33. zakim-robot
    @zakim-robot
    Jul 07 22:21
    [ugi] Hi all, I’m researching text selection/highlighting in web browsers with the keyboard (also switch access and screen readers). Are there any resources that you can point me to? How do keyboard-only users usually select text on a web page, in the absence of a caret?
  34. zakim-robot
    @zakim-robot
    Jul 07 23:17
    [car] Good question @ugi. I don't have a complete answer, but just trying things quickly, it looks like Ctrl+A (Cmd A) does select everything (in all the browsers I tried). Shift+Arrow selection keys work in FF. In Chrome/Safari, Shift+Arrows only work if you begin the selection with the mouse, which, of course, is not helpful. In IE, Shift+Arrows work after turning on caret browsing with F7, as you mentioned. I didn't try Edge.
    Regarding screen readers, they probably all have a text selection feature. In JAWS, for example, you can mark the start of the selection with Ctrl+WindowsKey+K and then move to the end of the selection and type Ins+Space+M to select.