--- title: "Accessibility Statement | WCAG 2.2 AA Target and Gaps" description: "The conformance target for this site is WCAG 2.2 Level AA. This statement lists what has been done, the gaps we know about, and how to report a barrier." focus_keyword: "accessibility statement for this rv shop website" canonical: https://ocrv.me/accessibility/ kind: legal updated: 2026-07-29 source: OCRV Center --- # Accessibility at OCRV Center: Target, Known Gaps and Reporting > The target for this site is **WCAG 2.2 Level AA**. Conformance is **partial**, and the specific gaps are listed below rather than summarised. Statement last reviewed **15 July 2026**. ## Is the OCRV Center website accessible? The conformance target is WCAG 2.2 Level AA and the current state is partial conformance, with known gaps listed openly on this page. The Yorba Linda shop also accepts every enquiry by telephone or in person, so no service depends on being able to use this website at all. - Target: WCAG 2.2 Level AA, partial conformance today - Known gaps are listed individually, not summarised as a score - Every function of this site is also available by phone or at the counter - Barrier reports go to a person and get a written reply ### Key facts | Item | Value | | --- | --- | | Conformance target | WCAG 2.2 Level AA | | Current state | Partial conformance (Known gaps listed on this page) | | Statement reviewed | 15 July 2026 | | Statement version | 1.2 | | Non web alternative | Phone or counter (Every enquiry route works without this website) | This statement describes how accessible this website currently is, measured against a named standard, with the gaps written out rather than averaged away. A statement that claims full conformance and lists nothing is usually a statement nobody tested. ## The conformance target and where we stand The target for this site is the Web Content Accessibility Guidelines version 2.2 at Level AA. That is the level referenced by most public procurement in the United States and it is the right bar for a commercial site that people rely on while stressed and often on a phone. Current status is partial conformance, meaning most of the site meets the target and the specific places it does not are named below. This statement was last reviewed on 15 July 2026 and carries version 1.2. It is reviewed when the site structure changes materially, when a barrier is reported, and at least annually regardless. The date at the top of this page is the date it was actually checked rather than the date it was published. - Standard: WCAG 2.2, Level AA - Status: partial conformance, with named exceptions - Statement reviewed 15 July 2026, version 1.2 - Review triggers: structural change, a reported barrier, or annually ## What has been done deliberately The site is built as static pages, so text is present in the document rather than assembled by a script after load. Every page has one heading level one and a properly nested heading structure beneath it, which is what lets a screen reader user skim a two thousand word repair page instead of listening to all of it. Every page also has a plain markdown mirror, which some readers find easier than any styled page. Beyond structure: link text describes its destination rather than saying to click, colour contrast was checked against the Level AA ratios for both text and interface components, focus is visible on every interactive element, and nothing depends on hover alone. Tables of prices and comparisons carry proper headers and captions so a cell can be announced with its row and column meaning intact. - Static text in the document, not injected after load - One heading level one per page, with a nested outline below it - Descriptive link text, with no bare click here or read more anywhere - Contrast checked against Level AA ratios for text and interface elements - Visible focus indicators, keyboard reachable navigation, no hover only controls - A plain markdown mirror of every page for readers who prefer unstyled text ## Known limitations, listed individually These are the gaps we are aware of. Each one is a genuine failure against the target rather than a hypothetical risk, and each has a workaround stated so you are not left guessing. Naming them is more useful than a paragraph claiming ongoing commitment. 1. Older video in the media archive lacks captions and transcripts. Newer material is captioned. Ask for a description of any clip and you will get one in writing. 2. Wide tables, particularly the rate card and comparison tables, scroll horizontally on a narrow screen. The same figures appear as prose in the surrounding text, and the markdown mirror renders them without the scroll container. 3. The map link on the contact page opens a third party service whose accessibility we do not control. The full street address is written out on the page so the map is never required. 4. Estimate and invoice documents produced for a specific job are not currently tagged for screen reader navigation. Ask and the same content is sent as plain text or read to you over the phone. 5. A small number of older photographs carry alternative text that is accurate but shorter than it should be. Any image can be described in detail on request. ## How this was assessed Assessment combined automated checking with manual testing, because automated tools catch perhaps a third of real problems and confidently pass pages that are unusable. Automated checks run against the whole page set as part of the build, including a contrast check that fails the build on a token combination below the Level AA ratio. That is a gate rather than a report. Manual testing covered keyboard only navigation through the primary journeys, screen reader passes on a representative sample including a long job page and the quote form, text scaling to two hundred percent, and reflow at a narrow viewport width. Sampling rather than exhaustive testing is why this statement claims partial conformance instead of full. - Automated checks in the build, including a contrast gate that blocks a release - Keyboard only walkthroughs of the primary journeys - Screen reader passes on a sample of long content pages and the form - Text scaling to two hundred percent and reflow at narrow widths ## How to report a barrier, and what happens then Tell us what you were trying to do, what page you were on and what got in the way. Email the shop or phone during posted hours. A person reads it, and you get a written reply saying whether it is fixable quickly, scheduled, or outside our control with a workaround. Reports are the most useful accessibility input we receive, because they come from real use rather than from a checklist. Nothing you need from this shop depends on this website. Estimates, diagnostics, bookings, claim documentation and questions all work by telephone or at the counter during posted hours, and information on any page here can be read to you or sent as plain text. If a document format is a problem, say which format works and it will be produced that way. ## Questions and answers ### Which accessibility standard does this site aim at? The Web Content Accessibility Guidelines version 2.2 at Level AA. Current status is partial conformance, with the specific failures listed on this page rather than summarised. The statement was last reviewed on 15 July 2026 and is reviewed again on any structural change, on any reported barrier, or annually. ### Why publish a list of failures instead of claiming conformance? Because a statement with no exceptions usually means nobody tested. Naming a gap gives you a workaround today, which is worth more than a promise. It also makes the list shorter over time, since a published failure is harder to leave unfixed than one recorded in an internal document nobody reads. ### Can I get an estimate without using this website at all? Yes, entirely. Phone during posted hours or come to the counter. Estimates, diagnostics, bookings and claim documentation all work without any web interaction, and anything published on this site can be read to you or sent as plain text. No service here is web only by design. ### Are your estimates and invoices readable with a screen reader? Not reliably yet, and that is one of the listed limitations. The job documents are not currently tagged for screen reader navigation. Ask and the same content is provided as plain text or read to you on the phone. Tell us which format works for you and it is recorded on your file so nobody asks twice. --- Source: [OCRV Center](https://ocrv.me/accessibility/). Last verified 2026-07-29.