Archive index

A11y Slackers Gitter Channel Archive 5th of May 2017

What fresh hell is THIS now? - Patrick Lauke
  1. James Nurthen
    @jnurthen
    May 05 00:05
    I love the fact that their description isn't even correct cause I don't even see the words United States postal service in the graphic
  2. stevefaulkner
    @stevefaulkner
    May 05 10:58

    Hey all! Does anybody have an opinion about this consultancy? Good? Bad? https://www.essentialaccessibility.com

    It would be nice to know who they are, I can't find any actual names of people involved, on the site. I don't trust any accessibility company that doesn't have known quantities involved, but that is just me.

  3. zakim-robot
    @zakim-robot
    May 05 11:02
    [tink] @stevefaulkner this from Linked In https://www.linkedin.com/search/results/people/?facetCurrentCompany=%5B%223512774%22%5D
  4. zakim-robot
    @zakim-robot
    May 05 13:44
    [callumacrae] I'm writing a talk description for a talk on accessibility, is anyone here able to have a look over it? :)
  5. [callumacrae] and in a couple weeks when I've got round to writing the actual talk, the talk itself. but I'm not ready yet :stuck_out_tongue_closed_eyes:
  6. zakim-robot
    @zakim-robot
    May 05 14:03

    [callumacrae] ```
    As developers, we have a responsibility to make sure that as many people as possible can use the websites and applications that we create. From a business point of view, it means there are more potential customers, and from a human point of view, it means that people who might struggle to use computers can still use our websites and access the services they need.

    But with a new generation of websites—single page applications—come a new set of challenges for users with disabilities, and the assistive technology they use to browse the web. Client-side routing, custom input elements, and shiny animated content: all things that screen readers can struggle with if the developer who implemented it didn't consider accessibility.

    During this talk, I'll explain what we as developers can do to ensure that our single page applications are usable by everyone, including people who might not use a keyboard, mouse and screen like the majority of us do. I'll show how some assistive technology is used, and demonstrate how some common mistakes we make affect people using that assistive technology.
    ```

  7. [callumacrae] not sure about the last paragraph. i'm trying to say "people who aren't you" without being hostile, and without saying that PWDs aren't developers
  8. [tink] @callumacrae who is the audience for the talk?
  9. [callumacrae] front-end developers
  10. [callumacrae] talk title is "Accessibility in Single Page Applications"
  11. [tink] If it were me I'd focus on what developers will get out of the talk. Present it as a talk that will help them solve accessibility problems they come across, give them practical and usable examples and information.
  12. zakim-robot
    @zakim-robot
    May 05 14:08
    [tink] Mentioning demos is always a good thing to do, but I'd also talk about design patterns you'll discuss/demonstrate (assuming that's the sort of thing you'll actually be talking about).
  13. [tink] In my experience devs want to know how to fix stuff, rather than why they should fix stuff.
  14. [callumacrae] sure. thanks :)
  15. [callumacrae] the talk is definitely going to be more how to find + fix stuff than why, just didn't want to give it all away in the description! =D
  16. [tink] I know, it's tricky isn't it :)
  17. [tink] Good luck wherever it's for though.
  18. [callumacrae] thanks! it'll be my first ever proper conference. looking forward to it
  19. [callumacrae] it'll also be my first time ever using a screen reader in front of an audience, and i rarely use it, so I'm probably not the best person to demo it :see_no_evil: but it's important that someone talks about it!
  20. zakim-robot
    @zakim-robot
    May 05 14:18
    [tink] I never do it live FWIW. I record demo videos and use those instead. It's a lot less prone to problems.
  21. [tink] Plus it's better in cases of lousy wifi (which is too often the case at conferences).
  22. [tink] jaws
  23. [tink] sighs. Sorry wrong place.
  24. zakim-robot
    @zakim-robot
    May 05 14:34
    [callumacrae] the conference organisers asked for a live demo, but tbh I'd prefer to just record a video
  25. [callumacrae] or, well, audio
  26. [marcysutton] I often pre-record demos too (but not always), especially for mobile devices. Did a few talks myself in the past on single page app a11y for JSConf EU and Angular confs. Making your talk current with inclusive patterns and code examples helps devs understand how it can work from an accessibility point of view. If you do record it live, use the mute button while you're talking.
  27. zakim-robot
    @zakim-robot
    May 05 15:15
    [quidkid] hey guys! so a client is asking us to launch the site but we haven’t finished making it completely accessible, nor has their internal digital governance group has done a spot check on it. I’m feeling pressure from my account manager to launch the site. But i feel like this is so wrong!!!
  28. [quidkid] asking for tips on what to do. shut up and launch the site or what? I told the account manager I’m worried about liability
  29. [tink] @quidkid ask your account manager to confirm in writing they are happy to take responsibility for any liability/law suits that come in as a result.
  30. [tink] At best it'll make them think twice about launching, at worst it'll put responsibility firmly in their court.
  31. [quidkid] @tink thank you so much for responding!! i asked about getting it in writing from the client but she just showed me an email in which the client was like they will handle it on their end(which i think is not going to fly by their digital governance group)
  32. zakim-robot
    @zakim-robot
    May 05 15:20
    [tink] If the email from the client clearly accepts responsibility for the decision to launch an inaccessible site (effectively absolving you/your agency from responsibility), that might be ok.
  33. [tink] If it were me I'd want a very clear and concrete email though.
  34. [tink] Under UK law an agency could technically be sued for aiding and abbetting. It's extraordinarly unlikely, but it is a possibility. I'm not sure about other bits of the world though.
  35. [quidkid] @tink except i’ve worked on so many other sites and I know the process. This is definitely shady on the client’s part but in our SOW we said we’d deliver an accessible website so that’s why i’m feeling uncertain
  36. [tink] Hmm. If it's in the requirements for the project, I'd definitely want the client to state clearly in writing that they are happy to launch without that requirement having been met.
  37. [tink] There may be only so much you can do, if your account manager isn't willing to push the client on it.
  38. [tink] But at the very least I would email your account manager, clearly explaining your concerns and the potential impact, then at least you'll have done all you can.
  39. zakim-robot
    @zakim-robot
    May 05 15:28
    [quidkid] thank you so much @tink I emailed her!!
  40. [tink] Good luck. It's a difficult situation to be in, but I think you've done the right thing.
  41. [quidkid] at the end of the day, that’s what matters most
  42. zakim-robot
    @zakim-robot
    May 05 21:57
    [beefancohen] hey all! i wrote a thing about a11y :) https://twitter.com/beefancohen/status/860601753632260096
  43. [emplums] omgggg @beefancohen accessibility-webpack-plugin is going to be so rad….
  44. zakim-robot
    @zakim-robot
    May 05 22:03
    [emplums] Would love to hear more about your vision with it and see if I can help out at all, I’m setting up automated a11y testing for Buffer right now
  45. zakim-robot
    @zakim-robot
    May 05 22:42
    [beefancohen] haha @emplums woo!! thats awesome
  46. [beefancohen] i guess the thought is that itll server side render all of the components in your app and report a11y on a component-basis during compilation
  47. [beefancohen] the biggest blocker is knowing what props to pass these components
  48. [beefancohen] can also imagine a11y snapshot tests so you can automate regressions