Support + accessibility
Accessibility Statement
Use this page to understand the site’s accessibility target, how barriers are reviewed, and the quickest way to get help if something blocks you from using the site comfortably.
Last updated March 6, 2026 · Written to make support expectations explicit instead of burying them in generic compliance language.
Quick answer
What is the fastest next step from this page?
Stay on the accessibility statement if you want the site’s target, testing approach, and barrier-reporting path. If your question is really about privacy or general support, the routes below are faster.
Decision blockers
Most accessibility-page visits are really one of four support needs
Visitors usually open this page because they want a fast answer on barrier reporting, response expectations, broader help, or whether the issue actually belongs under privacy or site terms. This section makes that routing explicit before the statement turns into a wall of compliance prose.
The real question is “how do I report a problem and what happens next?”
Stay on this page if you need the conformance target, testing approach, and support-response timing. When you are ready to act, jump straight to barrier reporting details so the page becomes useful, not ceremonial.
The real question is “I need human help that goes beyond accessibility alone”
Use the contact page when the issue includes a broader support request, a non-accessibility question, or context that does not fit neatly inside a barrier report.
The real question is “I am worried about forms, analytics, or vendors”
That is usually a data-handling question, not an accessibility one. The faster route is the Privacy Policy, where cookies, processors, and submitted information are explained directly.
The real question is “I need site-use rules or disclaimer boundaries”
If the concern is legal use, rights, disclaimers, or dispute language, move to the Terms of Service. That page is the right route when the issue is policy scope rather than usability support.
This page explains the site’s accessibility target, how issues are reviewed, and how to ask for help if you run into a barrier using the site.
Matt LaClear is committed to providing a website that is accessible to as many people as possible, regardless of technology or ability. We continually improve accessibility as part of our design, development, and content workflows.
Conformance Target
Our target is to conform with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.
Testing Methodology
We evaluate accessibility using a combination of automated checks and manual review. Our process includes keyboard-only navigation testing, semantic structure and landmark checks, color contrast review, and spot testing with assistive technologies such as screen readers on current major browsers.
When issues are identified, we prioritize fixes based on user impact and severity, then verify remediations before publishing updates.
Accessibility Features
- Semantic headings and landmark regions to support screen reader navigation.
- Visible keyboard focus indicators and keyboard-accessible navigation patterns.
- Skip-link support for faster keyboard access to primary content.
- Motion-sensitive interaction support for users with reduced-motion preferences.
- Consistent color and spacing systems designed to support readability.
Ongoing Improvements
Accessibility is an ongoing process. We periodically review templates, components, and published content and address issues as they are identified.
Third-Party Content
Some third-party content or embedded tools may be outside our direct control. We make reasonable efforts to choose providers with strong accessibility practices and to provide accessible alternatives whenever feasible.
Need Help or Found an Issue?
If you experience an accessibility barrier on this site, contact us and include the page URL and a brief description of the issue:
We aim to acknowledge accessibility feedback within 2 business days and provide a substantive update or resolution timeline within 10 business days.
Compatibility
This website is designed to work with current versions of major browsers and assistive technologies. Older browsers or unsupported environments may experience reduced functionality.
Best next step
Choose the fastest route for what you need
Need a response about a barrier?
Jump to accessibility support if you want acknowledgement timing and the right contact path.
Need compliance context?
Review the Privacy Policy if your question is about forms, analytics, or vendors.
Need a human answer right now?
Use the contact page if you want help that goes beyond this statement.
Related support
Where visitors usually go next
Need privacy details?
Use the Privacy Policy for data-handling and vendor-processing details.
Need site-use rules?
Use the Terms of Service for content-use, disclaimers, and jurisdiction language.
Need a direct reply?
Use the contact page if you want help beyond accessibility reporting alone.