Reviewed: 19 July 2026
VeyraStone aims to make veyrastone.com usable with a keyboard, screen reader, zoom, high-contrast preferences, and reduced-motion settings. WCAG 2.2 Level AA is the working target for the public Site.
This is an honest implementation statement, not a claim that every page and third-party component has passed independent conformance certification.
Current status
Based on automated checks and internal template review, the Site is partially conformant with WCAG 2.2 Level AA. Partially conformant means that many core requirements are supported, while some issues may remain or require broader assistive-technology and user testing.
Measures currently implemented
- A skip link and semantic page landmarks.
- One primary heading on the public templates advertised in the sitemap.
- Keyboard-operable navigation, catalogue controls, disclosures, and form fields.
- Visible focus styles and Escape-key handling for custom panels.
- Document language declared as English (United States).
- Responsive layouts that support mobile screens and text enlargement.
- Reduced-motion handling for reveal effects.
- Descriptive alternative text and explicit disclosure on AI-generated editorial images.
- Form labels, required-state semantics, browser autocomplete for name, company, and email, and live-region treatment for asynchronous success or error feedback.
- Contrast corrections for the application-card and process-step labels identified in the July 2026 audit.
- No inactive single-language selector presented as an interactive control.
Known limitations and boundaries
Third-party form behavior
The contact form is rendered by Fluent Forms. VeyraStone reinforces autocomplete and dynamic status semantics, but plugin updates can change generated markup. The form is included in production regression checks and still requires periodic manual screen-reader testing.
Generated and future imagery
Current editorial application images are AI-generated references, are labelled as such, and are not product or project evidence. Future inventory and project photography will need contextual alternative text, captions, and disclosure appropriate to each page.
Natural-stone color information
Some material distinctions are inherently visual. Text descriptions should also explain movement, contrast, finish, and natural features. A physical sample can support tactile and visual review but is not promised as an accessibility substitute for every user.
Documents and video
The public Site does not currently rely on a library of technical PDF downloads or project videos. Before such material becomes a primary way to access information, it should receive tagged structure, reading order, captions, transcripts, and other applicable alternatives.
Testing coverage
Automated tools cannot prove accessibility. VeyraStone has not represented that the Site has completed an independent audit or a formal test programme with people who have disabilities. Keyboard, zoom, contrast, Lighthouse, and automated-rule checks are used as regression signals; manual assistive-technology review should continue.
Feedback and assistance
If a barrier prevents access to content or an inquiry path, email sales@veyrastone.com with the subject “Accessibility.”
Helpful details include:
- the page URL;
- what you were trying to do;
- the barrier you encountered;
- browser, operating system, and assistive technology if relevant; and
- the format or alternative that would help.
VeyraStone will review the report and, where reasonably possible, provide the information through an alternative method while the underlying issue is investigated. No fixed response deadline is promised on this page.
Technical approach
Accessibility is reviewed when templates, navigation, forms, images, color tokens, or interactive behavior change. The production release probe checks heading count, language, selected accessible-name regressions, legal-page availability, and form autocomplete. Manual keyboard and assistive-technology review remains necessary for meaningful releases.
Third-party services
Cloudflare may present a security challenge outside the normal Site templates. WordPress, GeneratePress, Fluent Forms, and other third-party components have their own release cycles. VeyraStone is responsible for configuring and testing the public implementation but does not control every upstream component.
Updates
This statement will be updated after material accessibility changes, a broader manual audit, or the introduction of new document, video, language, or form systems.