In This Article

System settings: accessibility

The Accessibility tab (CMS only) allows you to enable (or disable) the use of the H1 and H2 heading choices in the rich text editor. By default, these heading choices are disabled so that the first heading choice is the H3 tag. This is done to preserve web-accessible formatting -- and WCAG 2.0 compliance.

Accessibility tab of the system settings


Why are they disabled?

These are disabled by default because header elements such as H1, H2, H3, etc., are meant to convey the hierarchy of information. As a result, the guide title is the H1, box titles are H2, and any headings within rich text content will begin with H3 to maintain the hierarchy that is mandated with WCAG 2.0

If you want to add an H1 or H2 element to a rich text item without enabling it at the system level, you can click the Source button in the rich text editor and change an <h3> to an <h1> or <h2> in the HTML code.

rich text editor has h1 and h2 disabled


Why would you enable them?

If you have boxes set to display as floating boxes -- meaning the box title and borders are not present --  outside of your LibGuides system (via box widgets), you may wish to make the H1 and H2 elements available to your authors.

  1. Go to Admin > System Settings.
  2. Click on the Accessibility tab.
  3. In the Rich Text Editor panel, use the H1/H2 Headings option to enable or disable these headings in the Rich Text Editor.
    • Disabled: the "Heading 1" and "Heading 2" options will be hidden from the Rich Text Editor's Format dropdown. (Users could still add <h1> and <h2> elements by editing the source code of their Rich Text/HTML content item.)
    • Enabled: the "Heading 1" and "Heading 2" options will appear in the Rich Text Editor's Format dropdown.

Accessibility options for the rich text editor

Related Articles

    Nav menu script