Suggested additional note for focus-not-obscured (AAA), tweak AA note #4403
Conversation
AAA version of the note that was added for AA in #4104
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@dbjorge you mentioned in our call that the quote bit needs to be updated "no part of the component is hidden" ... but that is the wording used in the AAA version https://www.w3.org/TR/WCAG22/#focus-not-obscured-enhanced ... so i think we're good with this? |
@@ -23,6 +23,7 @@ Intent of Focus Not Obscured (Enhanced) |
|||
|
Typical types of content that can overlap focused items are sticky footers, sticky headers, and non-modal dialogs. As a user tabs through the page, these layers of content can hide the item receiving focus, along with its focus indicator. |
|||
|
A notification implemented as sticky content, such as a cookie banner, will fail this success criterion if it partially covers a component receiving focus. Ways of passing include making the banner modal so the user has to dismiss the banner before navigating through the page, or using scroll padding so the banner does not overlap other content. Notifications that do not require user action could also meet this criterion by closing on loss of focus. |
|||
|
Another form of obscuring can occur where light boxes or other semi-opaque effects overlap the item with focus. This form of obscuring is not in scope for this success criterion. While less than 100 percent opacity is not causing the component to be |
|||
|
This criterion evaluates the focused component, rather than the focus indicator. The component itself does not include the focus indicator when checking that "no part of the component is hidden" - unless the focus indicator is inside the component, or focus is indicated by a change to the component itself. Although users benefit from both the component and the focus indicator (if external to the component) not being obscured when tracking the focus, for the purposes of this criterion only checking the component provides a clearer metric. However, if the focus indicator is obscured, it would likely fail 2.4.7 Focus Visible. |
|||
There was a problem hiding this comment.
Slight wording changes to improve readability and to match the wording to the context of the AAA requirement.
| <p class="note">This criterion evaluates the focused <em>componentem>, rather than the focus <em>indicatorem>. The component itself does not include the focus indicator when checking that "no part of the component is hidden" - unless the focus indicator is inside the component, or focus is indicated by a change to the component itself. Although users benefit from both the component and the focus indicator (if external to the component) not being obscured when tracking the focus, for the purposes of this criterion only checking the component provides a clearer metric. However, if the focus indicator is obscured, it would likely fail <a href="focus-visible">2.4.7 Focus Visiblea>.p> | |
| <p class="note">This criterion evaluates the focused <em>componentem>, rather than the focus <em>indicatorem>. The component itself does not include the focus indicator when checking that "no part of the component is hidden" — unless the focus indicator is inside the component, or focus is indicated by a change to the component itself. Users benefit from both the component and the focus indicator (if external to the component) not being obscured when tracking the focus; however, for the purposes of this criterion, only checking the component provides a clearer metric. If the focus indicator is fully obscured, it would likely fail <a href="focus-visible">2.4.7 Focus Visiblea>.p> |
There was a problem hiding this comment.
I don't think it makes sense to change that here. It matches the wording we already agreed on and used in the AA note #4104 and doesn't need changing for the AAA
There was a problem hiding this comment.
If you don't think it's more readable with the changes, okay. But if you think the mild editorial tweaks improve readability, maybe we should upgrade the AA at the same time. I think we should definitely consider the final change for "fully", as this is only likely to cause a failure of 2.4.7 if the focus indicator is fully obscured, no?
There was a problem hiding this comment.
the AA note didn't include "fully" https://github.com/w3c/wcag/pull/4104/files so yes that would need to be patched there too to keep them in line.
There was a problem hiding this comment.
done the "fully" to both AA and AAA, tweaked the PR description accordingly
mbgower
added
Understanding
2.4.12 Focus Not Obscured (Enhanced)
Substantive
Editorial
and removed
Substantive
labels
patrickhlauke
changed the title
AAA version of the note that was added for AA in #4104
Includes a small tweak to the AA note as well regarding focus indicator not being fully obscured