CPACC common mistakes
CPACC · Understand the traps and how to avoid them.
Treating the medical model and the social model as simple opposites and selecting 'social model' for every question about disability, even when the scenario describes impairment-related limitations that the social model also acknowledges (e.g., pain, fatigue, or health needs).
Candidates memorize a one-line contrast ('medical = bad, social = good') and stop there. The exam tests nuanced application: the social model distinguishes impairment from disability but does not deny impairment; many items describe a mix of individual and environmental factors.
What to do instead
For each scenario, identify what is being attributed to the person (impairment/health condition) versus the environment (barriers, attitudes, design). Choose the model that matches the attribution in the stem, not a default preference. Review the ICF biopsychosocial model as a bridge, and practice classifying short scenarios by which factor is emphasized.
Confusing person-first language with identity-first language and applying one as a universal rule, rather than matching the preference stated or implied for the group or individual in the item.
Training materials often present person-first language as 'the correct' approach, but many Deaf, autistic, and blind communities prefer identity-first language. Items test whether the candidate recognizes community preference and individual self-identification.
What to do instead
Learn which communities commonly prefer identity-first language (e.g., Deaf, autistic, blind) and which often prefer person-first, while remembering that individual preference overrides group tendency. In questions, look for explicit preference cues in the stem and follow them.
Equating accessibility with screen-reader support only, and overlooking cognitive, motor, auditory, vestibular, and situational dimensions when selecting the most appropriate accommodation or design approach.
Screen readers are the most visible assistive technology, so candidates over-anchor on them. Exam items frequently describe low vision, motor impairment, cognitive load, or temporary/situational limitations where screen-reader fixes are irrelevant or insufficient.
What to do instead
Before answering, list the functional needs in the scenario (vision, hearing, mobility, cognition, speech, seizure, etc.) and match the solution to the need. Practice mapping common barriers to the full range of assistive technologies and design strategies, not just screen readers.
Treating WCAG conformance levels as interchangeable and selecting 'AA' or 'AAA' as a blanket answer without checking which success criteria apply to the content type and which level the standard actually assigns.
Candidates remember 'AA is the usual target' and apply it indiscriminately. Many items hinge on specific success criteria (e.g., contrast ratios, captions, reflow) and their assigned levels, or on the distinction between minimum conformance and enhanced conformance.
What to do instead
Memorize the structure: Level A is the minimum, AA is the commonly required level in law and policy, AAA is enhanced and not required as a blanket standard. Learn the level of frequently tested criteria (e.g., 1.4.3 Contrast Minimum is AA at 4.5:1; 1.4.6 Contrast Enhanced is AAA at 7:1; 1.2.2 Captions is A). When an item asks for a level, verify the specific criterion rather than defaulting.
Mixing up the roles of WCAG, WAI-ARIA, and ATAG/UAAG, and choosing WAI-ARIA as the fix for content accessibility problems that actually require semantic HTML or authoring-tool support.
All three are W3C/WAI documents, and ARIA is widely discussed, so candidates reach for it as a universal solution. In reality, ARIA supplements but does not replace native semantics, and ATAG/UAAG govern authoring tools and user agents, not page content.
What to do instead
Build a one-line role card for each: WCAG = web content accessibility; WAI-ARIA = accessible rich internet applications, roles/states/properties for custom widgets; ATAG = authoring tools; UAAG = user agents/browsers. For content questions, prefer native HTML semantics first and treat ARIA as a supplement. Practice identifying which document governs the artifact named in the stem.
Applying the wrong law to the wrong jurisdiction or sector, for example citing the ADA for a private employer's web accessibility in the EU, or the European Accessibility Act for a U.S. federal agency.
The standards domain spans multiple jurisdictions and sectors (ADA, Section 508, Section 504, EU Web Accessibility Directive, European Accessibility Act, EN 301 549, CRPD, national laws). Candidates learn labels without the scope conditions that determine applicability.
What to do instead
Create a matrix of law, jurisdiction, covered entities, and key obligations. For each practice item, first identify the jurisdiction and the covered entity (public/private, employer/service provider/federal agency), then select the law. Pay special attention to the EU Web Accessibility Directive (public sector websites and mobile apps) versus the European Accessibility Act (a broad range of products and services).
Treating the ADA as a single uniform standard and missing the differences among Title I (employment), Title II (state and local government), and Title III (public accommodations), including which titles have specific web accessibility rules and which rely on general nondiscrimination principles.
The ADA is often summarized as 'the disability law,' so candidates apply it generically. Items test title-specific obligations, remedies, and the current status of web accessibility regulation under each title.
What to do instead
Memorize the three titles and their covered entities and obligations. Note that Title II has a specific web and mobile app accessibility rule (published 2024, with compliance timelines) while Title III web accessibility is addressed through general nondiscrimination and DOJ guidance rather than a standalone technical rule. Practice sorting scenarios by title before choosing an answer.
Confusing Section 508 (federal procurement and federal agencies) with Section 504 (recipients of federal financial assistance) and applying the wrong one to a hospital, university, or contractor scenario.
Both are amendments to the Rehabilitation Act and are frequently mentioned together. Candidates remember 'Section 508' as the accessibility law and overlook that 504 reaches any program receiving federal funds, including many private organizations.
What to do instead
Anchor each section to its trigger: Section 508 applies to federal agencies and to ICT procured by them (with the Revised 508 standards incorporating WCAG 2.0 AA); Section 504 applies to recipients of federal financial assistance. For scenarios involving federal funding, check 504 first; for federal procurement or federal websites, check 508.
Choosing 'provide an accommodation' as the default answer when the better answer is to remove the barrier through universal design or proactive accessibility, or vice versa when an individual accommodation is genuinely required.
Candidates learn accommodations as the core response to disability and over-apply them. Many items test the distinction between reactive individual accommodation and proactive systemic accessibility, and the principle that universal design reduces the need for accommodations.
What to do instead
Ask whether the barrier is environmental and can be designed out for everyone (universal design/proactive fix) or is an individual need that design cannot fully address (accommodation). Prefer the most systemic, inclusive solution that meets the need, and reserve accommodations for residual individual requirements.
Treating an accessibility program as a one-time remediation project and ignoring governance elements such as policy ownership, procurement controls, training, testing cadence, feedback channels, and metrics when answering organizational practice items.
Candidates focus on technical fixes and underestimate the management domain. Exam items often describe a mature program and ask which element is missing or which practice sustains accessibility over time.
What to do instead
Learn the components of a sustainable accessibility program: executive sponsorship and policy, roles and responsibilities, procurement and vendor requirements, design and development standards, testing (automated plus manual plus user testing), training, an accessible feedback mechanism, and tracking/metrics. When an item asks for the best next step, choose the governance or process element that institutionalizes the fix rather than a one-off technical patch.