-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] Add focus indicator style guidance #2132
Comments
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 new subsections:
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! Thoughts, @markcaron or @coreyvickery ? |
I would think that we're wanting to document the focus states in 2 ways:
There may be some repetition, but I think that's ok. We can also cross-link the sections where appropriate. Note: @hellogreg, when you messaged me in chat, I arrived at the |
Thanks, @markcaron ! I do like the idea of an |
@hellogreg @markcaron I agree with everything. Can we also add a subnavigation to the |
@coreyvickery I think that's a great idea. |
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: