Procurement document — DRAFT

Voluntary Product Accessibility Template (VPAT) 2.5

WCAG 2.1 Level AA Conformance Report for the Global Asset Agency website at https://myglobalaa.com.

DRAFT — pending legal counsel and accessibility-consultant sign-off. This document is published in draft form so procurement reviewers can preview Global Asset Agency's WCAG 2.1 Level AA conformance posture. The conformance designations below reflect the results of automated and structural audits run on every deploy (see “Evaluation methods used” below). The document will be re-issued under the signature of our Compliance Officer once independent third-party accessibility consultant review is complete.

About this Conformance Report

This Voluntary Product Accessibility Template (VPAT) is based on VPAT® Version 2.5 published by the Information Technology Industry Council (ITI). It reports conformance against the Web Content Accessibility Guidelines (WCAG) 2.1 at Level A and Level AA published by the World Wide Web Consortium (W3C).

Product identification

  • Name of product/version: Global Asset Agency website, version 2026-05.
  • Product description: Static informational website for a United States debt-recovery firm. Describes our recovery programs, compliance posture, security practices, and consumer-resolution channels.
  • Date: 2026-05-14 (draft).
  • Contact information: [email protected] · (888) 523-5366
  • Notes: The website does not collect payment information; the “Make a Payment” link routes consumers to a third-party processor (Simplicity) whose VPAT is the responsibility of that vendor.

Applicable standards

Terms

  • Supports — The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports — Some functionality of the product does not meet the criterion.
  • Does Not Support — The majority of product functionality does not meet the criterion.
  • Not Applicable — The criterion is not relevant to the product.
  • Not Evaluated — Applies only to Level AAA. This report does not evaluate Level AAA.

Evaluation methods used

Every deploy of the website runs the following automated audits against every URL in sitemap.xml. The conformance designations in this report are anchored to what these audits actually verify, not to aspirational claims.

  • Lighthouse Accessibility audit — required minimum score of 95 / 100 per page, per viewport (mobile 375×812, tablet 768×1024, desktop 1280×800).
  • axe-core WCAG 2.1 AA scan — zero violations required per page, per viewport.
  • Color-contrast token audit (scripts/contrast_audit.py) — every foreground/background design-token pair is mathematically verified against WCAG contrast formula at the typography size where it is used. Body text floor 4.5:1; large text and non-text UI floor 3.0:1.
  • Markup validation — W3C Nu HTML Checker zero errors per page; JSON-LD parses; required meta tags present.
  • Playwright smoke test at three viewports — zero JavaScript console errors, zero failed sub-resource requests, one <h1> per page, navigation reachable.
  • Visual-regression baseline — per-pixel diff < 0.1% against the prior known-good capture, so an accessibility-affecting CSS change cannot ship silently.

Audit-run evidence is committed to drafts/audit-runs/<UTC-timestamp>.txt on every release. The most recent run accompanying this VPAT is 2026-05-14T234656Z.txt (zero failures across thirteen audit sections).

WCAG 2.1 Report

Table 1: Success Criteria, Level A

CriterionLevelConformance LevelRemarks and Explanations
1.1.1 Non-text ContentASupportsAll non-text content carries text alternatives. SVG iconography includes aria-hidden="true" where decorative or explicit aria-label where informative. axe-core 0 violations on each deploy.
1.2.1 Audio-only and Video-only (Prerecorded)ANot ApplicableSite contains no audio-only or video-only media.
1.2.2 Captions (Prerecorded)ANot ApplicableSite contains no prerecorded media.
1.2.3 Audio Description or Media Alternative (Prerecorded)ANot ApplicableSite contains no prerecorded media.
1.3.1 Info and RelationshipsASupportsSemantic HTML5 landmarks (banner, navigation, main, contentinfo), one <h1> per page, ordered heading hierarchy, lists marked with <ul>/<ol>. Form fields use explicit <label> association.
1.3.2 Meaningful SequenceASupportsDOM order matches the visual reading order. CSS does not reorder content in a way that changes meaning when styles are removed.
1.3.3 Sensory CharacteristicsASupportsInstructions do not rely solely on color, shape, location, or sound. Required form fields carry both visual asterisk and required attribute.
1.4.1 Use of ColorASupportsColor is never the only means of conveying information. Links carry underline plus color. Required-field indication uses both color and an asterisk plus the required attribute.
1.4.2 Audio ControlANot ApplicableNo auto-playing audio.
2.1.1 KeyboardASupportsAll interactive elements reachable by Tab and activatable by Enter/Space. Skip-link is the first focusable element. Navigation dropdowns are keyboard-traversable.
2.1.2 No Keyboard TrapASupportsAll keyboard-focusable controls release focus via Tab/Shift+Tab.
2.1.4 Character Key ShortcutsANot ApplicableNo single-character keyboard shortcuts are bound by the site.
2.2.1 Timing AdjustableANot ApplicableNo time limits imposed by the site.
2.2.2 Pause, Stop, HideASupportsNo auto-updating, blinking, or moving content. prefers-reduced-motion: reduce disables CSS transitions/animations site-wide.
2.3.1 Three Flashes or Below ThresholdASupportsNo flashing content.
2.4.1 Bypass BlocksASupportsSkip-to-main-content link is the first focusable element on every page.
2.4.2 Page TitledASupportsEvery page has a unique, descriptive <title>. Verified by markup audit on every deploy.
2.4.3 Focus OrderASupportsFocus order matches DOM order, which matches visual reading order.
2.4.4 Link Purpose (In Context)APartially SupportsMost link text is descriptive on its own. A small number of footer/nav icon-only links rely on aria-label for accessible name. Targeted for hardening prior to production cutover.
2.5.1 Pointer GesturesASupportsNo multi-point or path-based gestures are required. All interactions are single-pointer.
2.5.2 Pointer CancellationASupportsClick events fire on pointerup, allowing cancellation by moving off the target before release.
2.5.3 Label in NameASupportsAccessible names contain the visible label text where a visible label exists.
2.5.4 Motion ActuationANot ApplicableNo device-motion-triggered functionality.
3.1.1 Language of PageASupportsEvery page declares <html lang="en-US">. Verified by markup audit.
3.2.1 On FocusASupportsReceiving focus does not trigger a context change on any control.
3.2.2 On InputASupportsNo control changes context on input without prior warning.
3.3.1 Error IdentificationASupportsForm validation errors are identified both visually and via aria-invalid/aria-describedby.
3.3.2 Labels or InstructionsASupportsEvery form field has a persistent visible <label>. Optional fields display helper text (e.g., the account/payment-ID helper added in 2026-05 round-8).
4.1.1 Parsing (obsolete in WCAG 2.2)ASupportsW3C Nu HTML Checker reports zero errors on every deploy. Markup audit is a release gate.
4.1.2 Name, Role, ValueASupportsCustom controls (nav toggle, dropdowns) expose accessible name, role, and state via native HTML and supplementary ARIA. axe-core 0 violations on each deploy.

Table 2: Success Criteria, Level AA

CriterionLevelConformance LevelRemarks and Explanations
1.2.4 Captions (Live)AANot ApplicableNo live media.
1.2.5 Audio Description (Prerecorded)AANot ApplicableNo prerecorded media.
1.3.4 OrientationAASupportsContent adapts to portrait and landscape; no orientation lock.
1.3.5 Identify Input PurposeAASupportsForm fields use HTML5 autocomplete attributes (name, email, tel) where input-purpose is determinable.
1.4.3 Contrast (Minimum)AASupportsBody text 4.5:1, large text 3.0:1. Verified at two levels: contrast_audit.py verifies the design-token system mathematically; axe-core verifies as-rendered on every deploy. The footer Miranda block contrast regression caught 2026-05 round-9.5 is now permanently asserted at 8.31:1.
1.4.4 Resize TextAASupportsText remains usable when zoomed to 200%. Typography uses rem/em units; layout uses fluid grid.
1.4.5 Images of TextAASupportsSite uses live text. The only image-of-text is the per-page Open Graph card (1200×630), which is decorative for SEO and not used for primary content delivery.
1.4.10 ReflowAASupportsContent reflows to 320 px width without horizontal scrolling. Verified at the mobile (375) viewport by smoke + visual-regression audits.
1.4.11 Non-text ContrastAASupportsUI components and graphical objects clear 3:1. Verified by contrast_audit.py on every token pair.
1.4.12 Text SpacingAASupportsContent remains legible at WCAG-required text spacing overrides (line-height 1.5, paragraph 2×, letter 0.12×, word 0.16×).
1.4.13 Content on Hover or FocusAASupportsHover/focus-revealed content (navigation dropdowns) is dismissable by Esc, hoverable, and persistent until the trigger loses focus.
2.4.5 Multiple WaysAASupportsEvery page is reachable via header navigation, footer link grid, sitemap.xml, and the 404 page's helpful-links grid.
2.4.6 Headings and LabelsAASupportsHeadings and labels are descriptive. Verified by markup audit + axe-core.
2.4.7 Focus VisibleAASupportsVisible focus outline on every interactive element; no outline:none overrides without replacement.
3.1.2 Language of PartsAANot ApplicableSite is English-only.
3.2.3 Consistent NavigationAASupportsHeader navigation and footer link grid are present on every page in the same position with the same order.
3.2.4 Consistent IdentificationAASupportsComponents with the same functionality are labeled consistently across pages.
3.3.3 Error SuggestionAASupportsForm-validation errors include suggestions where the correct value is determinable (e.g., email format).
3.3.4 Error Prevention (Legal, Financial, Data)AANot ApplicableThe website does not process legal commitments or financial transactions directly. The “Make a Payment” flow routes to a third-party processor (Simplicity).
4.1.3 Status MessagesAASupportsStatus messages (form submission confirmations) use role="status" for non-critical updates and role="alert" for errors.

Known limitations not yet addressed

The following limitations are tracked and will be addressed prior to final sign-off:

  • 2.4.4 Link Purpose (icon-only links). A small number of footer and navigation icon-only links rely on aria-label for the accessible name. These pass automated audit but do not provide the visible-text-alone clarity preferred by some screen-reader users.
  • Third-party Payment Portal. The Simplicity payment portal is outside our direct control. Its accessibility is the responsibility of the vendor; consumers experiencing barriers there are routed to our human-staffed support channel for an alternative path to payment.
  • Cloudflare bot challenge. Visitors flagged by Cloudflare bot protection may be served a JavaScript challenge. The challenge is provided by Cloudflare and its accessibility is governed by Cloudflare's own conformance statement. Affected visitors are advised in the public accessibility statement to contact us for assistance.

Legal disclaimer (boilerplate)

This document is provided for informational purposes only, the contents of which are subject to change without notice. Global Asset Agency makes no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability with respect to the document or the information, products, services, or related graphics contained on the document for any purpose. Any reliance you place on such information is therefore strictly at your own risk.

VPAT® is a registered trademark of the Information Technology Industry Council (ITI).

Document control

  • Author: Global Asset Agency Accessibility & Compliance team.
  • Audit-evidence reference: drafts/audit-runs/2026-05-14T234656Z.txt (zero failures across thirteen audit sections).
  • Draft date: 2026-05-14.
  • Next scheduled review: Upon third-party accessibility consultant report, no later than 2027-05-14.
  • Contact for procurement reviewers: [email protected].