Accessibility conformance
VPAT 2.5 Accessibility Conformance Report
Name of product: Career Readiness Report public website (careerreadinessreport.com) Report date: July 27, 2026 Report version: 1.0 Contact: [email protected] Vendor: Champlin Enterprises, LLC, Illinois, United States VPAT version used: VPAT 2.5 INT (November 2023), the edition covering WCAG, Revised Section 508 and EN 301 549 in a single report.
Scope of this report, read before the tables
This ACR covers the public website at careerreadinessreport.com as it exists on the report date. It does not cover the assessment application, which launches August 15, 2026 with capabilities rolling out on a published roadmap from there.
We are drawing that line explicitly because the alternative is worse. Publishing an ACR for software that does not yet exist would mean asserting tested conformance for interfaces nobody has tested, and an accessibility coordinator relying on it would be relying on fiction. An ACR covering the application is issued against the running product once its interfaces exist, and will supersede this one.
What this report is good for today: it shows the standard we build to, the methods we test with, and the specific criteria we already meet on a real shipped interface.
Applicable standards and guidelines
| Standard | Included in this report |
|---|---|
| WCAG 2.2 Level A | Yes |
| WCAG 2.2 Level AA | Yes |
| WCAG 2.2 Level AAA | No, not evaluated |
| Revised Section 508 (36 CFR Part 1194, Appendices A, B, C) | Yes |
| EN 301 549 v3.2.1 | Yes |
Terms used
- Supports. The functionality of the product has at least one method that meets the
criterion without known defects, or meets it with equivalent facilitation.
- Partially Supports. Some functionality does not meet the criterion.
- Does Not Support. The majority of functionality does not meet the criterion.
- Not Applicable. The criterion is not relevant to the product.
Evaluation methods
- Automated: Lighthouse accessibility audits run against the live site on every deploy.
Current score 100.
- Automated: axe-core rule set.
- Manual: keyboard-only traversal of every page and interactive element, including the
launch-notification form.
- Manual: screen reader spot checks with VoiceOver on macOS and Safari.
- Manual: 400% zoom and 320 CSS pixel reflow checks.
- Manual: contrast ratio verification of every text and background pairing against the
design tokens.
We have not commissioned a third-party accessibility audit, and we have not conducted usability testing with assistive-technology users. Both are stated as limitations rather than omitted.
---
Table 1: Success Criteria, Level A
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Supports | All informative images carry descriptive alt text; decorative images use alt="". Icons are inline SVG marked aria-hidden with adjacent text labels. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | No audio or video content. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No audio or video content. |
| 1.2.3 Audio Description or Media Alternative | Not Applicable | No audio or video content. |
| 1.3.1 Info and Relationships | Supports | Semantic HTML throughout: landmarks, h1-h3 hierarchy with no skipped levels, ul role="list", real table markup with header cells, labels bound to inputs. |
| 1.3.2 Meaningful Sequence | Supports | DOM order matches visual order; no CSS reordering that changes reading sequence. |
| 1.3.3 Sensory Characteristics | Supports | No instruction depends on shape, size or position alone. |
| 1.4.1 Use of Color | Supports | Color is never the sole means of conveying information. Links are underlined or otherwise distinguished in body copy. |
| 1.4.2 Audio Control | Not Applicable | No auto-playing audio. |
| 2.1.1 Keyboard | Supports | All interactive elements are reachable and operable by keyboard. The site uses native controls. |
| 2.1.2 No Keyboard Trap | Supports | No component traps focus. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No single-character key shortcuts implemented. |
| 2.2.1 Timing Adjustable | Not Applicable | No time limits. |
| 2.2.2 Pause, Stop, Hide | Supports | No auto-updating or moving content. Scroll-reveal animations are decorative, run once, and are disabled under prefers-reduced-motion. |
| 2.3.1 Three Flashes or Below Threshold | Supports | No flashing content. |
| 2.4.1 Bypass Blocks | Supports | Skip link to main content, plus ARIA landmarks. |
| 2.4.2 Page Titled | Supports | Every page has a unique, descriptive title. |
| 2.4.3 Focus Order | Supports | Focus order follows a logical reading sequence. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text is descriptive; no bare "click here" or "read more". |
| 2.5.1 Pointer Gestures | Not Applicable | No multipoint or path-based gestures. |
| 2.5.2 Pointer Cancellation | Supports | Activation occurs on the up-event via native controls. |
| 2.5.3 Label in Name | Supports | Accessible names contain the visible label text. |
| 2.5.4 Motion Actuation | Not Applicable | No motion-actuated functionality. |
| 3.1.1 Language of Page | Supports | lang="en" on the root element. |
| 3.2.1 On Focus | Supports | Focus does not trigger a change of context. |
| 3.2.2 On Input | Supports | No automatic context change on input. The notification form submits only on explicit activation. |
| 3.2.6 Consistent Help (WCAG 2.2) | Supports | Contact routes appear in the footer in the same location on every page. |
| 3.3.1 Error Identification | Supports | Form errors are identified in text and announced via a live region. |
| 3.3.2 Labels or Instructions | Supports | Every input has a persistent visible label. The honeypot field is hidden from assistive technology and excluded from the tab order. |
| 3.3.7 Redundant Entry (WCAG 2.2) | Not Applicable | Single-step form; no information is requested twice. |
| 4.1.2 Name, Role, Value | Supports | Native elements throughout; ARIA used only where native semantics are insufficient. |
WCAG 2.2 removed 4.1.1 Parsing, so it is not reported.
---
Table 2: Success Criteria, Level AA
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No live media. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No video content. |
| 1.3.4 Orientation | Supports | Layout works in both portrait and landscape; no orientation lock. |
| 1.3.5 Identify Input Purpose | Supports | The email input uses type="email" with autocomplete="email". |
| 1.4.3 Contrast (Minimum) | Supports | All text pairings verified. The lowest ratio in the system is 5.00:1 (muted text on the footer tint) against a 4.5:1 requirement. Body text is well above. |
| 1.4.4 Resize Text | Supports | Text scales to 200% without loss of content or function; layout uses relative units. |
| 1.4.5 Images of Text | Supports | No images of text except the logo wordmark, which is exempt as a logotype. |
| 1.4.10 Reflow | Supports | No horizontal scrolling at 320 CSS pixels. Wide tables scroll within their own container rather than forcing the page to scroll. |
| 1.4.11 Non-text Contrast | Supports | Interactive component boundaries and focus indicators meet 3:1 against adjacent colors. |
| 1.4.12 Text Spacing | Supports | No loss of content when spacing overrides are applied. |
| 1.4.13 Content on Hover or Focus | Not Applicable | No hover or focus-triggered additional content. |
| 2.4.5 Multiple Ways | Supports | Footer navigation, in-page links, an XML sitemap and an RSS feed. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe topic or purpose. |
| 2.4.7 Focus Visible | Supports | A visible focus ring is present on all focusable elements; the browser default is enhanced, never removed. |
| 2.4.11 Focus Not Obscured (Minimum) (WCAG 2.2) | Supports | No sticky element obscures a focused control. |
| 2.5.7 Dragging Movements (WCAG 2.2) | Not Applicable | No dragging operations. |
| 2.5.8 Target Size (Minimum) (WCAG 2.2) | Supports | Interactive targets meet or exceed 24 by 24 CSS pixels. |
| 3.1.2 Language of Parts | Not Applicable | All content is in English. |
| 3.2.3 Consistent Navigation | Supports | Navigation appears in the same relative order on every page. |
| 3.2.4 Consistent Identification | Supports | Components with the same function are labeled consistently. |
| 3.3.3 Error Suggestion | Supports | Validation messages describe how to correct the input. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | No legal, financial or data-modifying transactions on the public site. |
| 3.3.8 Accessible Authentication (Minimum) (WCAG 2.2) | Not Applicable | No authentication on the public site. Noted as in scope for the application ACR, where the planned answer is that authentication requires no cognitive function test and supports password managers and campus SSO. |
---
Revised Section 508 Report
Chapter 3, Functional Performance Criteria
| Criterion | Conformance | Remarks |
|---|---|---|
| 302.1 Without Vision | Supports | Full screen-reader operability; all content available as text. |
| 302.2 With Limited Vision | Supports | Zoom to 200% and reflow at 320px both supported; contrast exceeds minimums. |
| 302.3 Without Perception of Color | Supports | No information conveyed by color alone. |
| 302.4 Without Hearing | Not Applicable | No audio content. |
| 302.5 With Limited Hearing | Not Applicable | No audio content. |
| 302.6 Without Speech | Not Applicable | No speech input required. |
| 302.7 With Limited Manipulation | Supports | Full keyboard operability; targets meet 24px minimum; no dragging. |
| 302.8 With Limited Reach and Strength | Supports | No operation requires simultaneous actions or sustained input. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | Plain language, consistent structure, reduced-motion support, no time limits. |
Chapter 4, Hardware. Not Applicable. The product is web software with no hardware component.
Chapter 5, Software. 501.1 applies through the WCAG tables above. The product is a web application accessed in a standard browser and exposes no platform accessibility services of its own.
Chapter 6, Support Documentation and Services. Supports. Documentation is published as accessible HTML on this site rather than as untagged PDF. Support is provided by email at [email protected], which imposes no requirement to use speech or hearing.
---
EN 301 549 v3.2.1
| Chapter | Conformance | Remarks |
|---|---|---|
| 4.2 Functional performance | Supports | See Chapter 3 table above. |
| 5 Generic requirements | Partially Applicable | Closed-functionality requirements do not apply to browser-based software. |
| 6 ICT with two-way voice communication | Not Applicable | No voice communication. |
| 7 ICT with video capabilities | Not Applicable | No video. |
| 8 Hardware | Not Applicable | No hardware. |
| 9 Web | Supports | WCAG 2.2 AA per the tables above, which exceeds the WCAG 2.1 AA baseline EN 301 549 references. |
| 10 Non-web documents | Supports | Documentation is HTML, not PDF. |
| 11 Software | Not Applicable | No non-web software component. |
| 12 Documentation and support services | Supports | Accessible HTML documentation and an email support channel. |
| 13 ICT providing relay or emergency service access | Not Applicable | Not a relay or emergency service. |
---
Known limitations and roadmap
- The application is not covered. The ACR for the assessment platform is issued
against the running product as its interfaces ship. See the roadmap.
- No third-party audit. All findings here are from our own automated and manual
testing.
- No assistive-technology user testing. We have tested with screen readers; we have
not run sessions with people who use them daily. That is the difference between technical conformance and usability, and we do not want to blur it.
- Screen reader coverage is narrow. VoiceOver on Safari has been exercised
thoroughly; JAWS and NVDA have not been part of routine testing.
Reporting a barrier
Email [email protected]. We acknowledge within two business days and give you a remediation plan even when the fix will take longer. If a barrier blocks a student from completing an assessment, tell us that in the subject line and we will treat it with the urgency of a production outage.