When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. Works well When I move focus to items, I can see them all. (a sticky footer) When I move focus to items, some are hidden behind the banner and I can't see them. Persona example - a reporter with repetitive stress injury who uses speech recognition software: Problem This page has a big banner that's always across the bottom. Why it’s important People who can't use a mouse need to see what has keyboard focus. In brief: What to do Ensure when an item gets keyboard focus, it is at least partially visible. Provide ways to help users navigate, find content, and determine where they are. WCAG 2.2 includes Notes about different languages more information is in WCAG 2 FAQ, internationalization. More information is in WCAG 2 FAQ, 4.1.1 Parsing. The 2.0 and 2.1 success criteria are essentially the same in 2.2, with one exception: 4.1.1 Parsing is obsolete and removed from WCAG 2.2. WCAG 2.2 provides 9 additional success criteria since WCAG 2.1. WCAG 2.2 was published as a “W3C Recommendation” web standard on 5 October 2023. 3.3.9 Accessible Authentication (Enhanced) (AAA)įor an introduction to Web Content Accessibility Guidelines (WCAG) and more about versions 2.0, 2.1, and 2.2, see the WCAG Overview.3.3.8 Accessible Authentication (Minimum) (AA).2.4.12 Focus Not Obscured (Enhanced) (AAA).2.4.11 Focus Not Obscured (Minimum) (AA).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |