Skip to main content

Public reports › School districts · Colorado

School district · Colorado · 38,197 students

Adams-Arapahoe 28J

aurorak12.org · homepage scanned Oct 16, 2026 · WCAG 2.2 A/AA automated check

C

Accessibility score

73/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

4

Major

0

Minor

Screenshot of the Adams-Arapahoe 28J homepage at scan time

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

In plain English

What this means for visitors

The scan found some issues on the website that might cause problems for visitors with disabilities. For example, small touch targets can be hard to tap for people with low vision or limited dexterity. To improve accessibility, start by making touch targets larger and fixing lists that are built incorrectly. Automated scans like this one catch many issues, but not all, so further review is recommended to ensure the site is usable for everyone, including those who rely on screen readers or keyboard-only navigation under ADA Title II.

Findings

4 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 2.5.83 elementsRule details ↗

Touch targets are too small

Small links and buttons are hard to tap for people with motor impairments.

Who it affects

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

First fix

Make clickable targets at least 24×24 CSS pixels or add spacing.

#2MajorWCAG 4.1.21 elementRule details ↗

Hidden content can receive focus

Keyboard users land on elements that screen readers say don't exist.

Who it affects

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

First fix

Remove tabindex from hidden elements or don't hide focusable content with aria-hidden.

#3MajorWCAG 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").

#4MajorWCAG 1.3.11 elementRule details ↗

Lists are built incorrectly

List structure is broken, so screen readers can't announce 'list of 5 items'.

Who it affects

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

First fix

Only put <li> inside <ul>/<ol>; remove stray elements injected by the editor.

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.