Problem
If a long breadcrumb in Claro is on multiple lines, it does not meet the WCAG minimum target size of 24px by 24px.
The Lighthouse error links to Dequeue University's target-size rule, for which the description is:
Touch targets must be at least 24 by 24 CSS pixels in size. Size is computed by taking the largest unobscured area of the touch target. If the size of the target is insufficient, then it must be possible to draw a virtual circle centered on the target with a diameter of 24 pixels that does not intersect any other targets, nor any of the circles on other undersized targets.
The corresponding WCAG rule is Success Criterion 2.5.8 Target Size (Minimum).
Steps to reproduce
- Install standard profile.
- Log in as admin.
- Go to
/admin/config/content/formats/manage/basic_html. - Run a Lighthouse accessibility audit for mobile.
The attached Lighthouse HTML export shows the error.
Proposed resolution
Change the CSS to enforce a minimum height of 1.5rem (24px) for the elements. The items are expected to always be >= 24px wide, so a minimum width spec should not be necessary.
Before changes

After changes


Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Issue fork drupal-3223147
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
lauriiiComment #4
ckrinaGood idea. Let's be sure the changes are not using px, but rems.
Comment #6
lauriiiMarking as major but not adding as a stable blocker for Claro since this also happens in Seven.
Comment #9
kostyashupenkoComment #10
kristen polThanks for the MR.
1. Patch still applies to both 9.3 and 9.4.
2. Code changes match the proposed resolution except that
line-height: 3rem;is in thecssfile andline-height: 48px;in thepcss. The proposed resolution is not consistent withpxvsrembetween the two classes.3. Assumes that no tests will be added for this since it's a visual thing that may be hard to test.
4. Tagging for steps to reproduce, testing, before/after screenshots, and issue summary update.
Comment #13
smustgrave commentedWas previously tagged for steps to reproduce, screenshots, and IS update
Comment #14
nikhil_110 commentedAddress #13
I have tried the steps to reproduce, screenshot and IS updated.
Comment #15
smustgrave commentedThis issue talks about how this is a lighthouse failure.
We probably will need a test case to show this was fixed.
Comment #16
shoshan commentedComment #17
shweta__sharma commentedI tried to replicate the issue but I am unable to replicate it. I followed the steps mentioned in the STR
Followed below mentioned steps -
How i can see the below breadcrumbs links mentioned in before screenshots?
Comment #19
saurav-drupal-dev commentedunable to push so created patch for D11 please review
Comment #20
supriyak commentedHi,
I tried to check the issue with steps mentioned in issue description on Drupal 11, but unable to replicate the issue.
Below I have attached screenshots on desktop and mobile view. As, if the issue is not reproducible on latest version can we close this case?
I am moving this to Needs Review.
Thanks!
Comment #21
supriyak commentedComment #22
smustgrave commentedFixes should be in MRs vs patches.
Also the steps mention D9.5, has this been confirmed in 11.x?
Comment #24
supriyak commentedHi @smustgrave,
I have checked this issue on versions 9.4.0-dev, 10.0.12-dev, 11.x-dev, but it is not reproducible on my end. I have attached screenshots for your reference.




I have followed all the steps mentioned here.
Please let me know what should be the next step from my side.
Thank you!
Comment #25
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #26
vensiresComment #27
kentr commentedI am able to reproduce on
11.xwith different STR. I updated the IS and am attaching the HTML Lighthouse report.I think I can fashion a failing Nightwatch Axe test.
The Axe rule currently referenced by Lighthouse now specifies
24x24 pxinstead of48x48 px, but I didn't change that in the IS because I don't know the history.On a meta-level, in case it is a policy problem:
This issue is
WCAG 2.2 AA. A Nightwatch Axe-core test just for this issue will need to explicitly invokeWCAG 2.2 AA, because the existing automated Axe tests don't appear to runWCAG 2.2 AA. So, the standard for this test will differ from the rest unless all tests are updated.The Accessibility Coding Standards are unclear IMO on whether core / Drupal CMS are required to meet
WCAG 2.2 AA.Though the existing Axe tests still wouldn't have caught this for other reasons, in general they would catch some
target-sizeproblems if we started includingWCAG 2.2 AA.Comment #31
kentr commentedMR 11394 is against
11.xand includes a Nightwatch test.Based on discussion in #3491461: [meta] Some interface components don’t meet the minimum target size, I reduced the height of the elements to
1.5rem, which comes to24px.I am attaching new screenshots with the changes, as they are different than the previous version.
Tagging for https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html
Comment #32
kentr commentedComment #33
smustgrave commentedAfter applying the MR confirmed I'm getting the same results as the screenshots in the issue summary. Tested at various mobile widths and confirmed the breadcrumb__item always stayed at 24px.
Believe this one is good.
Comment #34
catchI think this could use review either from a Claro maintainer or an FEFM, I don't feel like my CSS is up to reviewing whether this covers all cases or not.
Comment #39
nod_Committed and pushed 72c39ca98ec to 11.x and dce32095c10 to 11.2.x and 0f3a62ab851 to 10.6.x and f0525143a35 to 10.5.x. Thanks!
Comment #44
nod_Comment #45
nod_