Making WordPress.org

Opened 6 years ago

Closed 13 months ago

#3559 closed defect (bug) (fixed)

About section: make heading sizes consistent

Reported by: tellyworth's profile tellyworth Owned by: mapk's profile mapk
Milestone: Priority: normal
Component: General Keywords: close
Cc:

Description

Some of the main and subheadings used on different About pages are inconsistent and have different CSS.

It's not entirely clear which ones are intentionally different and which are accidental.

See https://meta.trac.wordpress.org/ticket/3046#comment:122 and follow-up discussion.

Change History (5)

#1 @tellyworth
6 years ago

Related: there are some resulting a11y issues, as pointed out by @rianrietveld in https://meta.trac.wordpress.org/ticket/3046#comment:104

#2 @rianrietveld
6 years ago

You can find more detailed information about semantic heading structure in the a11y handbook:
https://make.wordpress.org/accessibility/handbook/best-practices/markup/heading-structure-in-theme-development/

#3 @obenland
6 years ago

  • Owner set to mapk
  • Status changed from new to assigned

It's unfortunate that we've not been able to come up with a consistent headings style across the different uses so far. I think it warrants a design review and possibly a small style guide.

In wporg we have a base set of heading styles, as demonstrated on the formatting unit test page, but these base styles are not utilized in either wporg-main or wporg-plugins.

As far as I can tell there are two page structures that need to be covered:

  1. Top-level pages, like the main About page.
  2. Subpages, like Developer Documentation or Requirements.

Somehow we managed to give them three different styles, if you include the support welcome page.

#4 @ben.greeley
13 months ago

  • Keywords close added

@tellyworth It looks like this ticket was specific to the CSS of the older sites being inconsistent across sites. With the redesign project underway and the sites mentioned here already redesigned or slated for a redesign, would it make sense to close this?

#5 @tellyworth
13 months ago

  • Resolution set to fixed
  • Status changed from assigned to closed

Yeah let's close this one, and open a fresh ticket if newly published headings are inconsistent.

Note: See TracTickets for help on using tickets.