Joe Colantonio
All right. Tool number three is our Accessibility Scanner, and this is one of my personal favorites. As you know, accessibility is everyone's responsibility, but most teams don't have time or budget for big audits or as an automation engineer, you don't necessarily know where to focus in your efforts or what code to use to actually validate some of these issues. And that's what's unique about this scan. It's created specifically for automation test engineers. It lets you get screenshots, plain English explanations, ownership tags and ready to use test code for either Selenium, Cypress or Playwright. And obviously, the Test Guild Accessibility Scanner is free. No login required. You just paste your URL. And it runs a quick check based on accessibility best practices. Things like alt text, area roles, contrast ratios and more. Think of it as almost like a smoke test for accessibility. If you haven't done any accessibility, this is step one that you should be doing for sure. Once you do that, you'll get a report that helps you catch common issues early before they possibly could end up costing you compliance fines or user trust. Plus, I think it's a great tool to use as a conversation starter to bring accessibility awareness into your sprints. Sounds cool, right? All right, let's check this out. All right. For the accessibility scanner, all you need to do is enter in your website. Let's do, I don't know, let us do ESPN. To check the type of validation. I wanted to WCAG 2.2. Start your scan. It can take a little bit. I added some quotes to help pass the time. All right, scan is done. First thing is you can either do developer mode or non developer mode. It just makes it simple to read. I keep it on developer mode, you can also do different views. You have a classic view. It'll tell you what that means. Or you could do a navigation cards, which I like better, gives you more information or smart grouping where it takes all the elements and puts them in a different kind of view here. Let's just do navigation cards. Keep it on developer mode. So first thing is it gives you a Guild score, just say, score you can use over time to see if it's getting better or worse, shows a screenshot. You can actually click into Zoom. And I'll show you the site that was scanned. Show you how many critical errors, how many serious issues, how many total issues. What I think is cool is so it has a critical thing and it explains what it means and why it matters. It kind of breaks things down into plain English. Also, who fixes it? A lot of times people don't know, all right, I found the issue, but who fixes that? It tells you, web developer, designer, and testers. Also how to fix, gives you some suggestions on how to fix. And if you're using a particular tool like Cypress or say Selenium, it'll give you the code to use to actually put into your particular framework to actually fix that or check that particular issue. It also links out to what the WCAG issue is. And what I really like, you can actually highlight on the screen where the issue is located. As you can see, it highlights these particular icons, these frames. So it'll show you where the issue is as well visually which I think is really helpful because a lot of times you may not know. Like I said, this is a great way to just do a simple scan right off the bat, see how you're doing it and actually track it over time using the score, just to gage if it's getting better or worse for your team. If you have any issues with this, like I said this is in beta, just give me some feedback. I would love to know how you rate it, if that was helpful and what I could do better at and what would make it better.