-
Notifications
You must be signed in to change notification settings - Fork 34
Automated Accessibility Testing with aXe-core #108
Comments
I would definitely like to participate: name: Dylan Barrell |
@dylanb could you give me two or three days that work for you from the schedule? |
@kentcdodds 7/13 and 7/27 |
Yay! Those dates work for me too! I will email you my info. |
ping @WilcoFiers, would you be interested in joining? If so, do 7/13 or 7/27 work for you? |
Wilco said he could make 7/13 but not 7/27! |
Awesome! The 13th it is then! |
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]):
Thanks! |
Awesome! So here's my details: |
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]):
Thanks!
The text was updated successfully, but these errors were encountered: