WCAG 2.2 Conformance Report

This report describes how the netex.consulting website measures against the Web Content Accessibility Guidelines (WCAG) 2.2. It follows the structure of a VPAT 2.5 (WCAG edition) and covers every Level A and Level AA success criterion, plus the Level AAA criteria we have chosen to adopt. It is a companion to our plain-language Accessibility statement.

Report information

• Product: netex.consulting (marketing website, static export)
• Report date: July 4, 2026
• Standard evaluated: WCAG 2.2, Level A and Level AA
• Evaluation methods: axe-core automated scans run against every route on each release; scripted Playwright keyboard-navigation tests; and a manual audit covering keyboard-only operation and screen-reader passes with NVDA and VoiceOver.
• Contact: admin@netex.consulting

How to read this report

Each success criterion is rated with one of three values:

• Supports — the site meets the criterion across the pages evaluated.
• Partially Supports — the site meets the criterion for most content, with the noted exception.
• Not Applicable — the criterion does not apply to any content on this site.

WCAG 2.2 removed success criterion 4.1.1 Parsing, so it is not listed below.

Table 1 — Level A

Criterion	Conformance Level	Remarks
1.1.1 Non-text Content	Supports	Informative images and icons carry text alternatives; decorative graphics are hidden from assistive technology.
1.2.1 Audio-only and Video-only (Prerecorded)	Not Applicable	The site publishes no prerecorded audio-only or video-only media.
1.2.2 Captions (Prerecorded)	Not Applicable	The site publishes no prerecorded synchronized media.
1.2.3 Audio Description or Media Alternative (Prerecorded)	Not Applicable	The site publishes no prerecorded synchronized media.
1.3.1 Info and Relationships	Supports	Structure is conveyed with semantic HTML landmarks, headings, lists, and programmatic form labels.
1.3.2 Meaningful Sequence	Supports	The DOM and reading order match the visual order on every page.
1.3.3 Sensory Characteristics	Supports	Instructions do not rely on shape, size, position, or color alone.
1.4.1 Use of Color	Supports	Color is never the only means of conveying information; links and states carry additional cues.
1.4.2 Audio Control	Not Applicable	No audio plays automatically on the site.
2.1.1 Keyboard	Supports	All interactive controls are operable with a keyboard.
2.1.2 No Keyboard Trap	Supports	Keyboard focus can move into and out of every component, including menus and dialogs.
2.1.4 Character Key Shortcuts	Not Applicable	The site implements no single-character key shortcuts.
2.2.1 Timing Adjustable	Not Applicable	The site sets no time limits on any interaction.
2.2.2 Pause, Stop, Hide	Partially Supports	Decorative tickers and background motion start automatically; they honor the reduced-motion preference but do not expose an on-screen pause control.
2.3.1 Three Flashes or Below Threshold	Supports	No content flashes more than three times per second.
2.4.1 Bypass Blocks	Supports	A skip link and landmark regions let users bypass repeated navigation.
2.4.2 Page Titled	Supports	Each route has a unique, descriptive page title.
2.4.3 Focus Order	Supports	Focus order follows a logical, meaningful sequence.
2.4.4 Link Purpose (In Context)	Supports	Link text, with its context, makes each link's purpose clear.
2.5.1 Pointer Gestures	Supports	Every control operates with a single tap or click; no path-based or multipoint gestures are required.
2.5.2 Pointer Cancellation	Supports	Controls activate on the up event, so a pointer press can be moved off and cancelled.
2.5.3 Label in Name	Supports	Each control's accessible name contains its visible label text.
2.5.4 Motion Actuation	Not Applicable	No functionality is triggered by device or user motion.
3.1.1 Language of Page	Supports	The page language is declared as English on the root element.
3.2.1 On Focus	Supports	Moving focus to a component does not trigger a change of context.
3.2.2 On Input	Supports	Changing a form control does not automatically cause a change of context.
3.2.6 Consistent Help	Supports	Contact and help links appear in a consistent location across pages.
3.3.1 Error Identification	Supports	Contact-form errors are identified in text and exposed programmatically.
3.3.2 Labels or Instructions	Supports	Every form field has a visible label and, where needed, an instruction.
3.3.7 Redundant Entry	Not Applicable	The contact form is a single step and never asks for the same information twice.
4.1.2 Name, Role, Value	Supports	Custom and native controls expose an accurate name, role, state, and value.

Table 2 — Level AA

Criterion	Conformance Level	Remarks
1.2.4 Captions (Live)	Not Applicable	The site publishes no live synchronized media.
1.2.5 Audio Description (Prerecorded)	Not Applicable	The site publishes no prerecorded synchronized media.
1.3.4 Orientation	Supports	Content is not locked to a single display orientation.
1.3.5 Identify Input Purpose	Supports	Contact-form fields use the appropriate autocomplete tokens for name and email.
1.4.3 Contrast (Minimum)	Supports	Text meets or exceeds the 4.5:1 ratio, and large text the 3:1 ratio.
1.4.4 Resize Text	Supports	Text can be resized to 200% without loss of content or function.
1.4.5 Images of Text	Supports	Real text is used throughout; images of text are limited to logos.
1.4.10 Reflow	Supports	Content reflows to a 320 CSS pixel width without horizontal scrolling.
1.4.11 Non-text Contrast	Supports	Interface components and focus indicators meet the 3:1 contrast ratio.
1.4.12 Text Spacing	Supports	No content or function is lost when users increase text spacing.
1.4.13 Content on Hover or Focus	Supports	Content revealed on hover or focus is dismissable, hoverable, and stays visible until dismissed.
2.4.5 Multiple Ways	Supports	Pages are reachable through the main navigation, the footer, and in-content links.
2.4.6 Headings and Labels	Supports	Headings and labels describe their topic or purpose.
2.4.7 Focus Visible	Supports	A visible focus indicator is shown on every interactive element.
2.4.11 Focus Not Obscured (Minimum)	Supports	A focused element is not fully hidden by the sticky header or other content.
2.5.7 Dragging Movements	Not Applicable	No functionality requires a dragging movement.
2.5.8 Target Size (Minimum)	Supports	Pointer targets are at least 24 by 24 CSS pixels, with adequate spacing.
3.1.2 Language of Parts	Supports	Page content is in English, and any inline passage in another language carries a lang attribute.
3.2.3 Consistent Navigation	Supports	Navigation is presented in the same relative order on every page.
3.2.4 Consistent Identification	Supports	Components with the same function are identified consistently across pages.
3.3.3 Error Suggestion	Supports	When a form entry is rejected, the site suggests how to correct it.
3.3.4 Error Prevention (Legal, Financial, Data)	Not Applicable	The site has no legal, financial, or data-modifying transactions to reverse or confirm.
3.3.8 Accessible Authentication (Minimum)	Not Applicable	The marketing site has no login or authentication step.
4.1.3 Status Messages	Supports	Form success and error messages are announced through ARIA live regions.

Table 3 — Adopted Level AAA

We do not claim full Level AAA conformance. We adopt the following AAA criteria where they measurably improve the experience.

Criterion	Conformance Level	Remarks
1.4.6 Contrast (Enhanced)	Supports	Primary body text meets the 7:1 enhanced contrast ratio.
2.3.3 Animation from Interactions	Supports	Motion triggered by scrolling or interaction is removed when a reduced-motion preference is set.
2.4.13 Focus Appearance	Supports	The keyboard focus indicator meets the enhanced size and contrast thresholds.
2.5.5 Target Size (Enhanced)	Supports	Primary actions meet the 44 by 44 CSS pixel enhanced target size.