Archive index

A11y Slackers Gitter Channel Archive 14th of October 2015

What fresh hell is THIS now? - Patrick Lauke
  1. MichielBijl
    09:39
    @stevefaulkner are you here?
  2. stevefaulkner
    10:00
    @MichielBijl am now :-)
  3. MichielBijl
    10:01
    “semantic magic is done my the browser”
  4. MichielBijl
    10:01
    https://www.paciellogroup.com/blog/2015/09/easy-content-organisation-with-html5/#comment-2412
  5. MichielBijl
    10:02
    Think that should be by ;)
  6. MichielBijl
    10:02
    Or is it only your browser :P
  7. stevefaulkner
    10:11
    thanks :clap: fixed
  8. zakim-robot
    11:17
    [jitendra, a11y] thanks @ccwilcox will check
  9. MichielBijl
    14:47
    /rant Uhg, I have to make an html newsletter
  10. MichielBijl
    14:54
    Are there any resources on making newsletters accessible?
  11. MichielBijl
    14:54
    All I find are newsletters about accessibility :P
  12. zakim-robot
    15:05

    [Jordan Scales, a11y] hey all! I develop a tool called tota11y and I’m looking into making its error reporting more accessible. in the following example I have an <input> on the document, then I place an “annotation” above the <input>, letting the user know that it has a violation. that “annotation” is then linked to an entry in the “info panel” with some more information.

    particularly, I’m interested in connecting the “annotation” with the input such that the user could navigate between the two easily with a keyboard

  13. zakim-robot
    15:05
    [Jordan Scales, a11y] Pasted image at 2015-10-14, 11:05 AM
  14. zakim-robot
    15:06
    [Jordan Scales, a11y] the issue is that the “annotation” and input are not necessarily siblings in the DOM! should they be? I’m thinking that if I can make them siblings, I’ll get keyboard a11y for free
  15. zakim-robot
    15:08
    [Jordan Scales, a11y] the small magnifying glass to the right of “Input is missing a label” in the “info panel” currently scrolls to the violating element (and, consequently, its “annotation), but I’m looking to instead make that magnifying glass focus_ the element. My concern then is how the user would get _back from the element to the info panel
  16. MichielBijl
    15:09
    aria-describedby on the input linking to the annotation?
  17. MichielBijl
    15:09
    Or make the whole thing a figure
  18. MichielBijl
    15:09
    It's an example, so it would fit perfectly in a <figure>
  19. MichielBijl
    15:10
    put aria-describedby on the figure and boom, they are linked
  20. zakim-robot
    15:10
    [Jordan Scales, a11y] aria-describedby was another thought I had - but will that further enable the user to navigate between the input and annotation? the reason I ask is because I can bridge the annotation to the info panel with the small “?” you’ll see in the annotation
  21. zakim-robot
    15:11
    [Jordan Scales, a11y] or would aria-describedby simply read off the text, then it’s up for the user to find the info panel
  22. MichielBijl
    15:11
    It would read of the text AFAIK
  23. MichielBijl
    15:12
    I mean, AFAIK there is no way to navigate between the element with aria-describedby, and the element it references
  24. zakim-robot
    15:12
    [Jordan Scales, a11y] what if the input was aria-describedby the detailed error message in the info panel? and the annotation itself was just inaccessible (it doesn’t provide any extra information)
  25. zakim-robot
    15:12
    [Jordan Scales, a11y] I like the idea of <figure> though! very interesting
  26. MichielBijl
    15:12
    I'd suggest something like this; hang on a minute
  27. MichielBijl
    15:15 
    <figure aria-describedby="long-description">   <!-- Example here -->   <figcaption>Input is missing a label</figcaption> </figure>  <div id="long-description">   <h2>Input is missing a label</h2>   <p>Inputs should have labels you dimwit</p> </div>
  28. MichielBijl
    15:16
    You could link to the description from the figcaption :)
  29. zakim-robot
    15:19
    [Jordan Scales, a11y] a-ha, I love it! tricky bit will be getting the input and annotation inside of the same <figure> because they’re not necessarily close to each in the DOM - but I can work that out
  30. zakim-robot
    15:19
    [Jordan Scales, a11y] thank you as always michiel!
  31. MichielBijl
    15:19
    No problem! Thank you for building this tool!
  32. stevefaulkner
    15:46
    This message was deleted
  33. stevefaulkner
    15:47

    [Jordan Scales, a11y] what if the input was aria-describedby the detailed error message in the info panel? and the annotation itself was just inaccessible (it doesn’t provide any extra information)

    Note accdescriptions are conveyed as a text string, no semantics.

  34. stevefaulkner
    15:47
    as are accnames
  35. MichielBijl
    15:48
    Good to know
  36. MichielBijl
    15:49
    Still, should link to the description from the ficaption
  37. MichielBijl
    15:49
    figcaption*
  38. powrsurg
    18:06
    So I filled out that survey to talk to Microsoft about accessibility and they sent me to form to fill out when they would like to call to talk to me. I like that the little graphic to promote their mobile app does not have sufficient contrast on the android and ios buttons on the form's confirmation page
  39. zakim-robot
    20:20
    [Claire Ryberg, a11y] Was this question ever resolved? http://lists.w3.org/Archives/Public/wai-xtech/2012Jul/0007.html
  40. zakim-robot
    20:21
    [Claire Ryberg, a11y] I'm running into the same problem, where I have a list of selectable <a> items, and I would like to use aria-selected for the one that gets clicked
  41. stevefaulkner
    21:03
    @Claire yes http://www.w3.org/TR/wai-aria-1.1/#aria-current but it is new and has not been implemented yet
  42. stevefaulkner
    21:06
    @cryberg ^^
  43. zakim-robot
    21:09
    [Claire Ryberg, a11y] @stevef: Thank you! Thats really helpful to know
  44. stevefaulkner
    21:12
    :+1:
  45. zakim-robot
    21:22
    [Claire Ryberg, a11y] @stevef: do you know how aria-current="true" might be read by a screen reader once it is implemented? I don't know that a selected item in a list reading as "current item" would make more sense than hearing "selected"
  46. zakim-robot
    23:35
    [ldavis, a11y] does anyone know why an empty anchor tag with simply a class would not pass chromes accessibility developer tools? These are place holders for other content btw
  47. zakim-robot
    23:45
    [Marcy Sutton, a11y] @ldavis: which audit rule is failing? That should help you narrow it down. Does it have any discernible text in it?