Site accessibility: check real forms and paths

A contact form is a meeting point between the site and an interested person. If the required field is not recognizable, the error message is vague, or the button cannot be reached from the keyboard, that path can break. Verifying these aspects makes the brand's attention towards those who use the service more concrete.

This guide offers a first operational review of pages and modules. It is not a complete audit, nor a declaration of compliance. The technical reference for further information is the W3C WCAG 2.2 quick guide; the tests described help identify problems to analyze and correct.

Choose a real route

Start from a goal: find a solution, read a card and request an appointment. Follow the links as a visitor unfamiliar with the site would. A single page may appear uncluttered while the overall journey changes terminology, hides a step, or ends without intelligible confirmation.

Prepare a short sheet with address, attempted action, observed result and obstacle. Avoid generic descriptions such as “the module is difficult”. A note such as «after the error I don't understand which field to correct» allows the person responding to reproduce the problem.

Test the path with the keyboard

Retrace actions without using the mouse. Observe which elements receive focus, whether the hotspot remains visible, and whether the order is understandable. Control menus, overlay windows and forms. If you open an interactive element, make sure you can use it and close it without getting stuck.

This test offers different information than a simple visual inspection. A button may appear very clear and be difficult to reach. Note the exact point of the route, the device and browser used: a reproducible report is more useful than an overall judgment of the page.

Review form labels and messages

The W3C Forms Tutorial delves into labels, instructions, and feedback. As your first editorial exercise, read each field and ask yourself what information a new person should enter. Example text within the field should not be the only explanation available while filling in.

Try submitting the form with missing information and then with an invalid format. A helpful message identifies the problem and suggests the relevant fix. «Error» says little; «Enter an email address in the format name@domain» helps you understand what to change, when that is actually the required format.

Control contents and magnification

Read the page by increasing the magnification and reducing the width of the window. Look for covered text, disappearing controls, and lines that require constant horizontal movement. Also try a longer title: a multilingual page can highlight limitations that are not noticeable in the short version.

Then evaluate the connections outside the context of the sentence. A “click here” list does not help distinguish destinations. Use wording that describes the page or action, such as «consult the CMS features». For informative images, check that the text alternative communicates the useful information, without turning into a sequence of keywords.

Organize work by impact on the path

Suppose, as an example, you find three problems: a slightly misaligned title, an incomprehensible error and a button that is unreachable from the keyboard. The operational priority should consider how much each problem prevents you from completing the task. This assessment does not replace the requirements analysis, but helps to start with the most concrete interruptions.

• Reproduce the problem with short, precise steps.
• Identify the person or role who can correct it.
• Define what behavior the fix will demonstrate.
• Try the same route again after the intervention.
• Check relevant language variants and devices.

The W3C Easy Checks collection is useful for in-depth analysis of a first review. Passing some initial checks does not prove that every piece of content is accessible: more extensive checks are needed when evaluating the entire site.

For a team using ElaiFlow, these tests can become part of the review of pages before publishing. The CMS helps manage the content; the quality of the journey requires attention to what is actually published. Continue with the checklist for multilingual versions.

Content prepared with AI assistance; sources consulted on 19 September 2026. The guide is introductory and does not certify the compliance of sites or products.

Illustrative AI-generated cover; it does not depict actual EL-AI people, premises or installations.