Archive index

A11y Slackers Gitter Channel Archive 13th of September 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Sep 13 00:28
    [backwardok] I’m looking around the guidelines and I thought I saw somewhere that visual labels were required for form fields, and the closest thing I’ve seen is 3.3.2 (https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html), but it doesn’t specify if the label needs to be persistent (doesn’t go away upon data entry)
  2. [backwardok] the G162 technique (https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G162) mentions validating data with the label, but I haven’t seen anything yet that strictly talks about having those labels there all the time
  3. [backwardok] is this an actual standard that’s part of wcag or is this something that’s just strongly advised? I ask because I’d like to enforce persistent visual labels for form fields, and would like to tie that to an a11y guideline, but I haven’t found that exact wording anywhere
  4. [backwardok] also see in H44 (https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H44): “for Success Criterion 3.3.2, the label element must be visible since it provides assistance to all users who need help understanding the purpose of the field.”
  5. zakim-robot
    @zakim-robot
    Sep 13 04:53
    [garcialo] @backwardok WCAG also doesn't specify if color contrast "needs to be persistent." At the very least, it's pretty much implied that in states where users will be interacting with a webpage, the guidelines must be met in order to claim conformance.
  6. [garcialo] ...including after data is entered into an input
  7. zakim-robot
    @zakim-robot
    Sep 13 05:11
    [garcialo] The only tie-in you should need is the SC itself that requires visible labels whether they're text or something else.
  8. zakim-robot
    @zakim-robot
    Sep 13 15:55
    [ghanek] Persistent labels are good for those w cognitive concerns (& we who are interrupted often, busy, or easily distracted). I'd tie that to SC 3.3.2, @backwardok
  9. zakim-robot
    @zakim-robot
    Sep 13 16:40
    [ghanek] I'll also add to that above group, those of who began a form-based task, and suddenly had to clean up the bio-hazard spill generated by interactions between young humans and pets. (dog emoji) :children_crossing:
  10. [higley] Does anyone have recommendations for a11y dev tools in browsers other than Chrome? Maybe https://addons.mozilla.org/en-US/firefox/addon/ainspector-sidebar/ (I’ve never used it, only the Chrome dev tools :()?
  11. [eric] I like the WAVE extension, as well as aXe
  12. zakim-robot
    @zakim-robot
    Sep 13 16:47
    [dylanb] @higley https://chrome.google.com/webstore/detail/axe/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US&authuser=1
  13. [svinkle] > in browsers other than Chrome
  14. [higley] aXe also has Firefox, so fair enough :)
  15. [ghanek] @higley In Firefox, my team uses aXe, WAVE, and Ainspector Sidebar. Each have different philosophies driving them, which is a good thing. We also use aXe & WAVE in Chrome.
  16. zakim-robot
    @zakim-robot
    Sep 13 16:55
    [dylanb] @svinkle @higley https://addons.mozilla.org/nl/firefox/addon/axe-devtools/
  17. [dylanb] problem is right now that Mozilla has screwed the pooch and you cannot install aXe for FF directly, you have to download the xpi and then install via about:addons -> settings -> install from file
  18. [dylanb] we are working on porting the new UI from Chrome to FF for FF 57
  19. zakim-robot
    @zakim-robot
    Sep 13 17:06
    [higley] Cool, I’m not actually trying to use it myself in FF, just trying to provide some recommendations for other developers :)
  20. zakim-robot
    @zakim-robot
    Sep 13 20:35
    [car] Welcome @maryjom!