Archive index

A11y Slackers Gitter Channel Archive 1st of October 2016

What fresh hell is THIS now? - Patrick Lauke
  1. Jonathan Neal
    @jonathantneal
    Oct 01 00:00
    Reviewing Adobe’s accessible mega-menu, I noticed they use aria-expanded on both the parent link and its sub-menu container. What is the benefit to give both elements this?
  2. James Nurthen
    @jnurthen
    Oct 01 04:48
    I guess they weren't sure which it should go on so they put it on both. It should only be on the parent link IMO.
  3. zakim-robot
    @zakim-robot
    Oct 01 13:00

    [car] @herman Sorry this is a few days late for your session discussion, but perhaps this is the IBM link you were looking for? http://www-03.ibm.com/able/guidelines/ci162/accessibility_checklist_web.html
    Look for "contrast" on that page, and you will see:

    1.4.3 Contrast (Minimum). The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, with a 3:1 ratio for large-scale text. (Level AA)
    Details are linked to here: http://www-03.ibm.com/able/guidelines/ci162/contrast.html
    You will note that this is the same as WCAG 2.0 1.4.3 (which is linked to from the checkpoint's page).

  4. zakim-robot
    @zakim-robot
    Oct 01 16:41
    [emplums] Giving a workshop on accessibility this week and I'm starting to realize my workshop feels a lot more like a talk... anyone have any hands on ideas to do in an accessibility themed workshop?
  5. [emplums] I'm planning on having everyone try to use a screen reader, introducing people to different extension tools, showing them a few things to add to the build process & was going to have everyone get pa11y running on a server but I'm worried it's too complicated for a workshop
  6. luis garcia
    @garcialo
    Oct 01 20:44
    I'd definitely say setting up an instance of pa11y would be too complicated for a workshop
  7. @emplums what are you trying to accomplish with the workshop?
  8. zakim-robot
    @zakim-robot
    Oct 01 20:53
    [emplums] @garcialo: two things: 1) I want to show the workshoppers what it's like to navigate the web with a disability, to have them actually try out the websites they work with through the lenses of someone with a disability and 2) want to give them the tools to work implementing accessible features & testing for accessibility into their current workflow
  9. luis garcia
    @garcialo
    Oct 01 21:42
    @emplums I personally would only suggest simple/free tools for beginners. HTML Codesniffer; sure just make sure they're not doing analysis on pages that will throw a lot of errors. Pa11y would be a bit overkill and too much opportunity for demo hell and getting trapped in troubleshooting.
  10. zakim-robot
    @zakim-robot
    Oct 01 21:47
    [emplums] @garcialo: hahah good point, I agree I think pa11y would be too much. I'm trying to put myself in the shoes of a complete beginner and try to remember the biggest questions about a11y I had.
  11. [emplums] Maybe I could pick out some sites before hand that have good examples of a11y issues that aren't too overwhelming
  12. [garcialo] What's the audience?
  13. [emplums] And I could show them build tests running on my environment but not necessarily ask them to do it on theirs cause that might be too much
  14. [emplums] Jsconf Colombia
  15. [garcialo] Have them use their sites. Just use a simple site like the BAD or demonstrating how to use the tools
  16. [emplums] So not really sure what the range of a11y experience will be but just going to assume everyone is a beginner. I put in my description that I'll be going over the basics so people who already know a lot I'm sure won't come
  17. [garcialo] They're all effectively the same in use. Run the tools, figure out the issues, find out how to fix it, change the son, rerun tool
  18. [garcialo] Change the DOM
  19. [emplums] Cool cool :)
  20. [emplums] Thank you! Helps so much to run these ideas past someone else