WordPress.org

Make WordPress Core

Opened 17 months ago

Last modified 3 months ago

#34991 assigned feature request

Introduce a typographic measure for the admin screens

Reported by: afercia Owned by: afercia
Milestone: 4.8 Priority: normal
Severity: normal Version: 4.4
Component: Administration Keywords:
Focuses: ui, accessibility Cc:

Description

For optimal readability, lines of text shouldn't exceed a certain length. In typography, this is called measure and looking around for references you will find several (different) recommendations, starting from 45-50 characters per line till 90 or even more.

By the way, there's no such a thing as an absolute, perfect, number to fit all the different cases. It depends on many different factors, starting from the typeface used, its metrics, if it's a single column or multi-column layout etc.

That said, when a line of text is really, really, too long, then readability, usability, and accessibility, they're all seriously affected.

I'd like to encourage typography lovers and designers to start some discussion, research, and development with the long-term goal to improve typography in the admin screens. Trying to implement a measure could be a nice start.

Also, I'd like to propose to consider the introduction of a new "typography" focus tag for Trac.

In the screenshots below: a couple examples of some admin screens rendered on a large display with the browser's window maximized.

https://cldup.com/Lqn6W2CVsy.png

https://cldup.com/CV2JcdQI1w.png

Change History (8)

#1 follow-up: @michaelarestad
17 months ago

You mean like in Tools?

https://cldup.com/jQy9xf2q17.png

Note: this is NOT an ideal solution, but I'm working on it. :)

#2 in reply to: ↑ 1 @afercia
17 months ago

Replying to michaelarestad:

You mean like in Tools?

Yep, Tools visually renders the idea. Was thinking more to a reusable CSS class to be used where necessary in the admin, setting a max-width to the actual content (not the container) and probably expressed in em. Probably needs some research.

#3 @michaelarestad
17 months ago

Yep, Tools visually renders the idea. Was thinking more to a reusable CSS class to be used where necessary in the admin, setting a max-width to the actual content (not the container) and probably expressed in em. Probably needs some research.

Yep. Definitely was planning on doing something similar that, which makes the container a bit more flexible.

This ticket was mentioned in Slack in #glotpress by ocean90. View the logs.


17 months ago

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


9 months ago

#6 @rianrietveld
9 months ago

  • Milestone changed from Awaiting Review to Future Release

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


3 months ago

#8 @afercia
3 months ago

  • Milestone changed from Future Release to 4.8
  • Owner set to afercia
  • Status changed from new to assigned

Quickly discussed in today's accessibility meeting and one option could be introducing a max-width for some elements to begin ith. Thinking for example at paragraphs in the settings screens. And then progressively extend the new rule to other screens, where necessary. Moving to 4.8 for discussion and experimentation.

Note: See TracTickets for help on using tickets.