Skip to content

Element in sequential focus order has visible focus [oj04fd] expectation allows common scenarios to pass even when failing #2368

@giacomo-petri

Description

@giacomo-petri

I understand that this rule is atomic, and passing it doesn't necessarily mean that rule 2.4.7 is also met. However, there are common scenarios where the focus indicator is invisible, yet the current rule still passes.

A typical example is a top navigation menu or toolbar, where each control uses outline: none when focused and triggers a fly-out menu to expand. This expansion changes the pixels on screen, so our rule considers it a pass. However, because outline: none removes the visible focus indicator, users can't tell which option is currently focused or which menu item has been expanded.

I also believe this rule currently lacks sufficient examples, so I've added several in #2369 PR.
Failed Example 3 illustrates the situation I mentioned earlier (even though the description is slightly different). I've marked it as a failure, even though (based on the current wording) it technically passes the rule's expectations.

The PR is currently in draft status, as I'd like to discuss these points with the group before making any changes.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions