CPACC Accessibility Auditing and Testing 5 — Questions and Answers
Question 1: Which document type is produced as the formal output of an accessibility audit to communicate findings to stakeholders?
- Conformance report (VPAT or ACR) (Correct answer)
- WCAG checklist spreadsheet only
- Screen reader session recording
- Browser console error log
Correct answer: Conformance report (VPAT or ACR)
A Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR) is the standard formal document used to communicate audit findings.
Question 2: A developer adds role='button' to a div but does not add tabindex='0'. What accessibility problem remains?
- The element lacks a visible label
- The element is not focusable via keyboard (Correct answer)
- The element will be ignored by screen readers
- The element violates color contrast requirements
Correct answer: The element is not focusable via keyboard
Without tabindex='0', a div with role='button' cannot receive keyboard focus, making it inaccessible to keyboard-only users.
Question 3: During testing with a screen reader, a tester encounters a table where data cells are not associated with headers. Which WCAG criterion is violated?
- 1.4.1 Use of Color
- 1.3.1 Info and Relationships (Correct answer)
- 2.4.6 Headings and Labels
- 4.1.1 Parsing
Correct answer: 1.3.1 Info and Relationships
WCAG 1.3.1 requires that information and relationships conveyed through presentation (like table headers) be programmatically determinable.
Question 4: An accessibility tester verifies that a single-page application updates the page title when navigating between views. Which user need does this address?
- Color contrast compliance
- Screen reader users understanding their current location (Correct answer)
- Keyboard trap prevention
- Adequate text size for low vision users
Correct answer: Screen reader users understanding their current location
Updating the page title on SPA navigation helps screen reader users understand which view or page they are currently on without examining all content.
Question 5: What does 'testing in context' mean in accessibility auditing?
- Testing only on the operating system the developer used
- Evaluating pages using actual assistive technologies in realistic user scenarios (Correct answer)
- Running automated scans on the production server only
- Testing exclusively with JAWS on Windows
Correct answer: Evaluating pages using actual assistive technologies in realistic user scenarios
Testing in context means using real assistive technologies in realistic user workflows to identify barriers actual users would encounter.
Question 6: A tester finds that an icon button has no accessible name. Which technique would BEST resolve this?
- Add a tooltip that appears on hover only
- Add aria-label with a descriptive text to the button (Correct answer)
- Increase the icon size to 44x44 pixels
- Add role='img' to the icon element
Correct answer: Add aria-label with a descriptive text to the button
Adding aria-label to the button element provides an accessible name that screen readers can announce, satisfying WCAG 4.1.2 Name, Role, Value.
Question 7: Which test best verifies that a website meets WCAG 2.4.7 Focus Visible?
- Check that all interactive elements have an aria-label
- Tab through the page and confirm a visible indicator appears on each focused element (Correct answer)
- Verify the site passes an automated scan with no errors
- Confirm all buttons use the default browser outline style
Correct answer: Tab through the page and confirm a visible indicator appears on each focused element
Manually tabbing through the page and visually confirming each focused element displays a visible focus indicator is the correct way to test 2.4.7.
CPACC Accessibility Auditing and Testing 5
Which document type is produced as the formal output of an accessibility audit to communicate findings to stakeholders?