Archive index

A11y Slackers Gitter Channel Archive 22nd of October 2015

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    14:04
    https://twitter.com/rodneyrehm/status/657195637964996608
  2. zakim-robot
    14:14
    … I was pointed to http://www.w3.org/TR/WCAG20/#visual-audio-contrast-contrast
  3. zakim-robot
    17:13
    [Cordelia McGee-Tubb, a11y] Does anyone have a good example of an accessible custom select field? (@marcysutton I remember you posted a link a while back to a prototype of a more accessible Virgin America site that I think had some?)
  4. zakim-robot
    17:15
    [Marcy Sutton, a11y] There wasn’t a select on that one, I don’t think...
  5. zakim-robot
    17:15
    [Marcy Sutton, a11y] It had radio buttons and focus management, but no select http://marcysutton.github.io/angular-a11y/demos/scroll-ui/
  6. zakim-robot
    17:16
    [Marcy Sutton, a11y] The Angular Material select is sadly not where I want it to be, and I haven’t had time to work on it.
  7. powrsurg
    18:35
    What is worse, a label inside an anchor tag or an anchor tag in a label?
  8. zakim-robot
    18:51
    [Marcy Sutton, a11y] they’re both pretty bad...
  9. zakim-robot
    18:51
    [Marcy Sutton, a11y] I’d guess the label inside the anchor is worse though…. Why would you wrap a label with an anchor?
  10. zakim-robot
    18:54
    [Cordelia McGee-Tubb, a11y] Label inside anchor, for sure. :disappointed:
  11. powrsurg
    19:00
    Only had access to change certain markup .... but I instead figured out how to add an aria-label on the textarea. Made it slightly less bad ...
  12. zakim-robot
    19:04
    [Cordelia McGee-Tubb, a11y] I can more easily understand why someone would put an anchor inside a label. For example, if they had an anchor in some field help text and mistakenly used a <label> element for both label and help text, instead of putting the help text in its own element. But I’m struggling to think up a use case for why someone would wrap a label in an anchor.
  13. garcialo
    19:04
    +1 for label inside link being worse
  14. powrsurg
    19:06
    The environment is one where tabs were used to expose different tab bodies. Anchors are used for the tab and I wanted that to be for the text area that is exposed on that tab
  15. powrsurg
    19:07
    So it could have two tabs (notes, files). It'd be weird for the notes tab to then also say Notes as a label for the textarea for taking notes.
  16. powrsurg
    19:08
    And yes, as I was typing this I thought of http://oaa-accessibility.org/example/34/
  17. zakim-robot
    20:23
    [Jiatyan Chen, a11y] My team is coding a photo gallery (modal dialogue with single slide+caption and keyboard controls) and we ran into the question of whether blinds users would even want to play through it. Could we have better serve them by providing a list of descriptions of the slides without them having to open the modal? Opinions?
  18. deborahgu
    20:24
    plenty of vision impaired people want to view images online, and need the help of text with the image.
  19. deborahgu
    20:25
    It's actually fairly common.
  20. zakim-robot
    20:25
    [Jiatyan Chen, a11y] Question arose because we struggled to get screenreader to read the captions in the modal. Appreciate properly implemented example if any :simple_smile:
  21. zakim-robot
    20:26
    [Jiatyan Chen, a11y] ok. got it.
  22. garcialo
    20:30
    Is there a "beat practices" for a "loading" screen where one of those spinning/hourglass.gif files is displayed for a fraction of a second?
  23. garcialo
    20:30
    ...er...best practice
  24. deborahgu
    20:32
    is that the correct case for aria-busy? Hmm, I wonder if those ought to be aria-progressbar from the accessibility API's point of view. Even though that's not how they display.
  25. garcialo
    20:41
    That's what I was thinking looking at the aria stuff on w3.org, I just don't know how they announce.
  26. garcialo
    20:47
    My first thought was something like a role="alert", but wasn't sure if that would be an appropriate use case for it.
  27. garcialo
    20:49
    I'm more on the WCAG side and less on the development/ARIA side of things. I should probably try out some of that newfangled javar script.
  28. deborahgu
    20:51
    I feel like the sound effect from aria-progressbar would perfectly convey the "waiting for loading" state, except progressbar assumes there's a known min and max value, which is quite accurate.
  29. deborahgu
    20:52
    Although, to be fair, that can be said about MS windows progressbars, too. rimshot
  30. deborahgu
    20:52
    s/which is quite accurate/which isn't quite appropriate in this case/
  31. zakim-robot
    21:54
    [Joe Watkins, a11y] @jiatyan if you put effort into handling the focus state for the user the AT should be set up for success. Send focus to the modal, give them the ability to close the modal, handle focus on close of modal sending them back to where they came from in the DOM, disallow focus to other page elements while modal is open, describe the modal experience to AT aria-describedby, leverage role="dialog",.. and use great markup in the modal and you should be ok.
  32. zakim-robot
    22:34
    [Jiatyan Chen, a11y] @joe-watkins: Thanks. We have already ring-fenced the keyboard interaction and focus for the modal. Challenge is if you were navigation left and right with the arrow keys to page through images, the focus is actually on the arrow buttons, not the image, and thus SR wouldn't read alt-text),
  33. zakim-robot
    22:36
    [Jiatyan Chen, a11y] I'd think it is a pain for SR to have to navigate off the arrow buttons onto the photo, and then back to the arrow buttons to move on to next photo.
  34. zakim-robot
    22:36
    [Jiatyan Chen, a11y] did that make any sense?