Archive index

A11y Slackers Gitter Channel Archive 3rd of February 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Feb 03 00:18
    [dylanb] @karlgroves I would not say “a lot”, I dabbled with making the standard Google map UI keyboard and screen reader accessible as an “overlay"
  2. [dylanb] my recommendation with maps is: think about the use case and see whether you can create a UI that does not rely on the actual map display because if you can, you will probably end up with a user interface that is better for everyone
  3. [dylanb] maps are often just glommed onto pages because it is easy to do and not because it is the best solution
  4. zakim-robot
    @zakim-robot
    Feb 03 02:15
    [caesar] Question re: 3.3.2 Labels or instructions... if the instruction text is just plain text in the form (but occurs prior to the field), doesn't that pass? Or does it have to be part of the label, or associated with the field using aria-describedby?
  5. [caesar] *does that pass.
  6. zakim-robot
    @zakim-robot
    Feb 03 04:32
    [michiel] Caesar: Note: When labels are provided for input objects, the input object's relationship to the label (or to redundant text serving as the label) must be programmatically determinable or available in text per Understanding Success Criterion 1.3.1 Info and Relationships.
  7. [michiel] Also see this WCAG technique: https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H44
  8. [michiel] So, the relationship needs to be programmatic.
  9. [michiel] This is especially helpful with checkboxes and radio buttons.
  10. zakim-robot
    @zakim-robot
    Feb 03 04:40
    [caesar] Thanks @michiel ... sorry, I wasn't clear. What if the instruction is separate to the label? E.g. there's a "Password" label, but then a separate instruction describing the format requirements?
  11. [michiel] An aria-describedby would be helpful in that case.
  12. zakim-robot
    @zakim-robot
    Feb 03 04:46
    [michiel] See example 2 on this page: https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA1
  13. [caesar] Helpful, sure. But is there any expectation that "static text" in a form be explicitly associated with the interactive form elements? Or are SR users expected to use the form using a combination of browse mode and forms mode? (i.e. can't just tab between fields, because you might miss the static content)?
  14. [caesar] I've seen some solve it by assigning tabindex="0" to the static text, for instance.
  15. [michiel] I would say that users expect to get all the information necessary when they tab into the field. However, I'm not a screen reader users, so you might be better off asking them :).
  16. [caesar] Hehe... indeed. Thanks for the info.
  17. zakim-robot
    @zakim-robot
    Feb 03 09:40
    [tink] With iOS there used to be a "Tables" entry in the rotor, but it doesn't seem to be there anymore. Am I misremembering it?
  18. zakim-robot
    @zakim-robot
    Feb 03 09:59
    [skymaiden] hello! quick question – is it OK to use both a title and aria-label? is it ok for them to be identical? (i figured aria-label would be read by screen readers, and the title is shown on rollover)
  19. [tink] For screen reader users, the ARIA will trump the title attribute.
  20. [tink] But depending n the type of element you're applying them to, you may not want to use the title attribute at all.
  21. zakim-robot
    @zakim-robot
    Feb 03 10:09
    [tink] This article has more info on why the title attribute is often not a good idea https://www.paciellogroup.com/blog/2013/01/using-the-html-title-attribute-updated/
  22. zakim-robot
    @zakim-robot
    Feb 03 10:29
    [iandevlin] Hello! I too have a quick question...if an input field has aria-hidden="true", should it also have an associated label? I would think not, however I am of course no expert.
  23. [michiel] iandevlin: why does it have aria-hidden?
  24. [iandevlin] Because it is only being used for adding a suggestion in the background behind what a user is typing.
  25. [michiel] tink: the tables entry is disabled by default. To enable: Settings.app → General → Accessibility → VoiceOver → Rotor.
  26. zakim-robot
    @zakim-robot
    Feb 03 10:34
    [tink] Thanks Michiel :)
  27. [michiel] Sure thing!
  28. [michiel] iandevlin: so is it visible?
  29. [tink] @iandevlin if the field isn't visible/usable by *anyone, then no it doesn't need a label.
  30. [iandevlin] Yeah, it is visible if you can see it, but it shows duplicate information, as the suggestions are also displayed elsewhere, but the top one is shoved under the main input where the user is entering their search term. This is why I was wondering if it is needed, as the info is duplicated.
  31. [iandevlin] Ideally this wouldn't even be an input, but it was added in the past to make the styling easier...
  32. [tink] If it's visible I wuldn't hide it from screen reader users.
  33. [iandevlin] Yeah, this is what I was thinking, I just wanted confirmation, thanks.
  34. [tink] So would remove aria-hidden, give it a (visible) label, and call it done.
  35. [iandevlin] Agreed.
  36. [tink] (highfive)
  37. zakim-robot
    @zakim-robot
    Feb 03 10:39
    [michiel] iandevlin: is this like the google search? Where they have like a placeholder behind the main input? With an auto complete menu underneath?
  38. [iandevlin] Yes michiel, something similar to that.
  39. [michiel] Because in that case I would think it’s safe to hide it, but announce the information in a passive way.
  40. [iandevlin] Hmm, ok. Will look into this too.
  41. [iandevlin] Thanks again.
  42. [michiel] Well, it’s useful information in that if you hit enter it will search for what is showing as placeholder text right? So it would make sense to make that feature available to AT, too.
  43. [michiel] Maybe someone with more experience with such components can give some more concrete feedback.
  44. zakim-robot
    @zakim-robot
    Feb 03 19:37
    [maya] I made this tool and thought you may enjoy! https://twitter.com/mayabenari/status/827600201800044544
  45. [karlgroves] Viking & Lumberjack “trailer” for CSUN https://www.youtube.com/watch?v=vNfKbxErYXQ
  46. zakim-robot
    @zakim-robot
    Feb 03 20:52
    [munrocape] Out of curiosity, I was wondering if there are any mailing lists (twitter accounts?) that are helpful for keeping up on things
  47. zakim-robot
    @zakim-robot
    Feb 03 21:03
    [marcysutton] You could check out Dennis Deacon's blog post? There are a few lists like these of accessibility people to follow http://www.dennisdeacon.com/web-design/accessibility/twitter-accounts-every-accessibility-person-must-follow-part-one/
  48. [maya] @munrocape there’s http://a11yweekly.com/
  49. [maya] past issues: http://us11.campaign-archive2.com/home/?u=884d5f16016183c67252bd18c&id=364cecaf87
  50. [munrocape] cool, thanks!