KnowledgeBase content accessibility

When creating KnowledgeBase content, it is important to use headings to define the structure of your page. In the KnowledgeBase editor, heading levels can be set in the “Paragraph Format” menu. Learn more about document style guidelines for the KnowledgeBase.

• There is a single heading level one. When creating a KnowledgeBase page, this will be your title.
• Headings two through four are hierarchical and structured like a page outline.
• Headings should be used to structure content, not for stylistic purposes. You can restyle your headings if needed.

Learn more about heading structure.

It is important to write concise, descriptive link text. When adding links in the KnowledgeBase editor, there is a “text” field to enter the text that will be displayed as your link. Learn how to write meaningful link text.

• Avoid using uninformative link phrases, such as “Click Here” or “Learn More.”
• Avoid using full URLs as they are long and complex and do not inform the user about the destination of the link.
• Avoid having links that open in a new tab.
  • When adding a link in the KnowledgeBase editor, there is a checkbox to open links in a new tab, which should not be checked in most instances. Links opening in a new tab can be disorienting for people with low vision or who are navigating via screen reader, especially when there is no warning.

When adding a table in KnowledgeBase content, there are a few steps to conveying your data accessibly:

• Mark up all column headers or row headers as table headers. You can select the table and add a header row from the table options. You can also indicate the scope of your header row or column in HTML using the scope attribute, for example: Header column name
• Header row name
• Use tables only when needed to present data. Avoid using tables to create a page layout.

WebAIM: Creating Accessible Tables