-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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.
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
Make the X Close buttons target size larger #66277
Comments
Quickly looking at a few buttons instances in the codenase, it appears there's some room for some CSS clean-up. For example, the X close button of the tabs panel uses the gutenberg/packages/editor/src/components/sidebar/style.scss Lines 1 to 8 in 75e3366
|
This close button appears to have been changed to a small size by #61331. cc @WordPress/gutenberg-design |
I agree the buttons should be the same size, as should the spacing between them and the horizontal padding of their containers. This consistency would make alignment much simpler to achieve and in most cases the default meaning we can remove some ad hoc styling. |
Noting the modal dialog component X close button was changed in #65102 / #65131. Neither the issue nor the pull requests have any accessibility label of any considerations related to accessibility. The modal X close button used to be 36 pixels. The new sizing scheme provides 3 size varaints: 40, 32, and 24 pixels. The button was changed to 24 pixels for no other apparent reasons than alignment. The 32 pixels variant would have been better as the modal provides enough space tor a bigger button. Making it 24 pixels makes the target size unnecessarily smaller and only for visual purposes. I'll split the modal close button to a separate issue to not block this one. |
Description
See conversation on #63243
Recent changes in #61331 and other PRs standardized the size of various X Close buttons to the
small
variant, which is 24 by 24 pixels.While standardizing is good, unnecessarily reducing the target size isn't.
Whenever possible, given the constraints of the layout and containers where the buttons live, the target size should be as large as possible.
Additionally, the 24px size is inconsistent with other buttons that may be displayed close to the X button. A few examples where I used background colors to illustrate the inconsistency:
In the Styles panel header: 3 buttons use the
compact
size (32 pixels) and the X button uses thesmall
size (24 pixels):Similarly, in the Plugins panel, one button is
compact
and the X button issmall
:A good point was made on #63243 (comment) that these buttons should be horizontally aligned with other controls in the UI so that the right padding of the containers should be adjusted. In the screenshot below, observe that besides the inconsistent size, the container right padding is inconsistent as well:
Additionally: all the other X close buttons e.g. within modal dialogs should be at least
compact
(32 by 32 pixels).It is worth reminding that the WCAG Target Size (Minimum) requires a size of at least 24 by 24 CSS pixels. That's the minimum though. There's no reason not to make these buttons bigger, when possible. The editor should aim to provide the best possible experience and not be limited to meet the minimum requirements.
Step-by-step reproduction instructions
small
.compact
, while the X close button issmall
.small
. Observe there is enough space to make itcompact
.one and observe the X close button is
small. Observe there is enough space to make it
compact`.Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Please confirm that you have tested with all plugins deactivated except Gutenberg.
The text was updated successfully, but these errors were encountered: