What I look for beneath a finished page

By Gyata Tabiri · Revised October 30, 2026

The visual finish is one part of a page. I also want to understand how its headings, controls, and reading order describe the task beneath that finish. Those decisions affect the experience and the handoff.

Start with the content

Identify the page’s main task and the sections needed to support it. Headings should describe those sections; their level should follow the content relationship. Font size and visual emphasis can then support the structure through CSS.

Use controls with a clear job

A link navigates to a destination. A button performs an action or submits a form. Native controls provide useful browser behavior, but they still need understandable labels, instructions, and feedback. Choosing the right element is a starting point, not a complete accessibility check.

Inspect an actual flow

On this site, the Contact form collects an inquiry, posts to a server handler, and shows a confirmation or an explanation of a problem. Review whether the labels, control names, and response wording agree with that behavior. A visitor should not have to infer whether a message was sent.

Review what the screenshot leaves out

Use the keyboard, enlarge the text, inspect focus, and check what happens when a required answer is missing. Test with appropriate assistive technology as part of the scope. Automated checks can find some problems, but cannot establish that the complete experience makes sense.

That is why I connect content and implementation in a review. The person using the page should understand the next step, and the colleague maintaining it should be able to follow the structure behind that step.

Web and UX work · Discuss a role or project

Reference: W3C form-label guidance.