Web Content Structure

  • Accessibility, Content Formatting, Standards

Mura provides basic containers for organizing web content. Main page content should be introduced with an H1 heading, and subordinate content sections should get H2, H3, and so on.


  • The H1 heading is used automatically for the page title, so it should not be used within the page content.
  • Use H2 for major sub-sections.
  • Use H3 for sub-sub-sections, and so on.
  • Nest headings hierarchically. Do not skip heading levels.
  • Heading text should be unique and meaningful.
  • With the right headings, a Table of Content display object can be inserted anywhere in the page with Inline Edit on frontend. It will automatically fill up with the titles and update whenever a heading is changing.

Emphasising Text


Do not bold complete sentences, only important information. Bold translates as an emphasis to screen readers. Think of bold as the equivalent of raising your voice to draw attention and apply bold as if you're highlighting text for an exam.


Limit use of italics for accessibility purposes, use Bold when possible to highlight information.


Limit the use of underlining text, as it will confuse users into thinking it is a link and will try to click on it.

Pictures & Alt Image Tag

Double click or right click on web image. Type in a description of the image in the Alternative Text box for Accessibility compliance. Alternative text is required to communicate the primary purpose of the image based on the context of the text with which the image is included.