Use POM shortcodes accessibly
Accessibility depends on the content and settings supplied to each element. Review the published page as a visitor, not only the builder preview.
Headings and reading order
- Use Title heading levels to describe the page hierarchy.
- Keep the source order meaningful when columns stack.
- Do not choose a heading level only for its visual size.
- Give every section a visible heading when it helps visitors understand the content.
Links, buttons and icons
- Write button text that describes the result of activating it.
- Use Button Aria-Label when the visible label needs more context.
- Do not use an icon as the only label unless the component provides an accessible name.
- Confirm links and controls remain distinguishable without relying only on color.
- When opening another window, make that outcome clear to the visitor.
Interactive containers
For accordions, tabs, modals, off-canvas panels, sliders and carousels:
- Test every trigger with a keyboard.
- Confirm focus moves or remains in a predictable location.
- Confirm controls have understandable labels.
- Avoid automatic movement that prevents reading.
- Ensure hidden panels do not create duplicate announcements.
Carousel cells outside the visible viewport are removed from keyboard and assistive-technology navigation until they become visible.
Images, video and maps
- Supply meaningful alternative text for informative images.
- Use empty alternative text for purely decorative images.
- Provide captions or transcripts for essential recorded media.
- Do not autoplay audio.
- Ensure map information is also available in text when it is needed to complete a task.
Forms and dynamic results
Use visible labels and instructions. Verify validation messages, required fields, loading states, empty results and successful submission without relying only on color or motion. Faceted Search controls should announce their purpose and maintain a logical keyboard order.
Device visibility
Do not hide essential content from one viewport. When maintaining separate visual versions, ensure visitors encounter only one equivalent version at a time.
Verification
Review keyboard navigation, focus visibility, heading order, labels, alternative text, contrast, zoom and reduced-motion behavior on the public page.