Accessibility Conformance Report
VPAT — WCAG Edition
Report date: 21 October 2026
This Accessibility Conformance Report is based on the ITI VPAT® Version 2.5 WCAG Edition. “Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI).
Product information
- Name of product / version: avcoding.com (public marketing website), as published 21 October 2026
- Product description: Static marketing and information site for AV Coding LLC (Crestron programming and AV design services), including scheduling via Calendly when Book a call is pressed.
- Contact: Email (subject line: Accessibility / VPAT)
- Related statement: Accessibility statement
Notes
- Scope: First-party commercial pages served from avcoding.com
(home, services, FAQ, about, work, privacy, accessibility, terms, and this report).
Development or demo routes such as
/foraging,/v01, and/world-testare out of scope. - Third parties: Calendly (Book a call popup), YouTube (privacy-enhanced player after play), and Web3Forms (form delivery) are outside AV Coding’s direct control. Where those components affect a criterion, the level is marked Partially Supports and phone/email alternatives are noted.
- Evaluation type: Self-assessment by AV Coding LLC. This is not a third-party certification audit. Levels reflect known design intent and documented limitations as of the report date.
- Conformance target: WCAG 2.1 Level A and Level AA for in-scope pages. WCAG 2.2 and Level AAA are not claimed in this report.
Evaluation methods used
- Manual keyboard-only navigation of in-scope pages and primary flows
- Semantic HTML and ARIA review of first-party components (landmarks, labels, dialogs)
- Visual review of focus indicators and text resize / larger-text control
- Automated checks (including Lighthouse accessibility category) as a supplement, not a sole source
- Inventory of third-party embeds and the accessibility statement’s known limitations
Applicable standards / guidelines
| Standard / Guideline | Included |
|---|---|
| WCAG 2.0 (ISO/IEC 40500) | Level A: Yes · Level AA: Yes · Level AAA: No |
| WCAG 2.1 | Level A: Yes · Level AA: Yes · Level AAA: No |
| WCAG 2.2 | No (not evaluated for this report) |
| Revised Section 508 / EN 301 549 | No (use a 508 or EU VPAT edition if those standards are required) |
Terms
Conformance levels use ITI’s recommended definitions:
- Supports: The functionality 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 product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: Used only for WCAG Level AAA (not used in this report).
WCAG 2.1 Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Meaningful images use alt text. Decorative scroll-world imagery is aria-hidden. The YouTube facade poster has a descriptive alt before play. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Supports | No audio-only or video-only first-party media. The homepage video is audiovisual and loads only after an explicit play action. |
| 1.2.2 Captions (Prerecorded) | Partially Supports | Captions for the embedded YouTube player depend on YouTube’s caption track for that video. AV Coding does not control the player UI after play. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Partially Supports | No separate first-party audio description track is published. Contact channels can supply an alternate description of the video content on request. |
| 1.3.1 Info and Relationships | Supports | Pages use landmarks, headings, lists, and labeled form controls. Section relationships are expressed in HTML rather than presentation alone. |
| 1.3.2 Meaningful Sequence | Supports | DOM order matches the reading order for primary content. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely on shape, size, or location alone. |
| 1.4.1 Use of Color | Supports | Color is not the sole means of conveying information; text labels and structure accompany status and links. |
| 1.4.2 Audio Control | Supports | No audio plays automatically. YouTube audio starts only after the visitor presses play. |
| 2.1.1 Keyboard | Partially Supports | First-party controls (navigation, theme, text size, cookie notice, forms, video facade) are keyboard operable. The Calendly popup opened by Book a call is third-party; keyboard behavior inside that popup is controlled by Calendly. Phone and email remain available without Calendly. |
| 2.1.2 No Keyboard Trap | Partially Supports | First-party UI does not trap keyboard focus. The cookie notice is a temporary dialog with Escape to decline. Focus behavior inside Calendly is third-party. |
| 2.1.4 Character Key Shortcuts | Supports | No single-character keyboard shortcuts are implemented by AV Coding on the commercial pages. |
| 2.2.1 Timing Adjustable | Supports | No session or content time limits are imposed by the site. |
| 2.2.2 Pause, Stop, Hide | Supports | Motion in the scroll-world is decorative. prefers-reduced-motion hides the backdrop and shortens CSS transitions. No essential information is conveyed only by moving content. |
| 2.3.1 Three Flashes or Below Threshold | Supports | Content does not flash above the general flash thresholds. |
| 2.4.1 Bypass Blocks | Supports | A skip link targets the main content landmark on every commercial page. |
| 2.4.2 Page Titled | Supports | Each page has a descriptive document title. |
| 2.4.3 Focus Order | Partially Supports | Focus order follows DOM order on first-party pages. Focus order inside Calendly after Book a call is third-party. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text and surrounding context identify purpose. Icon-only controls have accessible names. |
| 2.5.1 Pointer Gestures | Supports | No multipoint or path-based gestures are required for first-party functionality. |
| 2.5.2 Pointer Cancellation | Supports | Primary actions use standard click/activate patterns without down-event-only completion. |
| 2.5.3 Label in Name | Supports | Visible labels are included in accessible names for first-party controls. |
| 2.5.4 Motion Actuation | Supports | No features require device motion or shaking. |
| 3.1.1 Language of Page | Supports | html lang="en" is set on commercial pages. |
| 3.2.1 On Focus | Supports | Focus alone does not trigger unexpected context changes. |
| 3.2.2 On Input | Supports | Changing settings does not automatically submit forms or change context unexpectedly. |
| 3.3.1 Error Identification | Supports | Form validation errors are identified in text for contact and privacy request forms. |
| 3.3.2 Labels or Instructions | Supports | Form fields have associated labels; cookie and preference controls are named. |
| 4.1.1 Parsing | Supports | Pages are generated as well-formed HTML from a static site build. |
| 4.1.2 Name, Role, Value | Partially Supports | First-party custom controls expose name, role, and state (for example theme toggle aria-pressed, cookie dialog). Third-party Calendly and YouTube widgets after activation may not expose the same quality of name/role/value. |
WCAG 2.1 Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Supports | No live synchronized media is offered on the site. |
| 1.2.5 Audio Description (Prerecorded) | Partially Supports | No first-party audio description track is published for the homepage video. An alternate description is available on request via email. |
| 1.3.4 Orientation | Supports | Content is usable in portrait and landscape; orientation is not locked. |
| 1.3.5 Identify Input Purpose | Supports | Common personal-data fields use autocomplete tokens where applicable (for example name and email). |
| 1.4.3 Contrast (Minimum) | Supports | Primary text and interactive teal accents are designed for WCAG AA contrast on light and dark themes. Isolated decorative graphics are not relied on for essential text. |
| 1.4.4 Resize Text | Supports | Text can be resized with browser zoom. A larger-text control (about 130%) is also provided in the header. |
| 1.4.5 Images of Text | Supports | Essential copy is real text. Logos are excepted images; a text fallback is available if the logo image fails. |
| 1.4.10 Reflow | Supports | Layouts reflow for narrow viewports without requiring two-dimensional scrolling for primary reading content. |
| 1.4.11 Non-text Contrast | Supports | Focus indicators and UI boundaries are designed for sufficient contrast against adjacent colors. |
| 1.4.12 Text Spacing | Supports | Content remains usable when text spacing is increased within WCAG-defined ranges. |
| 1.4.13 Content on Hover or Focus | Supports | No essential additional content appears only on hover in a way that cannot be dismissed or is pointer-trapping. |
| 2.4.5 Multiple Ways | Supports | Pages are reachable via primary navigation, footer links, and the public sitemap. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe topic or purpose. |
| 2.4.7 Focus Visible | Supports | Keyboard focus is visibly indicated on interactive first-party controls. |
| 3.1.2 Language of Parts | Supports | Pages are English throughout; no mixed-language passages require separate lang markup. |
| 3.2.3 Consistent Navigation | Supports | Repeated navigation appears in a consistent relative order across commercial pages. |
| 3.2.4 Consistent Identification | Supports | Components with the same function (Book a call, theme toggle, cookie preference) are identified consistently. |
| 3.3.3 Error Suggestion | Supports | When a known correction is available (for example missing required fields), forms provide corrective guidance in text. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Site forms do not create legal or financial transactions. Privacy and contact submissions can be corrected by contacting AV Coding. |
| 4.1.3 Status Messages | Supports | Form success and error messages are exposed in a way assistive technologies can present without a focus change where implemented. |
Feedback and alternatives
If you encounter a barrier, email Email with the page URL and what you were trying to do. We will work on a fix or provide the information another way. Scheduling without Calendly is available by phone or email on the same pages as Book a call.