The operational decision
Give visitors a clear structure for finding hours, directions and contact routes. Accessibility review starts with the actual task a visitor needs to complete: finding an entrance, reading hours or contacting staff. A polished appearance alone does not show that the information can be used.
Prepare the workflow
Use real heading elements with descriptive names and a logical hierarchy; do not rely on large bold paragraphs alone to communicate structure.
Example wording for approval
“Office hours, Getting here and Contact the practice are separate sections in this example. Each heading should describe the information that follows it.”
Worked example
A fictional page uses large bold text for hours, directions and contact details, but none is marked as a heading. A visual reviewer can scan it while a heading-navigation user receives no structure. Have the editor inspect the semantic outline and assign headings to the actual sections. Then navigate directly to Contact the practice. The review passes when the structural labels and their order reflect the page's real tasks, not merely the designer's preferred font sizes.
Handoff record
Record these task-specific fields: page URL, heading outline, missing section, editor.
Acceptance check
Navigate the heading list with assistive technology or an inspection tool. Confirm that the order matches the public page and that headings identify actual sections.
Further reading
Try Ava with your business’s public information ↗