Finalsite + AudioEye: Fix form labels and link text

Misty Flowers

April 28, 2026 23:26

A step-by-step walkthrough for editors: how to identify unlabeled form fields and non-descriptive link text flagged by AudioEye, and how to fix both in Finalsite. Part of the AudioEye how-to series: practical guides for the most common issues your AudioEye report surfaces.

💡Quick answers

What does AudioEye mean by these issues? Either a form field is missing a visible label, or a link uses generic text like "click here" that gives no context about where it leads.
Can AudioEye fix these automatically? No. These are content-specific issues that require manual updates in Finalsite.
How do I find the specific element? Add /?oss=1 to your page URL to launch the scanner.
How do I fix a form field? In the New Forms module, ensure the Label field is filled in and visible. Hint text and placeholder text are not substitutes.
How do I fix link text? Rewrite the link so that it describes the destination (e.g., "View our 2026 calendar" instead of "Click here").

Why form labels and link text matter

Form labels and link text share the same underlying problem: a user navigating by screen reader or keyboard has no context for what an element does. When a screen reader reaches an unlabeled text field, it simply announces "text field." The user has no way to know if they should enter their name, email, or a message.

Non-descriptive link text causes a similar problem. Screen readers can generate a "links list" to help users jump quickly to content. A list full of "click here" and "read more" is useless. Every link must make sense on its own, out of context.

What AudioEye shows you

Issues appear as "Form element does not have a label" or "Link text is not descriptive." While the report provides the URL, the /?oss=1 scanner is the fastest way to pinpoint the exact element on your page.

Step 1: Find the flagged element

Open the page your AudioEye report flagged, then add /?oss=1 to the end of the URL (or &oss=1 if the URL already has parameters). Press Enter and the scanner panel will highlight the specific element.

Step 2: Fix unlabeled form fields

Every form field needs a visible, descriptive label that is programmatically associated with the field. In Finalsite's forms, this is the Label field—the text that appears above the field.

Label vs. Hint text vs. Placeholder text

Only the Label is reliably announced by screen readers as the field's name:

Label: Appears above the field. This is the accessible name. Always required.
Hint text: Appears below the field. Useful for guidance, but not a substitute for the Label.
Placeholder text: Appears inside the field. It disappears when the user types and is often skipped by screen readers. Not a substitute for the Label.

Pro-tip for required fields

For maximum clarity, add "(required)" directly to your Label text, for example: "Email address (required)."

Step 3: Fix non-descriptive link text

Every link should make its destination clear from the link text alone. Rewrite any link that uses generic phrases like "click here," "learn more," or "this page."

Write this	Avoid this
"Read our 2026 Accessibility Policy"	"Click here" or "Read more"
"View the district calendar for May 2026"	"Here" as a linked word mid-sentence
"Download the lunch application (PDF)"	"Download" with no context

⚠️ Important Note

Do not use the Title field in link settings as a substitute for descriptive text. Tooltips do not appear on mobile or for many keyboard users. Keep the description in the actual link text.

Step 4: Verify the fix

Publish your changes in Composer (or save and publish your Form).
Reload the page with /?oss=1.
Confirm the scanner no longer flags the element.