Archive index

A11y Slackers Gitter Channel Archive 25th of March 2016

What fresh hell is THIS now? - Patrick Lauke
  1. jonathantneal
    Mar 25 02:03
    @afercia, no it wasn’t. I’ll try it again. Glad I asked but sorry if I created any confusion.
  2. jonathantneal
    Mar 25 03:13
    I was able to verify that aria-expanded gets announced in VoiceOver. I’m not sure what my issue was. I’m not sure if aria-controls is announced in any way. Should it do anything special? I see, only in JAWS. Would it be appropriate to have JavaScript listen for clicks on aria-controls and trigger focus on their target?
  3. jonathantneal
    Mar 25 03:21
    ^ related: http://tink.uk/using-the-aria-controls-attribute/
  4. zakim-robot
    Mar 25 07:14
    [jitendra] is role required in this case? 
    <button class="load-more" role="button">    Load More Stories </button>
  5. stevefaulkner
    Mar 25 09:52
    @jitendra no, in fact it's the opposite http://w3c.github.io/aria-in-html/#aria-adds-nothing-to-default-semantics-of-most-html-elements
  6. MichielBijl
    Mar 25 10:57
    @jitendra, no it is not.
  7. MichielBijl
    Mar 25 10:58
    Depending on what you want to achieve, you might want to add type=button; but that's about it.
  8. zakim-robot
    Mar 25 14:23
    [jitendra] @michiel: What’s the benefit of adding `type=“button” here?
  9. zakim-robot
    Mar 25 14:30
    [juryjowns] type=“button” is if the button is inside a form and you don’t want it to submit the form.
  10. zakim-robot
    Mar 25 14:30
    [juryjowns] otherwise buttons default to type=“submit"
  11. zakim-robot
    Mar 25 14:32
    [jdan] @juryjowns TIL - thanks!
  12. zakim-robot
    Mar 25 14:34
    [juryjowns] @jdan I learned that a couple months ago, and it stuck since I thought it was strange that buttons default to type=“submit” instead of type=“button"
  13. zakim-robot
    Mar 25 19:15
    [marcysutton] I learned that working on a UI framework, where buttons are sometimes inside of forms and sometimes not :)
  14. zakim-robot
    Mar 25 19:20
    [juryjowns] @marcysutton: That makes sense. Better set your state, because you have no idea where someone is going to put it!
  15. zakim-robot
    Mar 25 19:35
    [ellyjones] when computing the accessible name for an <input type="checkbox"> that is inside a fieldset with a legend, should the accessible description of the legend be appended to the accessible description for the checkbox?
  16. zakim-robot
    Mar 25 19:35
    [ellyjones] (I'm trying to figure out what needs to be done with https://crbug.com/550663, and it references a w3c bug that doesn't seem entirely related...)