Archive index

A11y Slackers Gitter Channel Archive 21st of June 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jun 21 19:26
    [tyronem] this might be a silly question, but I want to cover all my bases: I have a link that has a disabled class that is supposed to disable clicking. I added an aria-disabled=“true”. Should I also add a role of link to that <a> tag, even though it’s already a link?
  2. zakim-robot
    @zakim-robot
    Jun 21 20:01
    [johnbhartley] disabled is not a valid attribute for anchors, would you be able to use a <button> instead? for list of valid attributes on <anchor> https://dev.w3.org/html5/html-author/#the-a-element
  3. [johnbhartley] ah, but your question is about aria-disabled, so that may not be the same
  4. zakim-robot
    @zakim-robot
    Jun 21 20:08

    [johnbhartley] @tyronem because it is already a link, you wouldn't need to add a role of link onto the <a> as browsers will already interpret it as such. if you would want it to act like a button you could give it role="button" but in this case it sounds like it's a true link. here's how browsers/AT ought to read it: http://maxdesign.com.au/jobs/sample-accessibility/05-forms/attribute-disabled.html

    if the link performs like a button then you could use the aria-disabled="true" disabled combo. to get the AT to read it as "Disabled"

  5. zakim-robot
    @zakim-robot
    Jun 21 20:23
    [tyronem] makes sense. I appreciate your answer @johnbhartley.
  6. zakim-robot
    @zakim-robot
    Jun 21 22:54
    [yang] Hey guys, I'm new here. What channel should I join to learn more about Section 508 compliance? thanks :)
  7. [michiel] Hey Yang, welcome to the party :tada:. I think you can drop your 508 questions right here :).
  8. zakim-robot
    @zakim-robot
    Jun 21 23:05
    [yang] Thanks Michiel, I'm looking into different accessibility standards: Section 508, WCAG 2.0 - W3C, and WAI-ARIA, trying to figure out their differences and which one my company should potentially go after. Any suggestion? Love to hear from folks who have gone through these processes :)
  9. [michiel] It depends on your companies situation. Where are they based?
  10. [michiel] WCAG 2.0 is the global “standard” when it comes to accessibility compliance on the web.
  11. zakim-robot
    @zakim-robot
    Jun 21 23:13
    [michiel] 508 and WCAG are both guidelines that’ll tell you what you need to do to make your web application accessible. With WCAG 2.0 being the more modern standard.
  12. [michiel] WAI-ARIA is a specification which provides you with the means to convey an elements role, state, and property.
  13. zakim-robot
    @zakim-robot
    Jun 21 23:28
    [michiel] If you get started with ARIA at some point be sure to have a look at the ARIA Authoring Practices: http://w3c.github.io/aria-practices/
  14. [michiel] (Which details how to use ARIA)
  15. zakim-robot
    @zakim-robot
    Jun 21 23:42
    [yang] Thank you Michiel. My company is Asana, we are based in San Francisco, but we do have global customers. We are getting an increasing amount of requests from some customers (especially governmental sectors) on accessibility. That's why I am exploring these options now.
  16. zakim-robot
    @zakim-robot
    Jun 21 23:52
    [michiel] For US government it’s still 508 I think. But I’m not really sure.
  17. [michiel] karlgroves or tink will probably know.
  18. [karlgroves] I heard my name
  19. [karlgroves] For the US Government, it is still 508. The difference now, however, is that with the 508 Refresh they've incorporated WCAG by reference
  20. [karlgroves] What that means is that 508 no longer has its own technical provisions(*) but rather points to WCAG
  21. [michiel] So 508 Refresh ≈ WCAG 2.0?