Postponed (maintainer needs more info)
Project:
Claro
Version:
3.0.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
16 Jan 2019 at 21:10 UTC
Updated:
21 Sep 2026 at 13:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
modulist commentedComment #3
saschaeggi@modulist I've updated the documentation according to your bug report. there was no specification that S should be used for mobile use. These are just meant to be different icon sizes which can be used throughout the user interface.
So the doc now includes target areas to clarify this. Thanks for pointing out.
So e.g. the icons for the toolbar would have a target area of 24x24 but the icon itself would be 16x16.
Comment #4
fhaeberleCan this issue be closed? As I assume, the iconography size system was established without the target area included to have a flexible design approach. However, the icons are used with enough target spacing in a lot of components and we should asses this accessibility concern for each component separately (which is already be done for the majority of the components).
Comment #5
huzookaComment #7
rainbreaw commentedI haven't investigated this issue thoroughly in the actual theme, but want to make a clarifying note here:
The image or icon itself does not need to be 44x44 (WCAG and iOS) or 48x48 (Material), it is the touch area that must be this size. Touch area isn't simply referring to physical touch on a mobile device, but also cursor touch and accuracy on a computer, as well.
Even if material icons are 24x24, the CSS itself must include enough padding around the icon or target to create enough tappable space.
While this is a WCAG 2.1 Level AAA criterion, it is a serious issue for users with dexterity challenges. This can include a large number of individuals in both permanent and situational/temporal scenarios, such as aging, repetitive stress injury, being very young, certain medications, ticks, tremors, stereotypies/repetitive motions associated with developmental disorders, etc. For more on this, see WCAG 2.5.5 Target Size.
Comment #8
ckrinaWe defined this min target area:

Comment #16
quietone commentedThe Claro theme was approved for removal in #3576460: [policy, no patch] Deprecate and remove Claro.
This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
The deprecation work is in #3576668: [meta] Tasks to deprecate Claro and the removal work in #3584638: [meta] Tasks to remove the Claro theme.
Comment #17
smustgrave commentedClaro has moved to contrib
PMNMI as not sure what's needed here?