🔍 Restore. Reinvest. Renew. (R3) — Accessibility Audit Report

Accessibility audit report for the Restore. Reinvest. Renew. (R3) program website (Illinois Criminal Justice Information Authority (ICJIA)).

Generated: 05/23/2026, 12:47:23 PM

Environment: Development (http://127.0.0.1:4322)

axe-core version: 4.11.4

Pages tested: 26

Viewports tested: desktop, tablet, mobile

Themes tested: default

Repo: github.com/ICJIA/icjia-r3-astro-2026 (private; access on request)

• Total Violations 0
• Total Passes 1772
• Pages Passing 26/26
• Skip Links 78/78

📋 All Tested Pages

About axe-core

What does axe-core test for?

• Semantic HTML structure (headings, landmarks, lists)
• Keyboard navigation and focus management
• Color contrast (programmatically — over solid backgrounds only)
• Form labels and field associations
• Alternative text on images and decorative-image conventions
• ARIA roles, states, properties, and valid attribute values
• Page-level requirements (document title, lang attribute, viewport meta)
• Interactive element accessible names (buttons, links, controls)
• Duplicate IDs that would confuse assistive tech

Why is axe-core critical for accessibility?

axe-core is the industry-standard automated accessibility testing engine, used by Microsoft, Google, the U.S. federal government, and most accessibility-conformance tools. Automated audits catch roughly 30–40% of WCAG conformance issues; the remainder (text-over-image contrast, keyboard traps, screen-reader experience, meaningful sequence) require human review. axe-core eliminates the large class of regressions that would otherwise reach production undetected, and is run on every build of this site via the Playwright e2e sweep at tests/e2e/a11y-sweep.spec.ts.

Rule Categories in This Audit

• WCAG 2.1 Level A & AA — the legal-conformance bar for ADA Title II / IITAA / Section 508 (the target this site is audited against).
• Best-practice rules — landmark structure, heading order, and other Deque-recommended checks beyond strict WCAG.
• Experimental rules — not included in this audit (only stable WCAG 2.1 A/AA tagged rules are run).

Configured Rules

The audit runs every axe-core rule tagged wcag2a, wcag2aa, wcag21a, or wcag21aa (68 rules total in this version of axe-core):

• area-alt — Ensure <area> elements of image maps have alternative text
• aria-allowed-attr — Ensure an element's role supports its ARIA attributes
• aria-braille-equivalent — Ensure aria-braillelabel and aria-brailleroledescription have a non-braille equivalent
• aria-command-name — Ensure every ARIA button, link and menuitem has an accessible name
• aria-conditional-attr — Ensure ARIA attributes are used as described in the specification of the element's role
• aria-deprecated-role — Ensure elements do not use deprecated roles
• aria-hidden-body — Ensure aria-hidden="true" is not present on the document body.
• aria-hidden-focus — Ensure aria-hidden elements are not focusable nor contain focusable elements
• aria-input-field-name — Ensure every ARIA input field has an accessible name
• aria-meter-name — Ensure every ARIA meter node has an accessible name
• aria-progressbar-name — Ensure every ARIA progressbar node has an accessible name
• aria-prohibited-attr — Ensure ARIA attributes are not prohibited for an element's role
• aria-required-attr — Ensure elements with ARIA roles have all required ARIA attributes
• aria-required-children — Ensure elements with an ARIA role that require child roles contain them
• aria-required-parent — Ensure elements with an ARIA role that require parent roles are contained by them
• aria-roledescription — Ensure aria-roledescription is only used on elements with an implicit or explicit role
• aria-roles — Ensure all elements with a role attribute use a valid value
• aria-toggle-field-name — Ensure every ARIA toggle field has an accessible name
• aria-tooltip-name — Ensure every ARIA tooltip node has an accessible name
• aria-valid-attr — Ensure attributes that begin with aria- are valid ARIA attributes
• aria-valid-attr-value — Ensure all ARIA attributes have valid values
• audio-caption — Ensure <audio> elements have captions
• autocomplete-valid — Ensure the autocomplete attribute is correct and suitable for the form field
• avoid-inline-spacing — Ensure that text spacing set through style attributes can be adjusted with custom stylesheets
• blink — Ensure <blink> elements are not used
• button-name — Ensure buttons have discernible text
• bypass — Ensure each page has at least one mechanism for a user to bypass navigation and jump straight to the content
• color-contrast — Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds
• css-orientation-lock — Ensure content is not locked to any specific display orientation, and the content is operable in all display orientations
• definition-list — Ensure <dl> elements are structured correctly
• dlitem — Ensure <dt> and <dd> elements are contained by a <dl>
• document-title — Ensure each HTML document contains a non-empty <title> element
• duplicate-id-aria — Ensure every id attribute value used in ARIA and in labels is unique
• form-field-multiple-labels — Ensure form field does not have multiple label elements
• frame-focusable-content — Ensure <frame> and <iframe> elements with focusable content do not have tabindex=-1
• frame-title — Ensure <iframe> and <frame> elements have an accessible name
• frame-title-unique — Ensure <iframe> and <frame> elements contain a unique title attribute
• html-has-lang — Ensure every HTML document has a lang attribute
• html-lang-valid — Ensure the lang attribute of the <html> element has a valid value
• html-xml-lang-mismatch — Ensure that HTML elements with both valid lang and xml:lang attributes agree on the base language of the page
• image-alt — Ensure <img> elements have alternative text or a role of none or presentation
• input-button-name — Ensure input buttons have discernible text
• input-image-alt — Ensure <input type="image"> elements have alternative text
• label — Ensure every form element has a label
• label-content-name-mismatch — Ensure that elements labelled through their content must have their visible text as part of their accessible name
• link-in-text-block — Ensure links are distinguished from surrounding text in a way that does not rely on color
• link-name — Ensure links have discernible text
• list — Ensure that lists are structured correctly
• listitem — Ensure <li> elements are used semantically
• marquee — Ensure <marquee> elements are not used
• meta-refresh — Ensure <meta http-equiv="refresh"> is not used for delayed refresh
• meta-viewport — Ensure <meta name="viewport"> does not disable text scaling and zooming
• nested-interactive — Ensure interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies
• no-autoplay-audio — Ensure <video> or <audio> elements do not autoplay audio for more than 3 seconds without a control mechanism to stop or mute the audio
• object-alt — Ensure <object> elements have alternative text
• p-as-heading — Ensure bold, italic text and font-size is not used to style <p> elements as a heading
• role-img-alt — Ensure [role="img"] elements have alternative text
• scrollable-region-focusable — Ensure elements that have scrollable content are accessible by keyboard in Safari
• select-name — Ensure select element has an accessible name
• server-side-image-map — Ensure that server-side image maps are not used
• summary-name — Ensure summary elements have discernible text
• svg-img-alt — Ensure <svg> elements with an img, graphics-document or graphics-symbol role have accessible text
• table-fake-caption — Ensure that tables with a caption use the <caption> element.
• td-has-header — Ensure that each non-empty data cell in a <table> larger than 3 by 3 has one or more table headers
• td-headers-attr — Ensure that each cell in a table that uses the headers attribute refers only to other <th> elements in that table
• th-has-data-cells — Ensure that <th> elements and elements with role=columnheader/rowheader have data cells they describe
• valid-lang — Ensure lang attributes have valid values
• video-caption — Ensure <video> elements have captions

What Are Skip Links?

Skip links are accessibility features that let keyboard and screen-reader users bypass repetitive navigation and jump straight to the main content of a page. Without one, every page visit requires tabbing through the entire site navigation before reaching anything useful.

Skip links are required by WCAG 2.1 Level A (Success Criterion 2.4.1 — Bypass Blocks). A compliant implementation requires four things:

• The skip link must be the first focusable element in source order.
• It must target a real element (typically #main-content or #main).
• It must be keyboard-accessible (i.e., a real <a>, not a <div> with a click handler).
• It must become visible when focused, even if hidden off-screen at rest.

Current status: ✅ All skip links present (78/78).

To verify yourself: load any page, press Tab, and the skip-to-main link should be the first thing that focuses. References: W3C SC 2.4.1 Understanding doc, WebAIM skip-nav technique.

About Testing Environments

This report was generated against the development environment at Development (http://127.0.0.1:4322). Audit results from development and production should be functionally identical — the rendered HTML / ARIA / DOM structure is the same in both modes — but stating the environment explicitly lets reviewers reproduce the audit and ties results to a specific code revision.

The same axe-core sweep runs against a production build on every CI run via tests/e2e/a11y-sweep.spec.ts, hard-failing the build on any violation. New routes are picked up automatically.

Accessibility Standards & Compliance

WCAG 2.1 Level AA

The site is audited against WCAG 2.1 Level AA — the international consensus standard for web accessibility. Level A is the minimum-bar set of success criteria; Level AA adds the contrast, reflow, and text-resize criteria that mid-grade accessibility programs target. AAA criteria (the strictest tier) are not in scope.

IITAA (Illinois Information Technology Accessibility Act)

The State of Illinois requires that public-facing IT comply with IITAA, which formally adopts WCAG 2.1 Level AA. Auditing to WCAG 2.1 AA is therefore the operative compliance target for any Illinois state agency site, including Illinois Criminal Justice Information Authority (ICJIA).

ADA Title II

The April 2024 final rule from the U.S. Department of Justice updates ADA Title II to require state and local government websites to conform to WCAG 2.1 Level AA. The compliance deadline for entities of this size is 2026; this site already satisfies the requirement.

Section 508

Section 508 of the U.S. Rehabilitation Act establishes the federal-government accessibility baseline and was harmonized with WCAG 2.0 Level AA in the 2017 "Refresh" update. Conformance with WCAG 2.1 AA exceeds Section 508 requirements.