Make WordPress Core

Opened 10 years ago

Closed 10 years ago

#38670 closed defect (bug) (fixed)

Twenty Seventeen: Post navigation font styles cause legibility issues

Reported by: laurelfulford Owned by: davidakennedy
Priority: normal Milestone: 4.7
Component: Bundled Theme Version:
Severity: normal Keywords: has-patch
Cc: Focuses:

Description

Originally brought up in Slack by @celloexpressions:

The combination of font-size and weight for post navigation makes lower case "i"s illegible, which can be very confusing. This is in Chrome/Windows.

Bumping the font size up or down by a pixel or two, or changing the font weight fixed it after some experimenting. I can't imagine this error is desired in the design, but I'm unsure of other solutions here.

https://wordpress.slack.com/archives/core-themes/p1478148620000040

Have discussed with @melchoyce, and the recommended fix is changing the font size from 16px to 17px.

Attachments (2)

2017-post-nav-unreadable-i.PNG (5.7 KB ) - added by laurelfulford 10 years ago.
38670.patch (1.3 KB ) - added by laurelfulford 10 years ago.

Download all attachments as: .zip

Change History (5)

#1 @davidakennedy
10 years ago

  • Keywords needs-patch added
  • Milestone Awaiting Review4.7

#2 @laurelfulford
10 years ago

  • Keywords has-patch added; needs-patch removed

Tested and discussed with @melchoyce a bit more - ended up changing the font size to 15px in 38670.patch , since 17px still had some legibility font styles.

Also adjusted the spacing around the arrows a bit, since they touch the text on small screen sizes.

#3 @davidakennedy
10 years ago

  • Owner set to davidakennedy
  • Resolutionfixed
  • Status newclosed

In 39152:

Twenty Seventeen: Fix post navigation font legibility issue

The combination of font-size and weight for post navigation made lower case "i"s illegible in some cases. Using 15px seemed to be the best choice all around. Also adjusts the spacing around the arrows a bit, since they touch the text on small screen sizes.

Props laurelfulford.

Fixes #38670.

Note: See TracTickets for help on using tickets.