"Familiar with WCAG" is the resume equivalent of white noise. Every recruiter has read it a thousand times, on a thousand other resumes, and it tells them absolutely nothing about what you can actually do. It doesn't say what you fixed, how you fixed it, or whether you would recognize a real accessibility failure if it was sitting right in front of you.
Recruiters and hiring managers skim. A line like that gets a mental shrug and moves on. But one specific line, naming a real criterion and a real outcome, stops the scroll. Here is how to rewrite that one bullet point so it survives the first pass and actually gets you the interview.
The Stat: The International Association of Accessibility Professionals (IAAP) offers three real, named credentials - CPACC (foundational, no coding required), WAS (technical, code-focused), and CPWA (awarded for holding both) - giving candidates a specific, verifiable credential to list instead of a vague self-assessment. (Source: International Association of Accessibility Professionals)
Why "accessible" is a red flag word, not a green one
Here's the uncomfortable truth: the word "accessible" on its own has become a filler word, like "detail-oriented" or "team player." Hiring managers who actually care about accessibility (and there are more of them every year, as legal and reputational pressure builds) have learned to distrust it. A bullet that says "built accessible interfaces" with nothing else could mean the candidate ran an automated scanner once, or it could mean they genuinely understand assistive technology. There's no way to tell, so the reader defaults to skepticism.
Compare that to a bullet that names a real WCAG success criterion. "Familiar with accessibility" is a claim about yourself. "Resolved 1.4.3 Contrast (Minimum) failures across primary buttons" is a claim about a specific, checkable piece of work. A hiring manager who knows accessibility can verify that claim in their head instantly. One who doesn't know accessibility will still register that you're speaking a precise, technical language, which reads as competence even before they understand the details.
This is the same shift we noticed after we read what actually stood out across 100 portfolios we reviewed: specificity beats polish. A portfolio (or a resume) that names the exact problem and the exact fix consistently outperforms one that just claims good intentions.
Turn vague claims into checkable ones
The fix is mechanical once you see the pattern. Take whatever vague accessibility line is currently sitting on your resume and ask three questions: What was actually broken? What criterion does that map to? What changed as a result? Here's how that plays out for the phrases we see most often.
| Vague phrase | Specific replacement | Why it works |
|---|---|---|
| "Familiar with accessibility" | "Resolved WCAG 2.1.1 Keyboard failures in a modal component that was previously mouse-only" | Names an exact, verifiable criterion instead of a vague self-rating |
| "Accessibility background" | "Fixed 1.4.3 Contrast (Minimum) violations across a checkout flow's primary buttons" | Ties the claim to a component and a measurable visual outcome |
| "Worked on accessible design" | "Added accessible names per 4.1.2 Name, Role, Value to custom form controls" | Shows understanding of assistive technology, not just visual styling |
Notice that each specific version does something the vague version can't: it survives a follow-up question. If an interviewer asks "tell me more about that," the vague bullet has nowhere to go. The specific one hands you a story you already know how to tell, because you lived it.
If you don't yet have a real fix to cite, that's fixable before your next application, not after. Run a component you've built, or one from a public site, through a real accessibility check and run a real fix through our free tools so you have a specific result to cite. It takes less time than rewriting your cover letter, and it gives you an honest, current example instead of a recycled one from a bootcamp project two years ago.
Use a credential to back up the claim, not replace it
Specific bullet points do most of the work, but a named credential adds a layer of proof a recruiter doesn't have to take on faith. This is where a lot of people either skip a real opportunity or reach for something vaguer than it needs to be, like "accessibility certified" without saying by whom.
There are exactly three credentials worth naming, and each signals something different:
- CPACC (Certified Professional in Accessible Core Competencies) - foundational, no coding required. Good for designers, product managers, content strategists, and QA who need to show they understand accessibility principles and law, not implementation.
- WAS (Web Accessibility Specialist) - technical and code-focused. This is the one to list if you're a front-end or full-stack developer who wants to prove you can actually implement fixes, not just identify them.
- CPWA (Certified Professional in Web Accessibility) - awarded for holding both CPACC and WAS. The strongest single line you can put on a resume if you've done the work to earn it.
All three come from the same body, so there's no ambiguity about legitimacy the way there can be with a one-off online course badge. You can read the details directly on IAAP's official certification overview before deciding which one matches where you are in your career. If you're not certified yet, that's fine, don't invent a credential. A specific, honest bullet point about real work beats a vague claim to a title you don't hold.
The five-second scan test
Before you save your resume, run this test: cover the rest of the page and read only your accessibility line in isolation. Ask whether a stranger could answer three questions from that one line alone: what did you actually do, what standard does it relate to, and what changed because of it. If the answer to any of those is no, it's still too vague.
A resume line that passes that test looks something like: "Fixed 12 WCAG 2.2 AA contrast and keyboard-trap failures across a checkout flow, reducing open issues to zero." That's not a claim about your character or your general familiarity with a topic. It's a claim about work you did, described precisely enough that anyone who knows the space can evaluate it in the time it takes to read one sentence, which is often all the time you get.
Match the specificity to the role, not just the skill
The same principle applies differently depending on what you actually do day to day, and it's worth tailoring your bullet rather than reusing one generic line across every application.
If you're a developer, lean into the technical criterion and the mechanism of the fix. Naming the exact success criterion, like WCAG 2.1.1 Keyboard, plus the component you touched, tells another engineer you know where accessibility bugs actually live in code, not just in a checklist.
If you're a designer, focus on the decision you made and the constraint you were solving for. "Redesigned form error states to meet 1.4.3 Contrast (Minimum) without losing the brand's color palette" shows you can hold two requirements at once, which is a much stronger signal than "designed with accessibility in mind."
If you're a product manager or QA lead, your strongest bullet is often about process: how you got a criterion tracked, tested, and closed across a team, not just how you personally implemented it. "Introduced a 4.1.2 Name, Role, Value check into the QA regression suite, catching failures before release" proves you can build a repeatable system, which is exactly what a hiring manager wants from someone in that seat.
In every version, the pattern holds: name the criterion, name the artifact, name the outcome. Swap the verb and the seniority level to match your actual role, but never drop back into the vague, unfalsifiable version just because it's easier to write.
Before you send it
If you want to practice naming a real fix before you write your next bullet point, our free tools are the fastest way to generate one you can actually stand behind. And if you'd rather talk it through with a real person, especially if you're weighing which credential fits your career path, the team at experts@wcag.world is happy to help you think it through, no pitch required.