Got my results two weeks ago and I'm officially CPACC certified. I started from basically zero knowledge of accessibility standards — I'm a UX designer by background so I understood usability but the formal disability frameworks and legal landscape were new territory. Twelve weeks felt tight at times but it was doable.
Weeks 1-4 were almost entirely spent on the disability and assistive technology domains. I'd underestimated how much there is to know about different disability types, the assistive technologies associated with each, and the barriers that exist across sensory, motor, cognitive, and speech categories. The IAAP Body of Knowledge is dense and I had to read most of it twice before it started sticking.
The accessibility standards and laws section was probably the most memorization-heavy part. WCAG 2.1 conformance levels, ADA Titles, Section 508, EN 301 549 — keeping all of those straight and knowing which applies in which context took me the longest. I made a comparison table for US vs EU vs international standards that I reviewed almost every day in the last three weeks. The exam had probably 15-18 questions that directly tested that kind of cross-framework knowledge.
My final score was 82%. The disability domain questions were the most straightforward because the content is fairly factual. The practical application questions — where you're evaluating whether something is accessible and why — were harder and that's where I'd focus more prep time if I were doing it over. Real-world scenario judgment is harder to study for than definitions.
How did you handle the assistive technology questions? That was my weakest area — I know the categories but the specific products and how they work with different browsers and screen readers felt like it could go really deep. I wasn't sure how granular the exam actually gets.
82% is a strong pass. I took it earlier this year and ended up right around 80. The scenario questions really are the tricky ones — knowing that something violates WCAG 1.4.3 is different from being able to identify why a specific design choice creates a problem for a low-vision user. Both get tested but the second type requires more applied thinking.
UX background is actually a decent foundation for this — you've already internalized a lot of the user-need thinking that underpins accessibility. I came from a development background and found the disability-side content harder to internalize because it felt further from my day-to-day work. The IAAP materials are thorough but they're written more for an advocacy context than a technical one.
The comparison table for legal frameworks is a great idea. I'm currently studying for the same exam and I've been struggling with keeping Section 508, EN 301 549, and AODA requirements separate in my head. They overlap enough that I keep conflating which provisions are specific to which framework.
Honestly I almost quit around week five. I'm a UX designer too and I kept telling myself the whole thing was just memorizing acronyms and legal citations that had nothing to do with real design work, and half the study material out there felt like it was written to sound important rather than to actually teach you anything. The disability models, the ADA versus WCAG versus Section 508 stuff, the international frameworks, it all blurred together and I convinced myself I wasn't a "certification person." What flipped it for me was just doing questions instead of rereading the Body of Knowledge for the tenth time. I started with these free cpacc basic question sets and getting things wrong actually made the concepts stick in a way passive reading never did.
So if you're sitting there thinking it's not clicking, keep going. The exam rewards understanding the why behind accessibility, not rote memorization, and once that clicked the legal and framework stuff stopped feeling random. I went in still half convinced I'd fail. I didn't. You probably won't either.
Quick update for anyone following along -- I'm at week 6 now and just hit 74% on my first full practice exam. Wasn't expecting that honestly, I thought I'd be lower given how shaky I felt on the AT terminology section going in. The disability classifications are finally clicking though, especially once I stopped trying to memorize them cold and just started connecting them to real users I've worked with as a designer.
Planning to sit the real exam in about five weeks, so early September. I've got two more timed mocks scheduled before then and I want to be consistently hitting 78-80% before I book the date. The legal stuff is still my weak spot -- CVAA and ADA Title III specifically -- so that's where most of my remaining study time is going. If you're earlier in your prep and struggling with the legal landscape, I'd say just keep pushing through it, it does start to make more sense after a while.
I almost didn't make it past week six, honestly. I was drowning in WCAG criteria and kept second-guessing whether I was studying the right things. What actually saved me was stepping back from the big guides and starting with something lower-stakes — I found some free cpacc basic questions that helped me figure out which concepts I actually had down versus which ones I just thought I understood. That gap was humbling.
Once I stopped trying to memorize everything and focused on the disability categories and how they map to barriers, it started clicking. The legal stuff took longest for me since I wasn't coming from that world at all. But if you're at week six feeling like you should quit, don't. The second half of prep went faster than the first once the framework made sense.
Just hit 79% on the cpacc/questions/general 2 practice set last night, which honestly surprised me because I bombed it pretty hard the first time I tried it two weeks ago. I'm planning to sit the real exam in about three weeks, so I'm in that final crunch mode now.
Congrats on passing, by the way. Your breakdown is super helpful because I'm also coming from a design background and the legal stuff wasn't clicking at first. It's starting to make more sense now that I've been drilling the WCAG criteria alongside it rather than treating them as separate topics.