How to check an appointment link’s accessible name

An accessible name is the label associated with a control in the accessibility information exposed by the page. It helps people identify a link’s purpose. A control can receive keyboard focus while still lacking that label. W3C explains the requirement to expose a control’s name, role and value.

Example: a scheduling graphic

Consider a link containing an image with the visible words “Schedule online.” If the image has empty alternative text and there is no other naming information, the link can be unnamed.

In this simplified example, the image alternative provides the link’s name:

<a href="/appointments/">
  <img src="schedule-online.svg" alt="Schedule online">
</a>

Visible HTML text is another straightforward option:

<a href="/appointments/">Schedule online</a>

The name should describe the actual destination or action. Supplying a name does not verify that the appointment system itself works accessibly. W3C provides guidance on meaningful link purpose.

Example: a phone icon

If a phone icon is decorative and hidden from accessibility software, provide a meaningful name on its link. Your vendor can use visible text or an appropriate accessible label, such as “Call the dental practice.” The actual telephone destination must also be checked.

When visible text is present, keep it consistent with the control’s accessible name. Avoid adding labels mechanically without checking the complete control and its purpose.

What to ask your website vendor

For each appointment or contact control, ask the vendor to record:

1. The page address and the exact link being checked.
2. The name and role shown in browser accessibility tools.
3. Whether the control can be reached and operated with a keyboard.
4. Results from the planned assistive-technology checks.
5. The change made and the same checks repeated afterward.

Keep identification, activation and task completion as separate results. A meaningful link name is one part of helping a patient book an appointment. Use our dental accessibility checklist and vendor handoff record to define the broader work.

How this example was checked

Intake Compliance tested simplified, fictional scheduling and phone controls in Chromium 153 using axe-core 4.13.0 and native browser accessibility information. The unnamed versions produced two targeted link-name findings. The corrected versions exposed the intended names and produced no findings for that specific rule.

This is a narrow technical demonstration. It does not describe a client project, establish whole-site conformance, or replace testing with people who use assistive technology. The example does not report findings about any named practice. Sources and the demonstration were checked on September 10, 2026.

For related work, see dental website accessibility services and dental intake-form accessibility.