You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$default-block-margin: 28px; // This value provides a consistent, contiguous spacing between blocks.
$text-editor-font-size: 15px;
$editor-line-height: 1.8;
$mobile-text-min-font-size: 16px; // Any font size below 16px will cause Mobile Safari to "zoom in".
.
This approach to defining font sizes might not fully support or comply with accessibility standards, particularly those outlined by the 1.4.4: Resize Text | WAI | W3C regarding text resizing.
Note that this issue is distinct from Fluid font sizes in WordPress 6.1, which focuses on font sizes on user sites. This issue aims to address the font sizes used within the Gutenberg editor's UI itself.
Looks like ^ this merge resolves this issue - is that right @okmttdhr
While this PR: Automattic/wp-calypso#87693 does introduce some improvements to font size scalability on WordPress.com, it doesn't address the issue I raised.
The concern I'm highlighting is how font sizes are defined for WordPress UI, as shown in the variable definitions here: packages/base-styles/_variables.scss. The issue is with static px values for font sizes, which could limit a11y.
What problem does this address?
Currently, font variables within the Gutenberg project are defined using px units, as seen in the file at
gutenberg/packages/base-styles/_variables.scss
Lines 11 to 23 in a4dd8d6
This approach to defining font sizes might not fully support or comply with accessibility standards, particularly those outlined by the 1.4.4: Resize Text | WAI | W3C regarding text resizing.
Note that this issue is distinct from Fluid font sizes in WordPress 6.1, which focuses on font sizes on user sites. This issue aims to address the font sizes used within the Gutenberg editor's UI itself.
What is your proposed solution?
The text was updated successfully, but these errors were encountered: