Skip to content

Incorporate suggestions from restoration of Target Size (Enhanced) Understanding #4589

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
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Incorporate suggestions from restoration of Target Size (Enhanced) Understanding #4589

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9deba97
update target inline definition
filippo-zorzi Aug 28, 2025
829632d
remove example 3, anchor link
filippo-zorzi Aug 28, 2025
66915db
change intent writing
filippo-zorzi Aug 28, 2025
f1b71bb
Merge branch 'main' into filippo-zorzi-target-size-enhanced-improvements
patrickhlauke Aug 29, 2025
57e22b0
Merge branch 'main' into filippo-zorzi-target-size-enhanced-improvements
patrickhlauke Sep 5, 2025
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
18 changes: 8 additions & 10 deletions understanding/21/target-size-enhanced.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,19 +17,19 @@ <h2>In brief</h2>
</section>
<section id="intent">
<h2>Intent</h2>
<p>The intent of this success criterion is to help users who may have trouble activating a small target because of hand tremors, limited dexterity or other reasons. If the target is too small, it may be difficult to aim at the target. Mice and similar pointing devices can be hard to use for these users, and a larger target will help them greatly in having positive outcomes on the web page.</p>
<p>The intent of this success criterion is to help users who may have trouble activating a small target because of hand tremors, limited dexterity, or other reasons. If the target is too small, it may be difficult to aim at the target. Mice and similar pointing devices can be hard to use for these users, and a larger target will help them greatly in having positive outcomes on the web page.</p>
<p>Touch is particularly problematic as it is an input mechanism with coarse precision. Users lack the same level of fine control as on inputs such as a mouse or stylus. A finger is larger than a mouse pointer, and generally obstructs the user's view of the precise location on the screen that is being touched/activated.</p>
<p>The issue can be further complicated for responsive/mobile sites which need to accommodate different types of fine and coarse inputs (e.g. a site that can be accessed both on a traditional desktop/laptop with a mouse, as well as on a tablet or mobile phone with a touch screen).</p>
<p>The issue can be further complicated for responsive and mobile sites that need to accommodate different types of fine and coarse inputs (for example, a site that can be accessed on a traditional desktop or laptop with a mouse, as well as on a tablet or mobile phone with a touch screen).</p>
<p>While this criterion defines a minimum target size, it is recommended that larger sizes are used to reduce the possibility of unintentional actions. This is particularly relevant if any of the following are true:</p>
<ul>
<li>the control is used frequently;</li>
<li>the result of the interaction cannot be easily undone;</li>
<li>the control is positioned where it will be difficult to reach, or is near the edge of the screen;</li>
<li>the control is part of a sequential task.</li>
</ul>
<p>The targets on a screen can have different purposes and uses, and this success criterion specifies how each is to be handled.</p>
<p>The targets on a screen can have different purposes and uses, and this Success Criterion specifies how each is to be handled.</p>
<p><strong>Equivalent targets:</strong> If there is more than one target on a screen that performs the same action, only one of the targets need to meet the target size of 44 by 44 CSS pixels.</p>
<p><strong>Inline:</strong> Content displayed can often be reflowed based on the screen width available. This is known as responsive design and makes it easier to read since you do not need to scroll both horizontally and vertically. In reflowed content, the targets can appear anywhere on a line and can change position based on the width of the available screen. Since targets can appear anywhere on the line, the size cannot be larger than the available text and spacing between the sentences or paragraphs, otherwise the targets could overlap. It is for this reason targets which are contained within one or more sentences are excluded from the target size requirements.</p>
<p><strong>Inline:</strong> Content displayed is often designed to reflow based on the screen width available. This is known as responsive design and makes it easier to read since you do not need to scroll both horizontally and vertically. In reflowed content, the targets can appear anywhere on a line and can change position based on the width of the available screen. Since targets can appear anywhere on the line, the size cannot be larger than the available text and spacing between the sentences or paragraphs, otherwise the targets could overlap. It is for this reason targets which are contained within one or more sentences are excluded from the target size requirements.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

while this is original text, i'm not a super-fan of the awkward "Content displayed". wonder if just dropping "displayed" would make this sound less clunky. or, if it must retain the distinction (so it's not confused with audio content, for instance), maybe changing it to "Visible content" or even at the very least "Displayed content"

<div class="note">
<p>If the target is the full sentence and the sentence is not in a block of text, then the target needs to be at least 44 by 44 CSS pixels.</p>
</div>
Expand Down Expand Up @@ -58,16 +58,14 @@ <h2>Examples</h2>
<dd>Three buttons are on-screen and the touch target area of each button is 44 by 44 CSS pixels.</dd>
<dt>Example 2: Equivalent target</dt>
<dd>Multiple targets are provided on the page that perform the same function. One of the targets is 44 by 44 CSS pixels. The other targets do not have a minimum touch target of 44 by 44 CSS pixels.</dd>
<dt>Example 3: Anchor Link</dt>
<dd>The target is an in-page link and the target is less than 44 by 44 CSS pixels.</dd>
<dt>Example 4: Text Link in a paragraph</dt>
<dt>Example 3: Text Link in a paragraph</dt>
<dd>Links within a paragraph of text have varying touch target dimensions. Links within
paragraphs of text do no need to meet the 44 by 44 CSS pixels requirements.</dd>
<dt>Example 5: Text Link in a sentence</dt>
<dt>Example 4: Text Link in a sentence</dt>
<dd>A text link that is in a sentence is excluded and does not need to meet the 44 by 44 CSS pixel requirement. If the text link is the full sentence, then the text link target touch area does need to meet the 44 by 44 CSS pixels.</dd>
<dt>Example 6: Footnote</dt>
<dt>Example 5: Footnote</dt>
<dd>A footnote link at the end of a sentence does not need to meet the 44 by 44 CSS pixels requirements. The footnote at the end of the sentence is considered to be part of the sentence.</dd>
<dt>Example 7: Help icon</dt>
<dt>Example 6: Help icon</dt>
<dd>A help icon within or at the end of a sentence does not need to meet the 44 by 44 CSS pixels requirements. The icon at the end of the sentence is considered to be part of the sentence.</dd>
</dl>
</section>
Expand Down