Skip to main content
The official website of VarenyaZ
VarenyaZ

Accessibility

Accessibility Statement

We are committed to making our website accessible to as many people as possible, including people with disabilities.

Scope

This statement applies to content published on varenyaz.com, including public website pages, public content, downloadable documents, and application surfaces owned by VarenyaZ. It may not apply to third-party websites or services linked from our site.

Standards

Our target standard is WCAG 2.1 Level AA, with additional alignment to WCAG 2.2 Level AA where feasible. For EU readiness, our engineering process also considers EN 301 549 requirements for web content, documents, and digital services.

Current Status

Current status: partially conformant. We are actively improving known issues and do not treat automated scans alone as proof of conformance. Items still requiring manual, assistive-technology, document, or third-party verification are listed below and tracked in the accessibility evidence package.

What You Should Be Able To Do

  • Navigate the website using a keyboard.
  • Use screen readers with core public content and representative flows.
  • Zoom text up to 200% without loss of core functionality on tested routes.
  • Use forms and public navigation without a mouse.
  • Access captions, transcripts, or alternate formats for supported media where available.
  • Request accessible formats for documents or content that are not yet fully verified.

Known Limitations

The public company profile PDF still needs manual tagged-PDF verification.

Affected content: /corporation/VarenyaZCompanyProfile.pdf

Alternative: Use the accessible HTML equivalent at /company-profile/.

Expected action: Target review date: August 31, 2026.

Some third-party widgets and embeds still require live vendor accessibility verification.

Affected content: reCAPTCHA, analytics consent behavior, embedded media, and social sharing widgets where present

Alternative: Use the contact form, email, or phone support paths if a third-party control blocks a task.

Expected action: Target review date: July 31, 2026.

Interactive demos, charts, and lab-style widgets are under staged manual review.

Affected content: AI Studio, labs widgets, charts, diagrams, and custom visual demos

Alternative: Request an accessible summary or alternate format through the feedback process below.

Expected action: Target review date: September 30, 2026.

Feedback And Support

If you encounter an accessibility barrier, contact us:

Please include:

  • Page URL.
  • Description of the issue.
  • Browser and assistive technology used, if applicable.
  • Preferred contact method.

Accessibility Feedback Form

Report an accessibility barrier

This form creates an internal Accessibility ticket and sends the report to the dedicated accessibility inbox.

Response Process

We acknowledge accessibility feedback within 2 business days. We aim to provide a substantive response or accessible alternative within 15 business days. Critical blockers affecting core services are prioritized.

Testing

This statement was prepared on May 13, 2026.

The website was last tested on May 13, 2026.

Testing to date includes:

  • Automated route scans with axe and Pa11y on representative public routes.
  • JSX accessibility linting and component-level accessibility tests.
  • Keyboard, focus, 200% text, 320px reflow, reduced-motion, and form-control probes on representative routes.
  • Design token contrast checks and dialog focus-management checks.
  • PDF/document marker inventory and accessible HTML alternative tracking.

Manual screen reader testing across the full assistive-technology matrix remains in progress and must be completed before any full-site conformance claim is made.

Browser And Assistive Technology Compatibility

The site is intended to work with current versions of Chrome, Edge, Safari, and Firefox, and with assistive technologies including NVDA, VoiceOver, TalkBack, and JAWS where enterprise testing is available. Compatibility can vary by browser, operating system, device, and assistive-technology version.

Technical Dependencies

Accessibility depends on semantic HTML, CSS, JavaScript, Next.js, React, browser support for modern web standards, media players, document viewers, and selected third-party services such as analytics, consent, spam prevention, and embeds. When a dependency creates an accessibility barrier, we track the issue and provide an alternative path where feasible.

Ongoing Improvements

We maintain an accessibility backlog, test new releases, train product, design, content, and engineering teams, review reusable components, and periodically refresh this statement as evidence, limitations, or support processes change.

This statement describes an active engineering program and should not be read as a legal certification or a claim that every item is fully conformant at all times.