CaseLeadCaseLead
Accessibility Conformance Report

VPAT® 2.5 — WCAG 2.1 Edition (Draft)

CaseLead publishes this conformance report as a working draft so procurement teams can see our current state honestly — including what has not yet been formally verified.

Product information

Terms used

Supports — functionality meets the criterion. Partially Supports — some functionality does not meet the criterion, or conformance has not been formally verified (remarks say which). Does Not Support — majority of functionality does not meet it. Not Applicable — criterion not relevant to the product.

Table 1: WCAG 2.1 Level A

CriterionWebsiteApplicationRemarks
1.1.1 Non-text Content ASupportsPartially SupportsWebsite images carry alt text. Application: primary controls labeled; some icon-only buttons and chart visuals need text alternatives.
1.2.1 Audio-only / Video-only ANot ApplicablePartially SupportsApp plays evidence media as-is; system-generated transcripts accompany processed audio but are not positioned as captions.
1.2.2 Captions (Prerecorded) ANot ApplicablePartially SupportsEvidence video is source material; transcripts available when processed, not synchronized captions.
1.2.3 Audio Description / Media Alternative ANot ApplicablePartially SupportsVision-model descriptions exist for processed imagery; not a formal audio-description track.
1.3.1 Info and Relationships ASupportsPartially SupportsWebsite uses semantic headings/landmarks/labels. Application panels use semantic controls in most views; some list/card structures rely on visual grouping — remediation in progress.
1.3.2 Meaningful Sequence ASupportsPartially SupportsDOM order follows reading order on the website; app verified in main panels, not yet across all drawers/modals.
1.3.3 Sensory Characteristics ASupportsSupportsInstructions do not rely on shape/position alone.
1.4.1 Use of Color ASupportsPartially SupportsSeverity and status use color plus text labels in most views; timeline lane markers under review for color-only meaning.
1.4.2 Audio Control ANot ApplicableSupportsNo auto-playing audio.
2.1.1 Keyboard ASupportsPartially SupportsWebsite fully keyboard operable. App: forms, chat, and navigation operable; some custom cards/graph interactions need keyboard equivalents.
2.1.2 No Keyboard Trap ASupportsPartially SupportsNo traps found in walkthroughs; formal AT verification pending.
2.1.4 Character Key Shortcuts ANot ApplicableSupportsNo single-character global shortcuts.
2.2.1 Timing Adjustable ASupportsPartially SupportsNo content timeouts on the site. App sessions expire per security policy (CJIS); re-authentication preserves work in progress in most flows.
2.2.2 Pause, Stop, Hide ASupportsSupportsAnimations respect prefers-reduced-motion; no auto-updating carousels.
2.3.1 Three Flashes ASupportsSupportsNo flashing content.
2.4.1 Bypass Blocks APartially SupportsPartially SupportsLandmark navigation available; explicit skip links being added.
2.4.2 Page Titled ASupportsSupportsDescriptive titles on all pages.
2.4.3 Focus Order ASupportsPartially SupportsLogical on the website; app modals/drawers under focus-management review.
2.4.4 Link Purpose (In Context) ASupportsSupportsDescriptive link and button text.
2.5.1 Pointer Gestures ASupportsPartially SupportsNo path-based gestures required; graph pan/zoom has button equivalents in most views.
2.5.2 Pointer Cancellation ASupportsSupportsActions trigger on up-event.
2.5.3 Label in Name ASupportsPartially SupportsVisible labels match accessible names on the site; app custom controls being verified.
2.5.4 Motion Actuation ANot ApplicableNot ApplicableNo motion-based input.
3.1.1 Language of Page ASupportsSupportslang="en" declared.
3.2.1 On Focus ASupportsSupportsFocus does not trigger context changes.
3.2.2 On Input ASupportsSupportsInput does not auto-submit or change context.
3.3.1 Error Identification ASupportsPartially SupportsForm errors announced via live region on the site; app error messaging consistent in main flows, under review elsewhere.
3.3.2 Labels or Instructions ASupportsPartially SupportsPersistent labels on website forms; most app forms labeled, icon-only inputs being remediated.
4.1.1 Parsing ASupportsSupportsValid, well-formed markup (criterion obsolete in WCAG 2.2; reported for 2.1 completeness).
4.1.2 Name, Role, Value ASupportsPartially SupportsNative elements preferred on the website. App has some div-based interactive cards pending role/name remediation — the known largest gap.
4.1.3 Status Messages AASupportsPartially Supportsaria-live on site form status; app toasts being converted to live regions.

Table 2: WCAG 2.1 Level AA

CriterionWebsiteApplicationRemarks
1.2.4 Captions (Live) AANot ApplicableNot ApplicableNo live media.
1.2.5 Audio Description AANot ApplicablePartially SupportsSee 1.2.3 — evidence media is source material.
1.3.4 Orientation AASupportsSupportsNo orientation lock.
1.3.5 Identify Input Purpose AASupportsPartially Supportsautocomplete attributes on website forms; app login fields covered, remainder under review.
1.4.3 Contrast (Minimum) AAPartially SupportsPartially SupportsDark themes target 4.5:1; some muted secondary text measured below target — palette remediation scheduled.
1.4.4 Resize Text AASupportsPartially SupportsRelative units; app dense tables usable at 200% with horizontal scroll, formal verification pending.
1.4.5 Images of Text AASupportsSupportsText rendered as text; product screenshots are illustrative.
1.4.10 Reflow AASupportsPartially SupportsWebsite reflows to 320px. App is a dense desktop workspace; primary flows reflow, data-grid views scroll horizontally by design.
1.4.11 Non-text Contrast AAPartially SupportsPartially SupportsFocus indicators and key controls meet 3:1 in most components; audit pending.
1.4.12 Text Spacing AASupportsSupportsNo clipping under adjusted spacing in sampled views.
1.4.13 Content on Hover or Focus AASupportsPartially SupportsSite tooltips dismissible/persistent; app hover previews being verified for dismissability.
2.4.5 Multiple Ways AASupportsSupportsNavigation + search on the site; app offers nav, search, and cross-links.
2.4.6 Headings and Labels AASupportsSupportsDescriptive headings and labels.
2.4.7 Focus Visible AASupportsPartially SupportsVisible focus on the website; app custom components under review.
3.1.2 Language of Parts AASupportsSupportsContent is English; evidence text displayed verbatim.
3.2.3 Consistent Navigation AASupportsSupportsConsistent nav across pages/panels.
3.2.4 Consistent Identification AASupportsSupportsConsistent icons/labels for repeated functions.
3.3.3 Error Suggestion AASupportsPartially SupportsSite forms suggest corrections; app coverage varies by flow.
3.3.4 Error Prevention (Legal/Financial/Data) AANot ApplicableSupportsDestructive/irreversible actions require confirmation; evidence itself is read-only to the platform.

Section 508 & EN 301 549

Revised Section 508 incorporates WCAG 2.0 A/AA, which the tables above cover as a superset (WCAG 2.1). Hardware chapters are not applicable (CaseLead is software; agency-supplied hardware is out of scope). Chapter 6 (support documentation and services): product documentation is delivered in accessible HTML; support is provided by humans through agency channels. An EN 301 549 mapping is available on request.

Legal disclaimer

This is a good-faith draft self-assessment prepared by CaseLead, provided for transparency ahead of formal third-party audit. It describes the product as evaluated on the report date and is not a certification. "VPAT" is a registered trademark of the Information Technology Industry Council (ITI). A deployment-specific, finalized Accessibility Conformance Report — updated after formal audit and remediation — is provided to purchasing agencies during procurement.

For procurement files: print or save this page as PDF. To request the finalized post-audit VPAT, evidence of remediation progress, or an EN 301 549 mapping, use the contact form.

← Accessibility statement · caselead.ai