Checkpoint: Testing and Accessibility Culture

Question 1 of 5

• Check it manually against the lightest part of the photo behind the text, and add an overlay if it fails
• Ignore it, since it isn’t a violation
• Disable the color-contrast rule so the report stays clean

Question 2 of 5

• The field is read-only
• NVDA’s keyboard layout is broken and needs reinstalling
• NVDA is still in browse mode, where letters are navigation keys; press Enter or NVDA+Space to switch to focus mode
• The page has too many headings

Question 3 of 5

• Turn the scan off until there is time to fix everything
• Fix the violations in the order axe lists them
• Add aria-label attributes wherever axe complains
• Record the current violations as a baseline, fail CI only on new ones, and fix the baseline starting with the checkout flow

Question 4 of 5

• A decorative divider announced as “graphic”
• A keyboard trap inside the embedded payment form
• Footer link text that says “More”
• Grey footer text at 4.2:1 contrast

Question 5 of 5

• Ask for their Accessibility Conformance Report, and include the widget in your own keyboard and screen reader testing
• Accept the claim, since vendors are legally responsible for their widgets
• Exclude the widget from your audit scope to keep the report focused