Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Automated Accessibility Testing with aXe-core #108

Closed
kentcdodds opened this issue Jun 7, 2016 · 9 comments
Closed

Automated Accessibility Testing with aXe-core #108

kentcdodds opened this issue Jun 7, 2016 · 9 comments
Labels

Comments

@kentcdodds
Copy link
Member

Title: Automated Accessibility Testing with aXe-core

Description: The Deque Labs team is doing some really cool stuff for automated accessibility testing, bringing their years of accessibility expertise to mainstream web developers. The open source axe-core framework, written entirely in JavaScript, supports a bunch of integrations: Webdriver JS, Grunt and Gulp plugins, Chrome and Firefox extensions, and more. Get the low-down on how to integrate accessibility testing into your workflow with the core team from Deque. (pronounced Dee-Cue)

Potential guest(s): @marcysutton, @dylanb, @WilcoFiers

If you haven't heard of JavaScript Air before, it's a live broadcast podcast all about JavaScript. Shows happen every Wednesday at 12:00 Central Time. For more information about being a guest, see this Google Doc. Note: we also have and enforce a Code of Conduct for the show and guests have nothing but great things to say about their experience on the show.

If you've been listed as a potential guest above, please comment on this issue about whether you're interested in coming on to talk about the subject and your availability (or unavailability) for the available dates on the schedule.

If you're interested, I'll need a little information from you for the website. Episode planning happens on the GitHub repo issues. Please comment on your episode’s issue with the following information (if you’d prefer, you can email this info to [email protected]):

  • Your name (as you want it on the site)
  • An email address to share a Google Doc with you
  • Your twitter handle

Thanks!

@dylanb
Copy link

dylanb commented Jun 8, 2016

I would definitely like to participate:

name: Dylan Barrell
email: [email protected]
twitter: @dylanbarrell

@kentcdodds
Copy link
Member Author

@dylanb could you give me two or three days that work for you from the schedule?

@dylanb
Copy link

dylanb commented Jun 8, 2016

@kentcdodds 7/13 and 7/27

@marcysutton
Copy link
Contributor

Yay! Those dates work for me too!

I will email you my info.

@kentcdodds
Copy link
Member Author

ping @WilcoFiers, would you be interested in joining? If so, do 7/13 or 7/27 work for you?

@marcysutton
Copy link
Contributor

Wilco said he could make 7/13 but not 7/27!

@kentcdodds
Copy link
Member Author

Awesome! The 13th it is then!

@kentcdodds
Copy link
Member Author

Really looking forward to this show! I need a few things from you all to get things set up for the show. I got this from @dylanb already. Please read the guest FAQ. Here's the most time intensive piece:

Episode planning happens on the GitHub repo issues. Please comment on your episode’s issue with the following information (if you’d prefer, you can email this info to [email protected]):

  • Your name (as you want it on the site)
  • An email address to share a Google Doc with you
  • Your twitter handle

Thanks!

@WilcoFiers
Copy link

Awesome! So here's my details:
Wilco Fiers, [email protected], @WilcoFiers

kentcdodds pushed a commit that referenced this issue Jun 15, 2016
kentcdodds pushed a commit that referenced this issue Jul 14, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants