Archive index

A11y Slackers Gitter Channel Archive 2nd of October 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Oct 02 01:14
    [hello] Has anyone taken the IAAP WAS (Web Accessibility Specialist) exam? or is planning to take it this month, like me? :)
  2. Peter Krautzberger
    @pkra
    Oct 02 08:00
    @svinkle thanks for the link. I know that one, too :smile: but I was looking for user advice for exploring SVGs (not authoring tips like the article). I'll make a demo of what VO on the desktop can do and ask again :)
  3. zakim-robot
    @zakim-robot
    Oct 02 13:36
    [floressu] after the excellent sessions of #a11yTOConf last week, colleagues are interested in participating here - is the @ontario.ca email domain an open one, or do they need a specific invite? thanks
  4. zakim-robot
    @zakim-robot
    Oct 02 13:44
    [thanks4allthefish] @lauraf is there any workaround for it?
  5. [svinkle] @floressu Anyone can join! :point_right: https://web-a11y.herokuapp.com/
  6. zakim-robot
    @zakim-robot
    Oct 02 14:12
    [floressu] @svinkle excellent, thanks so much
  7. zakim-robot
    @zakim-robot
    Oct 02 15:19
    [trave] Anyone else in here trying out the awesome vue-a11y-calendar component? Its working beautifully in chrome for me, but for whatever reason in firefox/safari (on macOS) only the outermost wrapper element is receiving focus when trying to click on any of the day buttons. Im trying to pinpoint why, but haven't figured out why quite yet. If you've got any suggestions of things to look for I welcome the feedback. :]
  8. [svinkle] @trave Are you referring to this one? https://github.com/IBM/vue-a11y-calendar
  9. zakim-robot
    @zakim-robot
    Oct 02 15:29
    [trave] yes
  10. [svinkle] I wish there was an online demo to check it out but I don’t see a link.
    Perhaps @car may have some insight?
  11. zakim-robot
    @zakim-robot
    Oct 02 15:36
    [trave] lemme see about throwing up something, or tracking down where their docs code is running with a working example.
  12. [trave] @svinkle https://ibm.github.io/vue-a11y-calendar/components/calendar
  13. [svinkle] @trave Thanks! Wow, yeah I see what you mean. That doesn’t seem right. (thinking face emoji)
  14. [trave] works great in Chrome
  15. [trave] I added an issue to their git repo, I just wanted to be more helpful and try to track down a reason/solution ... its strange
  16. zakim-robot
    @zakim-robot
    Oct 02 15:41

    [rselzer] > works great in Chrome

    Famous last words

  17. [trave] heh
  18. zakim-robot
    @zakim-robot
    Oct 02 15:56
    [trave] I believe Im on the right track to solve it, the javascript is expecting the click event to be triggered from the TD cell around the BUTTON element, looking for a specific classname... I'll add some logic there to handle it, and make a pull-request to contribute it back up the stream. :]
  19. [trave] thanks for the attention and letting me think outloud in here =D
  20. zakim-robot
    @zakim-robot
    Oct 02 18:09
    [jasonday] Anyone know of a11y quizzes or such?
  21. [jasonday] dev specific
  22. zakim-robot
    @zakim-robot
    Oct 02 18:36
    [cehfisher] i like this resource @jasonday https://teachaccess.github.io/tutorial/ for beginners/intermediate devs
  23. [cehfisher] not sure how advanced you are looking to go
  24. zakim-robot
    @zakim-robot
    Oct 02 19:18
    [quidkid] this is so cool and it claims to be accessible but not sure if it is really… https://shopify.github.io/draggable/
  25. [eric] can’t focus on anything on tab, I think they’re using accessible to mean “approachable”
  26. zakim-robot
    @zakim-robot
    Oct 02 19:28
    [quidkid] yeah couldn’t focus anything via keyboard either but I think it’s in the works: Draggable supports most of the interaction events we could think of – mouse, touch, and force touch are all available out of the box, with accessible keyboard support coming soon
  27. zakim-robot
    @zakim-robot
    Oct 02 19:54
    [jonathantneal] Well, at least “accessible” is now a powerful buzz word.
  28. zakim-robot
    @zakim-robot
    Oct 02 20:11
    [svinkle] I was at the meetup when this was first presented; pretty incredible stuff. But no, not really accessible.
  29. [svinkle] Also it was a demo about the web audio api more than a drag-and-drop component.
  30. zakim-robot
    @zakim-robot
    Oct 02 21:25
    [robdodson] hey folks, i just published a post on custom elements/web components, accessibility, and where I see the whole thing heading. Hoping to get more folks interested in AOM :) https://medium.com/dev-channel/the-future-of-accessibility-for-custom-elements-291cfb3ffabe
  31. zakim-robot
    @zakim-robot
    Oct 02 21:47
    [jonathantneal] That was good. Reality is more sobering than refreshing, but such is life for things not purely JS these days.
  32. zakim-robot
    @zakim-robot
    Oct 02 22:30

    [svinkle] I didn’t get AOM at first, why it was needed. It just seemed like it was using JS in-place of HTML attributes. That is, until I read the explainer doc: https://wicg.github.io/aom/explainer.html

    It can be thought of in the same way that folks are using React components as a level of abstraction for developers to build apps, usually in the form of a style guide. The same could be used for HTML; need a slider? 

    <custom-slider min="0" max="5" value="3"></custom-slider>
  33. zakim-robot
    @zakim-robot
    Oct 02 22:37
    [caesar] Honest question: wouldn't it be better to put the effort into making the widgets from the existing (popular) frameworks accessible, than to create a new framework altogether?
  34. [caesar] Reminds me of the xkcd comic where creating something to replace something else just results in 1 more new thing that needs to be supported.
  35. zakim-robot
    @zakim-robot
    Oct 02 22:45
    [jonathantneal] http://i0.kym-cdn.com/photos/images/newsfeed/000/538/731/0fc.gif
  36. [caesar] LOL I can think of many reasons why not, but I don't wanna pretend like I know what I'm talking about. I'm no front-end developer :)
  37. zakim-robot
    @zakim-robot
    Oct 02 22:52
    [simonmaher] It would be better if the existing frameworks were made accessible, but I feel it would be more feasible for new frameworks to be created in their place.
  38. [robdodson] Responded in the thread. We're not proposing building a new framework or anything.
  39. [robdodson] I think there was maybe some confusion around web components or maybe the howto-components project?

  40. [svinkle] I think folks are just trying to take some of the positive aspects of modern frameworks and reign it back to the native browser API. Some of the concepts were seeing are pretty great. It would also help when folks want to use non-native controls to match a design; get semantics and functionality right the first time. That's my thought anyway.

    Please let me know of I'm off my rocker.

  41. [robdodson] Yes. Web components are an attempt to standardize the ideas from various frameworks so developers can write components that work anywhere. Today if you write an angular component you can't use it in a react app. But if you write a web component you can use it anywhere.
  42. [svinkle] That sounds good to me! Thanks for explaining, @robdodson thumbsup emoji
  43. zakim-robot
    @zakim-robot
    Oct 02 23:25
    [caesar] @robdodson thanks for the explanation. I did have a disclaimer that I wasn't a front-end dev!