Semantic Structure
Pages use headings, landmarks, lists, links, forms, and section structure so assistive technologies can navigate the content more predictably.
Accessibility
Access should be designed into the VEHICOTEK experience.
VEHICOTEK aims to make its public website easier to navigate, understand, and use across products, installer pathways, warranty support, company pages, and account entry points.
Commitment
Accessibility is treated as an operating practice, not a footer-only statement.
The current storefront foundation uses reusable components, consistent navigation, keyboard-aware menus, semantic page structures, and validation patterns so future VEHICOTEK pages do not need to reinvent accessibility behavior one route at a time.
This statement describes current public-page practices and does not claim third-party approval or final coverage for future backend, portal, cart, checkout, warranty, claim, or installer-account workflows that have not yet been implemented.
Supported Practices
Current public-page practices.
Keyboard Access
Global navigation, menu triggers, route links, search entry, account entry, and form controls are built to be reachable and operable with a keyboard.
Focus Visibility
Interactive UI components include visible focus styling aligned with the VEHICOTEK design system.
Readable Content
Public pages use consistent typography, meaningful link labels, text alternatives for conceptual visuals, and responsive layout patterns.
Form Feedback
Contact form fields expose labels, help text, required states, validation errors, and an alert region for submission-state messaging.
Motion Awareness
The homepage intro stores session-only playback state, and motion behavior should continue to respect user preferences as animation expands.
Known Limitations
Current boundaries stay visible.
The page documents the present storefront instead of pretending every future system has already been audited.
Share FeedbackDraft Legal and Support ContactsDedicated accessibility contact details are not approved in the repository, so feedback currently routes through the Contact workflow.
Backend-Dependent ConfirmationAccessibility feedback can be validated in the storefront, but a real support reference requires an approved backend contact endpoint.
Ongoing Content ReviewFuture product, account, warranty, installer, cart, checkout, and admin workflows will need page-level accessibility review as they are implemented.
Feedback
Report a website accessibility barrier.
Use this form for public website accessibility feedback. Include the page URL, browser or device context, and a clear description of the barrier. Do not include unnecessary disability details, passwords, verification codes, payment-card data, government identifiers, or other sensitive information.