Accessibility: headings, contrast, keyboard use, and alternative text

Documentation / Design and styling

Accessible authoring requires checking the content and the rendered page. Native components provide useful structure, but a successful save does not certify accessibility or correct every design choice.

Headings and text

Use the real page header for the page's main title. In the managed body, choose H2, H3, and H4 according to content hierarchy, not only their visual size. Use paragraph styles for ordinary copy. Keep link labels understandable without relying on color or nearby decorative imagery.

Check the page at increased browser zoom and narrow widths. Long labels, fixed-height areas, and image-based text can become difficult to read even when they fit on a desktop screen.

Contrast and media

Inspect text and Buttons against their actual backgrounds. A curtain overlay can improve readability over header media, but it does not automatically establish sufficient contrast. Review different video frames and image crops.

Provide meaningful alternative text for informative images. An image title or visible caption is not automatically an adequate substitute for the rendered alt attribute. Custom source supports image alternative text directly; inspect the saved output to confirm it describes the image's purpose. Decorative imagery should not repeat unnecessary information.

Keyboard and motion

Navigate links, Buttons, menus, forms, and dialogs with a keyboard. Check visible focus, meaningful labels, and whether focus can leave each interactive area. Review custom behavior modules and third-party embeds separately from native controls.

Enable reduced motion and ensure information remains visible and usable. Review the published page, including translated content and shared navigation, rather than only the editor.

For image preparation and forms, see Media, forms, and integrations. For custom-source boundaries, see Design and styling.