Core Accessibility Principles for Content Authors

Headings organize content for screen reader users and improve readability.

Use headings in a logical hierarchy:

• H1 for the page title
• H2 for major sections
• H3 for subsections
• H4-H6 when necessary

Do not:

• Skip heading levels.
• Use headings only for visual styling.
• Bold regular text instead of using actual heading elements.

Descriptive links improve navigation for screen reader users and users navigating by links alone. Links should describe their destination or purpose.

Avoid vague phrases such as:

• Click here
• Read more
• More
• Learn more

• See Accessibility Bytes #4: Descriptive Links and Hypertext for more information.

Alternative text (alt text) provides a text equivalent description of the image’s purpose. Use alt text for:

• Informative graphics.
• Charts.
• Icons that convey meaning.
• Photographs containing important information.

Keep alt text concise and meaningful. If an image is decorative, mark it as decorative when the platform supports that option.

• See Authoring Meaningful Alternative Text and Accessibility Bytes #5 Alternative Text for more information.

Text must have sufficient contrast against its background. Common failures include:

• Light gray text on white backgrounds.
• Colored text over images.
• Low-contrast buttons or links.

Do not rely on color alone to communicate meaning. Instead of “Required fields shown only in red”, use “Required fields marked with both color and text such as "Required".

• See Making Color Usage Accessible, Accessibility Bytes #2 Color Contrast, and Accessibility Bytes #3 Use of Color for more information.

Structured programmatic lists improve navigation and screen reader interpretation. Use built-in list formatting tools instead of manually typing symbols. Use bulleted or numbered lists instead of typing dashes manually or using spacing to simulate lists.

• See Accessibility Bytes #7 Information Grouped in a List for more information.

Use tables only for data. Do not use tables to visually position content on a page. When creating tables, use built-in options, where they exist, for row headers and column headers rather than manually formatting text to appear as a header.

Requirements for accessible tables include:

• Programmatic headers, such as column or row headers.
• Simple table structure when possible; avoid merged or split cells unless necessary.
• Each data cell is programmatically associated with all applicable header cells.

Forms are among the most common outputs of low-code and no-code platforms. Accessibility barriers within forms can prevent users from completing tasks, requesting services, submitting information, or participating in programs.

Authors and administrators should ensure:

• Form fields have visible and programmatic labels.
• Instructions are clear and associated with the relevant fields.
• Required fields are clearly identified.
• Error messages explain how to correct problems.
• Keyboard users can complete the entire form.
• Focus moves appropriately after validation errors.
• Time limits, if used, are communicated and adjustable when appropriate.

Accessibility testing should include both form completion and error recovery scenarios.

A fully accessible webpage can still fail accessibility requirements if linked documents are inaccessible.

Common document issues include:

• Missing headings.
• Missing document language.
• Improper reading order.
• Missing alternative text.
• Untagged PDFs.
• Incorrect table structure.

Before uploading:

• Verify document accessibility.
• Use accessible templates.
• Export tagged PDFs.
• Test with accessibility checkers.
• Prioritize publishing information as accessible HTML rather than relying solely on downloadable files whenever feasible.

• For more information on accessible documents, see Create Accessible Digital Products, Accessibility Bytes No. 1: Use Document Accessibility Checkers and Accessibility Bytes No. 17: Five Tips for Accessible Documents.

Audio-only, video-only and synchronized media require accessibility alternatives that allow users who cannot see, hear, or access portions of the content to obtain equivalent information and understand the content. This may require:

• Captions
• Audio descriptions.
• Transcripts.
• Accessible media players.

The specific accessibility requirements depend on the type of media and how information is presented.

Before publishing audio, video or multimedia, verify:

• Captions are accurate and synchronized.
• Media controls are keyboard accessible and programmatically labeled.
• Audio descriptions are sufficient.

• See Audio- and Video-Only Media, Captions and Transcripts, and Video and Other Synchronized Media for more information.