Archive index

A11y Slackers Gitter Channel Archive 20th of July 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jul 20 00:08
    [karlgroves] I miss all the fun conversations
  2. zakim-robot
    @zakim-robot
    Jul 20 01:36
    [ugi] Untitled
  3. zakim-robot
    @zakim-robot
    Jul 20 02:13
    [caesar] It must be something else, because when I try that code by itself in Codepen JAWS reads fine: https://codepen.io/cyberseraphic/pen/RgzzBV
  4. zakim-robot
    @zakim-robot
    Jul 20 06:00
    [christopherpigden] Hi guys, I was wondering what your opinion is on using all caps on text for headings? I know that as a general rule we should avoid using all caps for paragraphs of text because they can be difficult for some users to read but is it ok to use it for headings or links that have 1 or 2 words?
  5. zakim-robot
    @zakim-robot
    Jul 20 06:54
    [veyfeyken] Thumbs up for slack implementing keyboard a11y: https://get.slack.help/hc/en-us/articles/115003340723
  6. zakim-robot
    @zakim-robot
    Jul 20 11:20
    [herin]
    Hi @christopherpigden, its a genetal rule to avoid capital letters.
    A simple reason i learned while looking for an answer to this is "Braille does not have a separate alphabet of capital letters as there is in print. Capital letters are indicated by placing a dot 6 in front of the letter to be capitalized. Two capital signs mean the whole word is capitalized.".
    When the whole word is capitalized its often considered as an abbreviation.
  7. [herin] Braille users using refreshing displays often needs more time to perceive the information than others. This causes more delay when the caps does not mean its an abbreviation and used for styling of headings.
  8. zakim-robot
    @zakim-robot
    Jul 20 11:26
    [christopherpigden] @herin Thanks for the info! Really interesting. Is this the main reason to not use capitals or are there others? Does it also cause problems for some sighted users?
  9. [herin] Yes. When certain fonts are used its hard to distinguish between I and L.
    Users with learning disabilities amd reading challenges depend on font height for faster reading.
    Assistive technologies including screen readers read the word letter by letter in some cases etc
  10. [herin] There has always been a debate on this.
  11. [herin] I stick to "if caps does not change the message we are trying to convey, we should avoid all caps"
  12. zakim-robot
    @zakim-robot
    Jul 20 11:31
    [herin] In most cases, designs adapt all caps for visual effects
  13. zakim-robot
    @zakim-robot
    Jul 20 11:40
    [christopherpigden] Ok thanks @herin! we’ve been discussing this at work today. There are some headings on our web pages that use all caps and I’ve been trying to make a case for not doing that with future templates due to problems it cause for users with dyslexia. I knew that it was a bad idea to use them but didn’t have a solid argument to back it up. I’ll pass this info along it’s really helpful.
  14. [herin] Thank you @christopherpigden. I think I raised it sometime ago. Glad I was able to help. Cheers!
  15. [herin] Gud luck!
  16. [christopherpigden] Thanks! :)
  17. [tink] @herin +1 on avoiding all caps.
  18. zakim-robot
    @zakim-robot
    Jul 20 11:49
    [herin] Was funny when we did some testing with AT for an Frequently Asked Questions (FAQ) page on an educational site.
    We had to avoid abbreviation so that it sounds good for students. =@
  19. [herin] It has to look good, sound good and work good too.
  20. [tink] A little while ago, I wrote about writing content that works with screen readers https://accessibility.blog.gov.uk/2017/02/08/advice-for-creating-content-that-works-well-with-screen-readers/
  21. zakim-robot
    @zakim-robot
    Jul 20 11:54
    [herin] Thanks for sharing @tink
  22. [tink] NP
  23. zakim-robot
    @zakim-robot
    Jul 20 12:17
    [christopherpigden] thanks @tink! will definitely share this with the team
  24. [donnabungard] awesome! Another good tip that goes along w that, that I've picked up from this community, is to write to a 6th grade reading level. That it's not about talking down but rather if you keep that in mind it'll help you to keep the verbiage simple and clear enough for screen readers while improving overall UX.
  25. zakim-robot
    @zakim-robot
    Jul 20 17:51
    [ghanek] Whoa! This Slack team just got a fancy icon! Image: A11y icon, with the A in red, 11 in blue, and the Y in orange.

  26. [george_zamfir] :wave: Hi everyone

    We released the keyboard accessibility / navigation improvements to all users & teams. Please feel free to use it and if you have feedback for us we’d love to hear it :a11y: <3

    https://web-a11y.slack.com/archives/C043BSXEN/p1500312439715557

  27. [george_zamfir] FYI: I’ve also used my new-found admin powers to upload a new :a11y: icon & emoji. You can use :a11y or :accessibility: to use this emoji.
  28. [george_zamfir] Screenshot of the emoji panel with the a11y emoji highlighted
  29. [ghanek] @george_zamfir Is that a custom emoji only for this team?
  30. zakim-robot
    @zakim-robot
    Jul 20 18:00
    [george_zamfir] It is actually the a11y emoji we use internally at Slack. But this team is special so here we are :a11y:
  31. [marcysutton] I already feel validated for making @george_zamfir a team admin! Thanks George!
  32. zakim-robot
    @zakim-robot
    Jul 20 18:24
    [elliottregan] Nice new logo you’ve got there!
  33. zakim-robot
    @zakim-robot
    Jul 20 21:09
    [virtualalex] Is the standard “visited link” behavior accessible?
  34. [virtualalex] Dark blue for link, dark purple for visited?
  35. [virtualalex] aren’t those pretty close together?
  36. [virtualalex] Another dumb question: why would a link/button ever not be activatable by keyboard? Is there actually a reason to DISABLE keyboard controllers?
  37. Michael Fairchild
    @mfairchild365
    Jul 20 21:55
    If some of y'all have a moment, would you mind weighing in on this issue? a11yproject/a11yproject.com#499