Latest / Software Testing with Fexingo: QA, Automation, and Reliable Software Engineering / How to Test Accessibility Without a Dedicated QA Team
Transcript
- Lucas: So last week I was helping a startup friend of mine, and they'd just gotten a legal notice about their app not being accessible. They're a team of twelve, no dedicated QA, let alone an accessibility engineer. Luna: That's the nightmare scenario. But honestly, it's becoming more common. The ADA lawsuits have been climbing for years now. Lucas: Right, and the thing is, they thought they were fine because they had a design system and some basic color contrast checks. But their user flows were a mess for keyboard-only users. Luna: So what did you tell them? Because I imagine you didn't just say 'hire an accessibility consultant' — that's not realistic for most small teams. Lucas: Exactly. I told them to start thinking about accessibility as a testing activity, not a design review. And that's what we're diving into today: how you bake accessibility into your existing QA process without a dedicated specialist. Luna: Good. Because the reality is, most teams are in the same boat. They know it's important, but they don't know where to start. Lucas: And the first place to start is with the standards. We're in 2026, and WCAG 2.2 has been around for a while now. It's the gold standard. And the key is to not treat it as a checklist of every single criterion, but to focus on the high-impact ones that catch most issues. Luna: So which criteria are the big ones? Like, what's going to catch the most problems for the average web app? Lucas: I'd say keyboard accessibility is number one. If a user can't tab through your site and trigger everything with the enter key, nothing else matters. That's also one of the easiest things to test manually — just unplug your mouse. Literally. Luna: That's a great first test. And it's surprising how many issues you find. I'd also add color contrast, because that's something automated tools are actually pretty good at catching. Lucas: Right. And that brings us to the tools. There are two pieces here: automated checks and manual checks. Automated tools like axe-core can be integrated straight into your CI pipeline. You add it to your test suite, and it catches maybe thirty to forty percent of issues. Luna: So it's not a silver bullet, but it's a solid safety net. And it's free, right? Lucas: Free and open source. The axe-core library is what powers the Lighthouse accessibility audits in Chrome DevTools. So you've already got it in your toolkit. The trick is making it part of your test runs, not a manual step you remember sometimes. Luna: And what about the manual side? Because automated tools miss things like screen reader flow or focus order. Lucas: Manual testing is where you catch the real user experience. But you don't need a dedicated tester for that. You can have a rotating 'accessibility buddy' on each sprint — someone who spends thirty minutes doing a guided pass with a screen reader and keyboard only. Luna: Rotating buddies sounds smart. It spreads the knowledge and keeps it from becoming one person's burden. But how do you make sure they actually know what to do? You can't just say 'go test accessibility.' Lucas: You give them a short checklist. I'm a big fan of the 'Accessibility Acceptance Criteria' approach. For each user story, you add three or four specific criteria: 'Page can be fully operated with keyboard,' 'All images have meaningful alt text,' 'Form inputs have associated labels.' Then the buddy tests against those. Luna: That's concrete. And it ties accessibility to the definition of done. If it's not in the acceptance criteria, it tends to get forgotten. Lucas: Exactly. And one more tip: don't wait until the end of the sprint. Start testing accessibility as soon as the feature is in a testable state. Catching a missing label during development is way cheaper than fixing it after release. Luna: So let's talk about the legal angle a bit more. Because that's often the trigger, like with your friend. What's the actual risk for a small company? Lucas: The risk is real. In the U.S., the Department of Justice has been clear that websites are places of public accommodation under the ADA. And there's been a steady drumbeat of lawsuits, especially against e-commerce sites. Fines and settlements can easily hit six figures, not to mention legal fees. Luna: And it's not just the U.S. The European Accessibility Act is now in force across the EU. So if you sell to European customers, this applies to you too. Lucas: That's a good point. It's a global issue now. But I want to be careful here — accessibility isn't just about avoiding lawsuits. It's about product quality. When you fix accessibility issues, you often improve usability for everyone. Think of captions — they help people in noisy environments, not just people who are deaf or hard of hearing. Luna: Right, the curb-cut effect. Like how closed captions are used by millions of people with no hearing impairment. So advocating for accessibility is a business argument, not just a moral one. Lucas: Precisely. And that's why I like to frame it to teams as 'quality attribute,' not 'compliance checkbox.' When you treat it as a feature, you're more likely to design for it from the start. Luna: So we've talked about automated tools and manual checklists. Is there anything else that's often overlooked? Lucas: One thing I see missed a lot is testing with actual assistive technology. Screen readers like VoiceOver on iOS or NVDA on Windows. You don't need to be an expert to run a basic pass. Just tab through and listen. Does it announce the page title? Does it announce form errors? That kind of thing. Luna: And you can practice on your own apps. It's a skill that builds over time. Lucas: Definitely. And there are also great community resources. The WebAIM million study found that over 96 percent of home pages have detectable WCAG failures. That's a staggering number. But it also means that if you do even basic checks, you'll be ahead of most of the web. Luna: That's a good stat to share with your team. It makes it feel like a real competitive advantage. Lucas: Yeah. And the ROI is there. Studies have shown that accessible sites convert better and have better SEO. But beyond that, it's just the right way to build software. You're including a huge segment of users who might otherwise be locked out. Luna: And because we're a listener-supported show, it's people like you who keep these conversations going. If you've found value in these episodes, you can support us at buy me a coffee dot com slash fexingo. It genuinely helps us keep producing this kind of content without ads. Lucas: Yeah, we're grateful for that. And we're not going anywhere — there's plenty more to cover, including a deep dive into automated visual regression testing in an upcoming episode. Luna: Oh, that's one I'm looking forward to. But before we wrap, let's bring it back to today. If you're a small team, what's your one actionable takeaway? Lucas: Pick one rule from WCAG 2.2 per sprint, add it to your acceptance criteria, and test for it. Start with keyboard navigation. That's the highest impact, lowest effort thing you can do. Luna: And automate what you can. Even if it's just running axe-core in your CI, it's better than nothing. Lucas: Exactly. Accessibility is a journey, not a destination. You don't need to fix everything overnight. But you need to start somewhere, and the sooner you start, the sooner you're building better software for everyone. Luna: Well said. And that's a wrap for today. Thanks for listening, and we'll catch you next time.