Public reports › Cities & towns · Oregon
City · Oregon · population 21,000
ashlandoregon.gov · homepage scanned Oct 16, 2026 · WCAG 2.2 A/AA automated check
Accessibility score
79/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
2
Major
0
Minor
Homepage as loaded by our crawler on Oct 16, 2026.
In plain English
The scan found some issues on the Ashland Oregon website that might affect visitors with disabilities. For example, links without readable text can be hard for screen reader users to understand, and frames without titles can be confusing. To improve accessibility, fixing these link and frame issues would be a good first step. Automated scans like this one catch many problems, but not all, so further review is also a good idea.
Findings
Each item is one failing rule; the count shows how many elements on the page trigger it. Severity follows axe-core impact levels.
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.
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").
Severity guide
Blocks a task outright for some visitors (for example an image-only flyer with no text, or a form field with no label).
Makes a task significantly harder (low contrast, links with no name, missing frame titles).
Reduces clarity or consistency (heading order, landmarks, touch-target size).