Archive index

A11y Slackers Gitter Channel Archive 30th of May 2017

What fresh hell is THIS now? - Patrick Lauke
  1. [nschonni] This is the initial update from the consultations the Canadian government did to see about our own ADA(ish) thing
  2. Jonathan Neal
    @jonathantneal
    May 30 00:27
    @car @robdodson, great video! I know SEO is gonna get super suspect of hiding headings. Has Google or the like already come out and said hiding “visually obvious” headings won’t be considered a kind of keyword stuffing?
  3. On a related subject to whoever might care, I accidentally left some non-heading elements in a production site while experimenting with <h role="heading">. Google picked it up as the search result’s page title, despite the text never appearing in the document title or in any of the sharing metadata.
  4. Jonathan Neal
    @jonathantneal
    May 30 00:33
    I suspect it was picked up as the page’s heading either because it was visually styled to look like a heading (it quacked like a duck), or because it had that role="heading" attribute.
  5. zakim-robot
    @zakim-robot
    May 30 14:29
    [garcialo] @jonathantneal I know we visually hide headings (and other content) all the time. We also have a couple of SEO people; they don't seem to mind what we do.
  6. zakim-robot
    @zakim-robot
    May 30 14:37
    [cehfisher] there is a related forum thread on read more type links about SEO/accessibility that @stevef started https://productforums.google.com/forum/#!msg/webmasters/YJcZUhtMIE4/XkOEzVakBAAJ
  7. [cehfisher] in case you don’t want to read it a Google guy replied Using something like that is fine. In general, what happens in a case like this is that we focus on the visible, primary content of the page, and de-emphasize the hidden / out-of-view content. So if you're providing extra context & hints like that, that would be fine. There's no "penalty" or "demotion" for having such additional content on a page (and at the same time, it's not something where it would make sense to stuff keywords in the hope that Google picks them up).
  8. zakim-robot
    @zakim-robot
    May 30 15:40
    [tink] We've just published the Inclusive Design 24 (#ID24) schedule... http://inclusivedesign24.org/
  9. [tink] The aim of #ID24 is to bring the conf to the audience (wherever they are in the world), and to make it free and accessible to everyone. Please help us spread the word as far and wide as possible?
  10. zakim-robot
    @zakim-robot
    May 30 15:49
    [carolinelindstrom] Awesome @tink, will definitely share at my company!
  11. Jonathan Neal
    @jonathantneal
    May 30 16:01
    @garcialo @cehfisher thank you so much
  12. powrsurg
    @powrsurg
    May 30 18:38
    http://thehistoryoftheweb.com/putting-web-accessbility-first/ - Mike Paciello referenced right at the start
  13. zakim-robot
    @zakim-robot
    May 30 19:18
    [quidkid] @tink wow thanks tink!!
  14. [tink] Welcome :)
  15. [daniel] Hi, everyone! I’m here at AccessConf in Guelph, Ontario today and there was a booth set up with a team promoting www.accesstext.org. Apparently it’s a free service you can use to request accessible versions of textbooks from certain publishers! Anyway, I just thought I’d share in case it may be of use to anyone. :)
  16. zakim-robot
    @zakim-robot
    May 30 19:43
    [seankeegan] @daniel I believe Access Text is for colleges/universities to request on behalf of students with print-disabilities only at this time. But, yes, it is free to join for post-secondary institutions.
  17. zakim-robot
    @zakim-robot
    May 30 21:14
    [ryan.leisinger] I was recently inspired by a Tweet to do some functional testing of Atlassian's Jira product that does issue tracking, KanBan, Agile Planning... There was quite a bit of functionality I couldn't do. Anyone have success with similar products being accessible?
  18. zakim-robot
    @zakim-robot
    May 30 22:25

    [karlgroves] Ryan: “Similar product” is pretty hard to define when it comes to Jira. There are certainly a lot of issue tracking systems out there, some of which are way more accessible than Jira.

    But Agile planning? Scrum workflows? Kanban boards, etc? A lot of those products are (poo emoji). VersionOne, for instance, has even worse UX overall and is horribly inaccessible.

    Then theres the other things Jira can do, like Help Desk, etc. Lots of things out there have better accessibility for help desks.

  19. [karlgroves] Overall, it kind of depends on the use case. I have a love/ hate relationship with Jira. The UX is horrendous. The permissions model confuses the hell out of me every time I onboard a new person. But I use it every day because I can’t quite find a single replacement for all the things I use.