BuildLACCDAccessibility guide

Write clear links and download labels

Give links purposeful labels, identify downloads honestly, and send unusual link behavior or document questions for technical review before publishing.

Content editors, document owners, and website reviewers3 min read

Write purposeful link text

Link the words that describe the destination or action. A person scanning only the links should be able to tell which report, registration form, project page, or external service each one opens. “Read the 2025 project delivery report” is clearer than “Read more,” and “Register for the community briefing” is clearer than “Click here.” Nearby sentence or list context can add meaning, but do not make people reconstruct it from a long page.

Example

Good link wording: “Download the campus wayfinding standards (PDF, 2.4 MB).”

Poor link wording: “Click here,” “More,” or five identical “Learn more” links in a card grid.

Do not use a raw URL as the only description when a readable title is available. If several links point to the same destination, consider combining adjacent image and text links so keyboard and screen reader users do not encounter duplicate stops.

Describe downloads honestly

For a file link, include the document title and, where useful, its format and size in the visible wording. Format and size are editorial recommendations that help people decide what will open and how much data is involved; WCAG 2.2 Success Criterion 2.4.4 requires a discernible purpose in context, not a particular “PDF” or megabyte suffix. The file itself must still be accessible. A link to an inaccessible PDF is not fixed by adding “PDF” to its label.

Use the approved document title, verify that the link resolves, and check whether a newer version has replaced the file. Warn people before opening a new window or external service when that behavior is necessary. Do not quietly add a new-tab behavior to every link.

Use editor controls and request review

In WordPress, select the descriptive text and use the Link control to add or edit the destination. Review the visible wording after the link is inserted; do not leave a filename or tracking string as the label unless that is genuinely the destination’s name. For icon-only links, ask the developer to confirm the accessible name and visible focus state.

Send the developer a list of links that open new windows, trigger downloads, launch maps, open media, or depend on JavaScript. The rendered link should be keyboard reachable, have a visible focus indicator, and expose its purpose and state. Ask the document owner to review the linked file under the standard that fits its format and delivery context. WCAG also applies to web documents delivered online; PDF/UA provides format-specific PDF guidance, and WCAG2ICT provides complementary guidance for non-web documents and software. These standards work together rather than replacing one another.

Before you publish

Check each item as you review. These marks last for this page visit only.

Before you publish

Sources and standards

Related WCAG criteria: 2.1.1 Keyboard; 2.4.4 Link Purpose (In Context); 2.4.7 Focus Visible. This is a task-specific reference, not a complete conformance checklist.

Guidance reviewed September 12, 2026. Tool interfaces may vary by version.

Related guides