Accessibility Report

ACADA received a 100 accessibility score in PageSpeed Insights.

This report summarizes the automated Lighthouse accessibility review for the ACADA public website and identifies the manual checks we continue to review as part of responsible accessibility practice.

Our Accessibility Statement

Accessibility at ACADA

ACADA wants everyone to experience our content, and we believe everyone deserves to enjoy learning absent constant frustration. This is why we have built accessibility into the ACADA site and coursework, to give maximum access absent controversial third-party controls many organizations have found insufficient. ACADA has made a substantial effort from the beginning of our journey to deliver quality tools, information, and reference material to everyone. If we can help you, if there is assistance you need to access our content, we want you to know your satisfaction and learning are at the top of our most fundamental priorities.

This page reflects ACADA's work on real access: readable structure, keyboard support, captions, contrast, landmarks, labels, and assistive-technology-friendly markup. The score matters because the underlying work matters.

Testing date: Site testing was completed on 6/10/2026, and results are subject to change as the site evolves. ACADA policy is to test all feature updates against accessibility standards as the site develops.

24

Passed Audits

Core automated checks passed, including labels, contrast, page landmarks, heading order, link names, image alt text, and ARIA validity.

10

Manual Checks

These items cannot be fully verified by automation and remain part of ACADA's manual review process.

38

Not Applicable

Several Lighthouse checks did not apply to the tested page or its current components.

Automated Review

What Lighthouse Confirmed

PageSpeed noted that automated accessibility checks can detect many important issues, but they do not guarantee accessibility by themselves. ACADA treats this score as a useful signal, not a substitute for human review, assistive technology testing, and direct user feedback.

Audio and Video

The report confirmed that video elements contain caption tracks using kind="captions", supporting users who need alternative content for audio and video.

Manual Review

Items We Continue To Check

These PageSpeed items are unscored because automated tools cannot fully evaluate the human experience of keyboard navigation, focus movement, visual order, and custom interaction patterns.

Interactive controls are keyboard focusable

Custom interactive controls should be keyboard focusable and display a visible focus indicator.

Interactive elements indicate their purpose and state

Links, buttons, and other controls should be distinguishable from non-interactive content and communicate their state.

The page has a logical tab order

Keyboard navigation should follow the visual layout and should not focus offscreen elements.

Visual order on the page follows DOM order

The source order should match the visual order so assistive technology users encounter content predictably.

User focus is not accidentally trapped in a region

Users should be able to tab into and out of every control, panel, drawer, or dialog.

The user focus is directed to new content added to the page

When new content appears, such as a dialog or drawer, focus should move to the new context when appropriate.

HTML5 landmark elements are used to improve navigation

Landmark elements such as main, nav, header, and footer should support navigation by assistive technology.

Offscreen content is hidden from assistive technology

Content that is visually hidden or offscreen should be hidden with display: none or aria-hidden when it is not meant to be read.

Custom controls have associated labels

Custom controls should have clear labels through visible text, aria-label, or aria-labelledby.

Custom controls have ARIA roles

Custom controls should expose roles that accurately describe their behavior.

Passed Audits

Automated Checks Passed

  • [aria-*] attributes match their roles
  • [aria-hidden="true"] is not present on the document body
  • [role]s have all required [aria-*] attributes
  • [role] values are valid
  • [aria-*] attributes have valid values
  • [aria-*] attributes are valid and not misspelled
  • Buttons have an accessible name
  • Image elements have alt attributes
  • User-scalable viewport restrictions are not used
  • ARIA attributes are used as specified for the element role
  • [aria-hidden="true"] elements do not contain focusable descendants
  • Elements use only permitted ARIA attributes
  • Background and foreground colors have sufficient contrast
  • Document has a title element
  • HTML element has a lang attribute
  • HTML element has a valid lang value
  • Links have a discernible name
  • Lists contain only valid list items and supporting elements
  • List items are contained within list parents
  • Touch targets have sufficient size and spacing
  • Heading elements appear in sequentially descending order
  • Skip links are focusable
  • Document has a main landmark
  • Deprecated ARIA roles were not used

Need Assistance?

Tell us where access can be better.

Accessibility is an ongoing responsibility. If any ACADA page, course, record, or tool creates a barrier for you, contact us and we will work to help you access the material.

Contact ACADA