The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: afercia <afercia@git.wordpress.org>
Co-authored-by: mirka <0mirka00@git.wordpress.org>
Co-authored-by: jameskoster <jameskoster@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Size Change: +5 B (0%)

Total Size: 1.82 MB

_{compressed-size-action}

Flaky tests detected in 2ca94dc.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11704107697
📝 Reported issues:

• [Flaky Test] submenu click on the arrow interactions #61884 in /test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js

the current size technically already meets WCAG AA.

That is the whole point of this PR. As explained in #66758 WordPress should not aim for just the mimimum technical compliance. Whenever possible, when there is enough space, the target size should be reasonably bigger than the minimum required of 24 pixels.

Aiming for only the minimum requirement is an approach that relegates accessibility to a remediation level, while WordPress should aim to provide the best experience for all users instead.

I tend to agree, there's adequate space to use a larger button, and not much justification for using the smallest variant imo.

Thanks @jameskoster for your feedback.
I'm not opposed to leave this PR available for testing for a few days so that anyone can test when they have a chance. On the other hand, it's a very little and self-contained change that could be easily reverted, if need be.
Merging now would expose the change to more eyes, which is always welcome to catch potential issues. Thanks.