Headings are responsible for breaking up content on the page in a way that screen readers can parse the different sections. Screen reader users are not able to scan the site visually, so this allows them to skip from section to section without having to hear all of the content read out loud first.

1. Headings break up blocks of content

Matthew Kilgore Cemetery Rules and Regulations – without proper heading definitions, this page would be difficult to access for screen reader users: http://www.cityofranchocordova.org/residents/about-us/history/matthew-kilgore-cemetery/cemetery-rules-regulations

Example:

2. Use bold, italics, and underline sparingly

Because these formatting tools are often used in lieu of headings, they are usually unnecessary. Also, if users are not careful about pasting in plain text into the CMS, then it will bring over tags that compromise the accessibility of the page. If you must use one of them, then apply it using the CMS toolbar.

3. Nest headings

Every page has Heading 1 already defined by default in the page title, so you must always use Heading 2 as the very first heading on every page. If using subheadings, they must be sequential--you cannot skip levels. i.e. Heading 3 followed by Heading 4, followed by Heading 5:

Example:

It is also important to note that all content after a heading is defined underneath it.

• Prompt for more information falls under the Holidays Heading at the bottom of the page: http://www.cityofranchocordova.org/i-want-to-/learn-about/rancho-cordovan-shuttle-service
• About Header was added to segment information for Council Member Linda Budge*: http://www.cityofranchocordova.org/government/city-council-/council-member-linda-budge