6 comments

  • Dustin CartwrightDustin Cartwright, 7 years ago

    This is great! The main holdup my team had with FA was the accessibility problems. It's good to see some highly used resources focus on that area, both as a designer and a deaf guy.

    3 points
    • Duke CavinskiDuke Cavinski, 7 years ago

      This was always the controversial part of these things, and I'm glad it's being addressed.

      0 points
    • Brian Talbot, 7 years ago

      Thanks, Dustin and all.

      Yeah, we're excited to be working on topics like this one. We collaborated with a few a11y industry folks to get this first pass out, but are hoping to learn more about:

      • how folks using Font Awesome are doing using the techniques
      • how the techniques are working for users with assistive tech and special contexts

      Once we know more, we'll keep on improving things over time. :)

      1 point
  • Peter AntoniusPeter Antonius, 7 years ago

    Hmm, why not aria-label or aria-labelledby?

    0 points
    • Brian Talbot, 7 years ago

      Hi, Peter.

      Good question. I've seen those techniques used before, but they did not come up on the Github issue (https://github.com/FortAwesome/Font-Awesome/issues/6133) nor the PR that addressed the issue (https://github.com/FortAwesome/Font-Awesome/pull/8879). While I am not very well seasoned with current aria/a11y practices, those threads had several active folks who are.

      I'm going to throw your good question by them. Feel free to read through those threads in the meantime. :)

      1 point
    • Brian Talbot, 7 years ago

      Hey, Peter.

      I talked with folks who are much smarter than I about accessibility about not using on the aria-label or aria-labelledby attributes.

      In short, ARIA is a screen reader only solution, and while support is pretty good, its not supported consistently everywhere or for every case. It’s always best to use the lowest tech solution possible, in this case the sr-only class and title attribute.

      0 points