Skip to content

Clarify Dismissible paragraph in Understanding SC 1.4.13 #5030

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.

Sign up for GitHub

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

Open
venkatvemuri28 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Clarify Dismissible paragraph in Understanding SC 1.4.13 #5030

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2071e49
Clarify Dismissible wording in Understanding 1.4.13
venkatvemuri28 Mar 28, 2026
8b7ee12
Merge branch 'main' into issue-1409-dismissible-wording
venkatvemuri28 Apr 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion understanding/21/content-on-hover-or-focus.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ <h3>Dismissible</h3>
<li>Position the additional content so that it does not obscure any other content including the trigger, with the exception of white space and purely decorative content, such as a background graphic which provides no information.</li>
<li>Provide a mechanism to easily dismiss the additional content, such as by pressing Escape.</li>
</ol>
<p>For most triggers of relatively small size, it is desirable for both methods to be implemented. If the trigger is large, noticing the additional content may be of concern if it appears away from the trigger. In those cases, only the second method may be appropriate.</p>
<p>For most triggers, it is desirable for both methods to be implemented. If the trigger is large, positioning the additional content so it does not obscure the trigger may place that content further from the user's current pointer location, making it harder to notice. In those cases, only the second method may be appropriate.</p>
<p>The success criterion allows for input error messages to persist as there are cases that require attention, explicit confirmation or remedial action.</p>
</section>
<section>
Expand Down
Loading