Archive index

A11y Slackers Gitter Channel Archive 14th of September 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Sep 14 00:03
    [herin] Hi :question: If my language is managed by meta tag and browser overrides it. Firefox shows En-GB and Chrome has En-US. Do you foresee any accessibility issues with this?
  2. zakim-robot
    @zakim-robot
    Sep 14 08:29
    [michiel] @herin: if it also overwrites it when the base language isn’t English. Say you set it to nl-nl and it’s overwritten by EN-US, then it would cause a11y issues.
  3. zakim-robot
    @zakim-robot
    Sep 14 08:50
    [adam4h] Hi
  4. [adam4h] any recommendations fro a website accessible ADA menu? only found examples from 2015
  5. zakim-robot
    @zakim-robot
    Sep 14 08:56
    [herin] Thank you @michiel
  6. zakim-robot
    @zakim-robot
    Sep 14 12:44
    [jasonday] @adam4h - Do you mean something like a mega menu? There are a lot of minor variations in behavior (search adobe a11y menu, and bootstrap navbar), but I like the following pattern:
  7. [david.laforest] There a lot of documentation on W3C about menu. You can find some here https://www.w3.org/WAI/tutorials/menus/ plus linked to success criteria
  8. zakim-robot
    @zakim-robot
    Sep 14 12:52
    [jasonday] I tend towards simplicity for menus - https://v4-alpha.getbootstrap.com/components/navbar/
  9. [jasonday] I think it's easy to get overly fiddly with behaviors
  10. zakim-robot
    @zakim-robot
    Sep 14 15:01
    [adam4h] @jasonday @david.laforest Thanks for your input
  11. zakim-robot
    @zakim-robot
    Sep 14 18:17
    [jz] Question about implementing a tabs interface, following the ARIA guidelines https://www.w3.org/TR/wai-aria-practices-1.1/#tabpanel - I've got a panel that has data requirements and may be noticeably slow to render. It seems like a better user experience to not render this panel's contents until the user selects it (they might never select it) - until the user selects the corresponding tab, should I render an empty panel, or no panel at all? If the answer is "no panel" - is it ok for the aria-controls attribute of the tabs to point to elements that don't exist?
  12. zakim-robot
    @zakim-robot
    Sep 14 18:38
    [david.laforest] show the tab panel and dont forget to give feedback to the user (both visual and screenreader) about the process occuring. When the process ends, show the content and notify screenreader user.
  13. [david.laforest] the rendering content is an equivalent feedback for visual user
  14. powrsurg
    @powrsurg
    Sep 14 19:20
    Heh, AWS S3 going down, again, during my team testing a new feature we're looking to deploy has resulted in us making some improvements in our alt text rendering ...
  15. zakim-robot
    @zakim-robot
    Sep 14 20:40
    [vicodin] Hey everyone, I am planning to give a talk in some conf on a11y and UX, like how a11y is subset of UX and all. This will include some basics and some tricks and tips to improve UX by making things accessible. The talk could be max 20 min long so I am not sure if I could cover ARIA, and planning to include only CSS things like color contrast, hiding things etc, and maybe semantic elements. How does that sound? Do you guys think its a good idea? and if not how it can be improved :)
    PS: I am focusing on UX part since the conf is about UX and also people might actually show interest in a11y if it helps them improving UX. Also, my first proposal.
  16. zakim-robot
    @zakim-robot
    Sep 14 23:06
    [marcysutton] @vicodin who is the audience? I'd say ARIA is more on the advanced side of things, there's a lot you could cover before even getting to that topic. So yeah, it would be fine to leave out of a 20-minute talk.
  17. [marcysutton] To answer my own question: if it's UX folks, I'd definitely leave it out. ARIA is inherently developer-centric
  18. zakim-robot
    @zakim-robot
    Sep 14 23:42
    [spell] Any good examples out there of organizations that speak to accessibility within their brand guidelines?
  19. [caseygreene] These two are pretty good:
  20. [caseygreene] http://accessibility.voxmedia.com/
  21. [caseygreene] https://ux.shopify.com/creating-an-accessible-culture-199aaec12232
  22. zakim-robot
    @zakim-robot
    Sep 14 23:47
    [spell] Cool! Thanks, @caseygreene
  23. [caseygreene] I can't speak to how comprehensive they are, but it at least looks like they've spent time thinking about how the principles of accessibility mesh with their internal philosophies