A public record should be usable without guessing how the page works.
CVPRO aims for WCAG 2.2 Level AA across its public site. That is a design and testing target, not a claim of certification or a promise that every barrier has already been found.
The basics should work before decoration does.
Accessibility is checked across navigation, reading order, interaction and responsive layout, including the parts most likely to fail when a page becomes more interactive.
Keyboard and focus
Navigation, accordions, tabs, filters and form controls should be reachable and operable without a pointer, with a visible focus indicator.
Structure and names
Pages use one visible primary heading, labelled controls and semantic regions so assistive technology receives more than visual position.
Contrast and resizing
Text and controls are designed for contrast, zoom and narrow-screen reflow without requiring horizontal page scrolling.
Motion and timing
Reduced-motion preferences are respected. Core information does not depend on animation, hover or a short time limit.
Tell us the page, task and barrier.
Include the page address, what you were trying to do, and the browser or assistive technology involved if you are comfortable sharing it. Do not send a career record merely to report an accessibility issue.
Current known limit
Downloadable DOCX and PDF samples are separate documents and may behave differently from the HTML pages. If one is not usable, ask for the same information in another format.
Response route
Email [email protected] with “CVPRO accessibility barrier” in the subject. We will investigate the specific task rather than ask you to diagnose the code.