You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because we currently have so many disparate keyboard focus styles across our site system (dashed/dotted/solid/inset outlines, background highlights, text color changes, etc.), we're standardizing these indicators to align with WCAG 2.2's recommendation:
Solid, offset outlines of at least 2px with at least 3:1 background/adjacent contrast
We need to craft some verbiage, add some relevant imagery, find a logical home for this at ux.redhat.com, and get the word out to our designers and engineers.
We've already got some documentation on this topic strewn across the site (e.g. the CTA Styles page), some of which we can consolidate for this issue.
I'm working on an initial draft of the text for this now. But we also need to decide where this content will live.
There is currently a Focus section on the Accessibility > Design page. We could put this new content in a subsection under that section, and put the existing content in their own subsections:
Design page
Focus section
Focus indicator styles (new subsection and content)
Focus and context changes (new subsection heading for existing content)
Focus traps (new subsection heading for existing content)
Or we could put it somewhere in the Foundations area of the site (either on an existing page or a new Interactions page), to make it clear that this is a design standard--and not just an accessibility topic. Or we could do something else altogether!
Because we currently have so many disparate keyboard focus styles across our site system (dashed/dotted/solid/inset outlines, background highlights, text color changes, etc.), we're standardizing these indicators to align with WCAG 2.2's recommendation:
Solid, offset outlines of at least 2px with at least 3:1 background/adjacent contrast
We need to craft some verbiage, add some relevant imagery, find a logical home for this at ux.redhat.com, and get the word out to our designers and engineers.
We've already got some documentation on this topic strewn across the site (e.g. the CTA Styles page), some of which we can consolidate for this issue.
References:
The text was updated successfully, but these errors were encountered: