A WCAG 2.2 checklist for SaaS web apps

• Every action can be done with the keyboard alone (Tab, Enter, Space, arrow keys)
• No keyboard traps: you can always move focus out of a component
• Custom widgets (date pickers, dropdowns, menus) follow ARIA patterns
• Focus order follows the visual order

• Focus is always visible (2.4.7)
• Focused elements are not hidden behind sticky headers or footers (2.4.11, new in 2.2)
• Dialogs move focus in and return it when closed

• Every field has a visible label connected to the input
• Errors are shown in text, not only by colour, and linked to the field (3.3.1)
• Error messages say how to fix the problem (3.3.3)
• Users don't have to re-enter information they already gave (3.3.7, new in 2.2)
• Login doesn't rely on memory tests or block password managers (3.3.8, new in 2.2)

• Text contrast at least 4.5:1, large text 3:1 (1.4.3)
• Input borders, icons and focus indicators at least 3:1 (1.4.11)
• Content reflows at 320 px wide without horizontal scrolling (1.4.10)
• Text can be zoomed to 200% without loss of content
• Click targets at least 24 × 24 px or well spaced (2.5.8, new in 2.2)

• Buttons and links have meaningful names, including icon-only buttons
• Tables use real table markup with header cells
• Status messages (saved, sent, errors) are announced without moving focus (4.1.3)
• Charts have a text alternative or a data table

Run an automated scanner such as axe on key pages first; it finds roughly a third of issues. Then test each key task with the keyboard only, with a screen reader (NVDA on Windows, VoiceOver on macOS and iOS) and at 400% zoom. Fix shared components first: one fixed date picker can resolve dozens of issues across the app.