Assembled from the vendor's July 2023 ACR (WCAG 2.0) plus WTAMU-supplied gaps; expanded to cover WCAG 2.1 Level A/AA. Final statuses require verification via manual testing with assistive technologies (NVDA/JAWS + Chrome; VoiceOver + Safari; TalkBack + Chrome), Windows High Contrast, 200% zoom, reflow, required text-spacing presets, keyboard-only operation, and mobile pointer interactions.
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
1.1.1 Non‑text Content (A) | Partially Supports | Some icons not visible with custom themes; user‑uploaded images may lack alt text; some third‑party payment controls/images not visible in Windows High Contrast or missing alt. Plan: enforce alt entry, audit icon/SVG sets, coordinate with payment vendors. |
1.2.1 Audio‑only and Video‑only (Prerecorded) (A) | Not Applicable | Core user journeys do not rely on prerecorded media. |
1.2.2 Captions (Prerecorded) (AA) | Not Applicable | No prerecorded media required for core workflows. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (A) | Not Applicable | No prerecorded media required for core workflows. |
1.2.4 Captions (Live) (AA) | Partially Supports | Live video for virtual auctions requires end‑user‑provided captions; integrate/document live captioning workflows and vendor options. |
1.3.1 Info and Relationships (A) | Partially Supports | ARIA misuse (aria-hidden on containers), non‑semantic headings, list/table misuse, active states not conveyed; third‑party disabled state. Plan: semantic audit, ARIA fixes, list/heading hygiene; vendor outreach. |
1.3.2 Meaningful Sequence (A) | Partially Supports | DOM vs visual order mismatches on some screens; normalize to visual reading order. |
1.3.3 Sensory Characteristics (A) | Supports | Instructions do not rely solely on color, shape, or position (verify across flows). |
1.3.4 Orientation (AA) | Supports | Responsive layouts support both orientations (verify on phones/tablets). |
1.3.5 Identify Input Purpose (AA) | Partially Supports | Some fields lack appropriate autocomplete tokens; add tokens to support purpose identification. |
1.4.1 Use of Color (A) | Partially Supports | Third‑party payment imagery not visible in Windows High Contrast; pursue vendor fixes or alternatives. |
1.4.2 Audio Control (A) | Not Evaluated | Embedded players (if any) must provide independent audio control; verify. |
1.4.3 Contrast (Minimum) (AA) | Partially Supports | User‑selected themes can reduce contrast; some error text lacks sufficient contrast; enforce minimum contrast and update error styles. |
1.4.4 Resize Text (AA) | Partially Supports | Some dialog content obscured at 200% zoom; redesign overlays/dialogs to avoid clipping/overlap. |
1.4.5 Images of Text (AA) | Supports | UI avoids images of text; verify marketing/content areas. |
1.4.10 Reflow (AA) | Partially Supports | Mobile order summary appears adjacent but is DOM‑bottom; overlays may not reflow cleanly; refactor layout/CSS for narrow viewports. |
1.4.11 Non‑text Contrast (AA) | Partially Supports | Iconography and focus indicators may lack sufficient contrast in some themes or HC; audit tokens and ensure visible focus. |
1.4.12 Text Spacing (AA) | Partially Supports | Requires verification under required spacing presets; fix truncation/overlap where present. |
1.4.13 Content on Hover or Focus (AA) | Partially Supports | Tooltips not keyboard accessible and may dismiss on hover/focus changes; replace with accessible popovers and manage dismissal. |
2.1.1 Keyboard (A) | Partially Supports | Non‑sequential tab order on some forms; tooltips inaccessible by keyboard; audit and fix tab sequence and triggers. |
2.1.2 No Keyboard Trap (A) | Supports | Modals/overlays provide escape/close controls; verify trapping and return focus consistently. |
2.1.4 Character Key Shortcuts (A) | Not Applicable | No single‑character key shortcuts. |
2.2.1 Timing Adjustable (A) | Partially Supports | Session/checkout/auction timeouts need warnings and extension mechanisms; document behavior and add extend controls. |
2.2.2 Pause, Stop, Hide (A) | Partially Supports | Auto‑updating auction pages need pause/refresh rate controls and appropriate live region usage. |
2.3.1 Three Flashes or Below Threshold (A) | Supports | No flashing content present. |
2.4.1 Bypass Blocks (A) | Does Not Support | Skip to content link not present; add global skip links. |
2.4.2 Page Titled (A) | Partially Supports | Some pages lack unique/descriptive titles; standardize dynamic titles across routes. |
2.4.3 Focus Order (A) | Partially Supports | Mobile order summary DOM vs visual order; prev/next reversed in DOM; loading messages do not receive focus; align DOM and focus behaviors. |
2.4.4 Link Purpose (In Context) (A) | Partially Supports | Some third‑party controls unclear; some form controls differ in visual vs DOM order; clarify labels/aria‑labels and fix order. |
2.4.5 Multiple Ways (AA) | Supports | Sitemap/search/contextual navigation available (verify completeness). |
2.4.6 Headings and Labels (AA) | Partially Supports | Some screens include multiple H1 elements and empty headings; enforce single‑H1 policy and lint headings. |
2.4.7 Focus Visible (AA) | Partially Supports | Focus indicators insufficient under some themes/HC; strengthen visible focus styles. |
3.1.1 Language of Page (A) | Supports | HTML lang set site‑wide (verify across pages/templates). |
3.1.2 Language of Parts (AA) | Not Evaluated | Mixed‑language content uncommon; verify where present. |
3.2.1 On Focus (A) | Supports | No unexpected context changes on focus (verify components). |
3.2.2 On Input (A) | Partially Supports | Forms that reveal/hide fields must announce changes and avoid focus loss; add ARIA live/status cues. |
3.2.3 Consistent Navigation (AA) | Supports | Navigation is consistent across pages (verify all layouts). |
3.2.4 Consistent Identification (AA) | Supports | Components with the same function are identified consistently. |
3.3.1 Error Identification (A) | Partially Supports | Some errors are low contrast and may lack programmatic association; improve error styles and link messages to fields. |
3.3.2 Labels or Instructions (A) | Partially Supports | Some fields missing labels; some third‑party tooltips not exposed to AT; add labels/help text and accessible tooltips. |
3.3.3 Error Suggestion (AA) | Partially Supports | Provide constructive suggestions and programmatic cues for correction. |
3.3.4 Error Prevention (Legal, Financial, Data) (AA) | Supports | Review/confirmation pages are provided for transactions (verify completeness). |
4.1.1 Parsing (A) | Not Evaluated | Modern frameworks reduce parsing errors; automated validation still required. |
4.1.2 Name, Role, Value (A) | Partially Supports | Some custom UI components lack proper programmatic name/role/state; fix component library and patterns. |
4.1.3 Status Messages (AA) | Partially Supports | Loading/interstitial messages not announced; add role=status/aria-live and focus management. |
Section | Conformance Level | Remarks and Explanations |
---|---|---|
302 Functional Performance Criteria | Partially Supports | Gaps for blind/low‑vision users around headings structure, focus visibility, status messages, non‑text contrast; third‑party payment widgets require fixes. |
501 Software | Partially Supports | See WCAG mapping above; remediate A/AA gaps in components and page templates. |
504 Authoring Tools | Partially Supports | Authoring UI should require alt text, encourage semantic headings/lists, and warn on low contrast. Add validators and guidance. |
602 Support Documentation | Not Evaluated | Confirm help docs and PDFs are accessible (headings, alt text, keyboard, tagging). |
603 Support Services | Not Evaluated | Confirm accessible support channels and accommodation processes. |
VPAT® is a registered service mark of the Information Technology Industry Council (ITI). This document follows the VPAT 2.5Rev INT structure for drafting purposes and will need finalization on the official template.
Did you know you can try our essentials, plus or professional plans for free!
Start a free trial Sign up for a demo