Skip to main content

Public reports › Cities & towns · North Carolina

City · North Carolina · population 19,092

Town of Boone

townofboone.net · homepage scanned Oct 15, 2026 · WCAG 2.2 A/AA automated check

C

Accessibility score

77/100 · Needs work

The homepage has issues that make common tasks harder for people using screen readers, keyboards or magnification. They are typically template-level and fixable in a day of vendor time.

0

Critical

3

Major

0

Minor

Screenshot of the Town of Boone homepage at scan time

Homepage as loaded by our crawler on Oct 15, 2026.

In plain English

What this means for visitors

The scan found some issues on the town's website that might make it hard for visitors with disabilities to use. For example, some text is hard to read because it doesn't stand out enough from the background, which can be a problem for people with low vision. To improve accessibility, start by fixing the contrast issues, as this will help the most visitors. Keep in mind that automated scans like this one catch many problems, but not all, so further review is still needed.

Findings

3 issue types found on the homepage

Each item is one failing rule; the count shows how many elements on the page trigger it. Severity follows axe-core impact levels.

#1MajorWCAG 1.4.34 elementsRule details ↗

Text doesn't have enough contrast against its background

Light grey text on white, or text over photos, is hard or impossible to read for people with low vision or color blindness, and for anyone outdoors on a phone.

Who it affects

Makes a task significantly harder (low contrast, links with no name, missing frame titles).

First fix

Use a darker text color or lighter background so the contrast ratio is at least 4.5:1 (3:1 for large text).

#2MajorWCAG 4.1.21 elementRule details ↗

Embedded frames have no title

Embedded maps, calendars and videos are announced as 'frame' with no description.

Who it affects

Makes a task significantly harder (low contrast, links with no name, missing frame titles).

First fix

Add a title attribute to each <iframe> (for example title="Google Map of the district office").

#3MajorWCAG 2.4.41 elementRule details ↗

Links have no readable text

Screen readers announce these links as just 'link', so people can't tell where they go. Common with icon-only links and 'read more' buttons.

Who it affects

Makes a task significantly harder (low contrast, links with no name, missing frame titles).

First fix

Give every link visible text, or add an aria-label describing the destination.

Severity guide

How to read the counts

Critical

Blocks a task outright for some visitors (for example an image-only flyer with no text, or a form field with no label).

Major

Makes a task significantly harder (low contrast, links with no name, missing frame titles).

Minor

Reduces clarity or consistency (heading order, landmarks, touch-target size).

What this grade does and does not cover

  • Covers: the public homepage only, loaded once in a desktop browser, tested with axe-core against WCAG 2.2 Level A and AA rules (a superset of the WCAG 2.1 AA standard in the DOJ rule).
  • Does not cover: inner pages, PDFs and documents, logged-in portals, video captions, alt-text quality, keyboard usability of custom widgets, or anything that needs a human judgment.
  • A grade is a monitoring signal, not a legal assessment or certification. How we score.