Legal / Sheet 03
Accessibility Statement
The OCRV Center accessibility statement sets a conformance target of WCAG 2.2 Level AA for this website, lists the specific measures built into the pages, names the limitations the shop knows about, and gives a direct email route for reporting a barrier and getting a response.
Policy record
- Entity
- OCRV Center
- Domain
- ocrv.info
- Facility
- Yorba Linda, CA
- Contact
- info@ocrvcenter.com
- Applies to
- This website
A body shop customer may be reading this site with a screen reader, with text scaled up, with a keyboard and no mouse, or on a phone in bright sun in a parking lot. All of those are ordinary. The site targets WCAG 2.2 Level AA, which is the standard most public bodies and courts treat as the working benchmark. Targeting a standard is a commitment to build toward it and to fix what falls short, not a claim of perfection.
This statement describes what was actually done, what is known to be imperfect, and what happens when a visitor reports a problem. It avoids the vague language common to accessibility pages, because vague language does not help anyone who cannot complete a task. If any part of this site blocks a visitor from finding a price, reading a repair description, or sending a message, that is a defect worth reporting. Send the page address and a short description of the barrier to info@ocrvcenter.com.
Structure, Landmarks, and Headings
Pages are built from semantic HTML rather than a stack of generic containers. A banner, a main region, a navigation region, and a footer are marked as such, so a screen reader user can jump straight to the content instead of walking past the menu on every page. Headings follow a single logical order from the page title downward without skipping levels, which means the heading list a screen reader produces works as a table of contents for the page.
Lists are marked as lists. Tables that carry data, including the labor rate table and the price range tables, use real table markup with header cells associated to the rows and columns they describe. A skip link at the top of each page moves focus directly to the main content. Link text describes the destination rather than saying read more, so a list of links pulled out of context still makes sense to someone scanning it.
Keyboard Operation and Visible Focus
Everything on this site can be operated with a keyboard alone. Tab moves forward, shift and tab move back, enter and space activate. Tab order follows the visual reading order of the page rather than jumping around. Nothing traps focus, which means a visitor who tabs into a menu or a disclosure panel can always tab back out. The focus indicator is visible against every background used on the site, and it was not removed for visual tidiness.
Interactive controls are real buttons and real links rather than styled text that only responds to a mouse click. Expandable sections report their state so assistive technology can announce whether a panel is open or closed. Touch targets are sized so they can be hit reliably with a thumb, which matters on a phone and matters more for anyone with a tremor or limited fine motor control. Nothing here depends on a hover state that a touch device cannot produce.
Text Alternatives, Contrast, and Not Relying on Color
Photographs of repair work carry alternative text that describes what the image shows, not just its file name. A picture of a rebuilt fiberglass front cap is described as such, because the description is the only way a screen reader user gets the point of the image. Images that are purely decorative are marked so assistive technology skips them instead of reading noise. Diagrams that carry information have a text explanation nearby that conveys the same content.
Color contrast was checked against the Level AA thresholds, which ask for a ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text and for the visual boundaries of controls. Body copy, headings, link text, button labels, and table text were all measured rather than eyeballed. Color is never the only signal. A required field is marked with text as well as color, and a highlighted row in a price table carries a label, not just a tint.
Motion, Text Size, and Forms
Animation on this site is minimal by design, and what exists respects the reduced motion preference set in the operating system. A visitor who has asked their device to limit motion gets static presentation instead of transitions. Nothing flashes, blinks, or moves on a loop. There is no auto playing video and no carousel that advances on its own, because content that moves without permission is a barrier for readers with vestibular sensitivity and a nuisance for everyone else.
Text resizes. A visitor can scale text to twice its default size, or zoom the whole page to four hundred percent, and the layout reflows into a single column instead of clipping content or forcing horizontal scrolling. Line length and spacing hold up under that treatment. On the contact and quote request form, every field has a visible label that is programmatically tied to its input, so clicking the label focuses the field and a screen reader announces the right name.
Form errors are handled the same way. An error message appears in text next to the field it concerns, is associated with that field in the markup, and describes what to fix rather than saying the entry is invalid. Focus moves to the first problem so a keyboard user is not left hunting. Required fields are announced as required. Nothing on the form depends on a time limit. A visitor who steps away mid message does not lose the entry to a session timeout.
Testing Performed and Combinations Checked
Testing here is a mix of automated scanning and manual work, and the manual work is where most findings come from. Automated tools run against the page set to catch missing alternative text, contrast failures, and broken label associations. After that, pages are walked with a keyboard from top to bottom, and the price tables and the contact form are read aloud with a screen reader to confirm the announced content matches what a sighted reader sees on screen.
The combinations checked informally include NVDA with Firefox on Windows, VoiceOver with Safari on macOS, VoiceOver with Safari on iPhone, and TalkBack with Chrome on Android. Keyboard only navigation was checked in Chrome, Firefox, Safari, and Edge. Page zoom and browser text scaling were checked in each of those browsers. This is not a certified audit by an outside firm, and the shop does not describe it as one. It is careful in house checking, repeated when pages change.
Known Limitations
Honesty about gaps is more useful than a clean claim. Several parts of this site fall short of the target or have not been verified to the same depth. Automated testing catches a fraction of real barriers, perhaps a third of the issues that matter, and manual testing by people who are not daily screen reader users will miss things that a daily user notices immediately. The list below is what the shop currently knows about, and it changes as reports arrive.
None of these are treated as permanent. The map frame can be paired with a plain text address block that gives the same information without depending on the frame, and that text is present on the contact page. PDF documents can be replaced with HTML pages, which is the direction new material takes. Price tables get reworked as review turns up problems. A reported barrier moves to the front of the queue, because a report means someone was actually blocked.
- The embedded map frame comes from a third party and its internal behavior is outside what the shop controls.
- Some PDF documents predate the current standard and may lack proper tagging or reading order.
- Dynamic price tables with several columns need continued screen reader review, particularly on narrow screens.
- Older photographs carried over from earlier versions of the site may have thin alternative text.
- Automated scanning cannot detect whether a description is actually useful, only whether one exists.
Reporting a Barrier, Alternate Formats, and Visiting the Shop
To report an accessibility problem, email info@ocrvcenter.com with the address of the page, a description of what was attempted, and what happened instead. Naming the browser and any assistive technology in use helps a great deal, though a report without those details is still worth sending. The shop acknowledges accessibility reports within three business days and gives a plan or a fix within ten business days. If a fix takes longer, the reply explains why and offers another way to get the information.
Any information published on this site is available in another format on request. That includes the labor rate sheet, a price range page, a repair description, or an estimate document. Ask at info@ocrvcenter.com and say which format works: large print, plain text in the body of an email, or a read aloud walkthrough over email correspondence. There is no charge for an alternate format, and nobody has to explain why they need one.
The physical facility matters too. The shop sits on La Palma Avenue in Yorba Linda, and customers travel in from Eastvale and the surrounding area. Parking near the office entrance is level, the counter area is reachable without steps, and staff will come out to a vehicle if getting to the counter is difficult. A customer who needs a document read aloud, a written summary of a verbal explanation, or extra time to work through an estimate should say so, and the office will make room for it.
- DWG
- LGL-03
- SCOPE
- ACCESSIBILITY STATEMENT
- SHEET
- 03 OF 05
- SCALE
- 1:1
- MARKET
- EASTVALE, CA
- SHOP
- YORBA LINDA, CA
Questions about a policy on this page
Write to info@ocrvcenter.com and reference the policy name. Correspondence about this website is handled from the Yorba Linda facility.
