frontend-wcag-operable

name	frontend-wcag-operable
description	Use when writing front-end components that must meet WCAG 2.x operability criteria: keyboard navigation, focus management, timing, seizure prevention, and navigation patterns.

WCAG Operable Guidelines

• Make all functionality accessible via keyboard with visible focus indicators
• Avoid keyboard traps where focus cannot leave a component via standard navigation
• Provide mechanisms to extend, adjust, or disable time limits where present
• Avoid content that flashes more than three times per second (seizure trigger)
• Implement skip navigation links to bypass repeated content blocks
• Use descriptive page titles, headings, and link text that indicate purpose
• Ensure focus order matches the visual and logical sequence of information
• Support multiple ways to find content (search, site map, logical navigation)
• Allow pointer gestures to be accomplished with a single pointer without path-based gestures
• Implement pointer cancellation to prevent unintended activation of critical actions