In the old, blue template there was an issue with document structure. There are two <h1> tags - or semantically speaking, two main headlines. This is an accessibility issue in that a document cannot be logically structured while it is like this.
In the new version of the template we have sought to remedy this by making the site branding header the h1 and the main content heading the h2. When authors create new pages they will have better structure and be more accessible.
When a site is migrated from the old blue templates to the new templates, there are potentially hundreds of headings that need to be ‘demoted’ from h1 to h2 and possibly h2 to h3. It could be a lot of work!
Instead of forcing this issue at the time of migration, there is a workaround that allows h1 headings to at least be styled like the h2 headings, lessening the visible impact and allowing maintainers to fix the issue when they are updating pages for other reasons. The idea is to allow a graceful migration that doesn’t cause much extra work.
The workaround is simply to apply the h2 styles to the h1 element via your custom style sheet. Adding the following code to your custom.css will cause h1 elements to be styled as h2 elements.
#content h1
{
letter-spacing: .05em;
font-size: 1.8em;
color: #567;
margin: 0 0 0.5em 0;
padding: 0;
}
This is not a perfect workaround as it will allow maintainers to ignore some problems with their pages. Ideally, it would be possible to use a find/replace routine to demote headings, but at this stage it isn’t available. Given that the problem has been brought about by changes of template structure rather than poor content, it is reasonable to allow maintainers to gradually fix the issue in the course of natural updates to pages.