Review a builder page for accessibility
Run this review after the content and layout are stable, and again after changing responsive visibility or interactive components.
1. Read the page without styling
Use the Backend Editor as a source-order outline:
- read rows from top to bottom;
- read columns in their saved order;
- read each component inside its column;
- confirm that the sequence still makes sense when columns stack.
Do not rely on desktop position to supply meaning.
2. Check headings and text
- Use one clear page heading and a logical sequence of subheadings.
- Choose heading levels by hierarchy, not visual size.
- Write descriptive link and button labels.
- Keep instructions in text rather than only in an image or background.
3. Check media
- Give informative images useful alternative text.
- Leave decorative images with the appropriate empty alternative.
- Preserve sufficient contrast over colors, images, and video.
- Avoid essential text embedded only inside an image.
4. Test the keyboard
On the public page, use the keyboard to reach every link, button, form control, tab, accordion, carousel control, modal, and off-canvas trigger. Focus must remain visible, follow a logical order, and return sensibly when an overlay closes.
5. Review responsive visibility
Hidden content must not remove the only heading, instruction, legal information, navigation route, or action at any width. When two visual versions carry the same meaning, verify that visitors encounter only the intended one.
6. Check specialized components
For forms, verify labels, instructions, errors, and completion feedback. For carousels, maps, tabs, and accordions, confirm that controls have understandable names and that the page remains usable without pointer-only gestures.
Sign-off
Complete the review at a wide viewport and in every affected device range, while signed out. Record and correct failures before publication rather than relying on editor appearance.