ACCESSIBILITY AT ZARIS

A more accessible web,
one improvement at a time.

We want people with different abilities, technologies and ways of navigating to be able to understand and use the ZARIS website.

STATEMENT SCOPE

Our accessibility commitment and current status.

ZARIS Tech is working to make its public website more usable for people with disabilities. We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our target for design, development and ongoing improvement.

This statement covers the public website at newwebzaris.zaristech.com. Separate applications, external destinations and third-party services may have different accessibility support.

Target standard
WCAG 2.2 Level AA
Conformance status
Not yet formally assessed
Assessment approach
Internal development checks; independent audit not completed
Statement updated
19 November 2026

WCAG FOUNDATION

Four principles guide accessible web content.

WCAG organizes accessibility around content being perceivable, operable, understandable and robust. These principles inform our design and engineering decisions.

01

Perceivable

Information should be available in ways people can perceive, including meaningful text alternatives and adaptable structure.

02

Operable

People should be able to navigate and use controls with a keyboard and without interactions that create avoidable barriers.

03

Understandable

Content, navigation, labels and error messages should be clear and behave in predictable ways.

04

Robust

Semantic implementation should work across current browsers and assistive technologies as reliably as practical.

IMPLEMENTATION MEASURES

Accessibility practices used on this website.

Accessibility is treated as an ongoing product-quality responsibility. The following measures describe implementation intent, not a certification.

Semantic structure

Landmarks, headings, lists and native controls are preferred so content has meaningful structure beyond its visual layout.

Keyboard and focus

Interactive elements are designed for keyboard access with visible focus states and logical navigation order.

Forms and feedback

Inputs use programmatic labels and status messages are intended to explain errors or outcomes without relying only on color.

Responsive reflow

Layouts adapt across viewport sizes and are designed to remain usable with browser zoom and larger text.

Motion preferences

Decorative animation is reduced where the user’s device requests reduced motion; core information does not depend on animation.

Meaningful alternatives

Informative images need useful alternative text, while decorative graphics are hidden from assistive technology where appropriate.

TECHNICAL INFORMATION

Technologies and compatibility.

The public website relies on HTML, CSS, JavaScript, SVG and limited WAI-ARIA where native HTML alone does not communicate the required state or relationship.

It is designed for current versions of major browsers and common desktop and mobile environments. A comprehensive browser, operating-system and assistive-technology compatibility matrix has not yet been completed.

Read W3C guidance for accessibility statements ↗
HTML
Meaning and structureLandmarks, headings, forms and controls
CSS
Presentation and reflowResponsive layout, contrast and focus visibility
JS
Interactive behaviorMenu state, validation and progressive controls
ARIA
Accessible statesUsed where semantic HTML needs additional context

KNOWN LIMITATIONS

Areas that need continued review.

Please contact us if one of these areas—or any issue not listed—prevents you from accessing information or completing a task.

01

Third-party and external destinations

Booking, verification, embedded provider and separate product pages may be operated by third parties or different applications. Their accessibility behavior can differ from the public website.

Alternative: email [email protected] and describe the task you need to complete.
02

New and changing content

New pages, media, documents or interactive features can introduce barriers that were not present in an earlier review.

Action: accessibility checks should be repeated when templates and key journeys change.
03

Assistive-technology combinations

Behavior can vary across browsers, operating systems and assistive technologies. The website has not yet completed a formal, representative compatibility audit.

Alternative: report the combination and barrier so we can investigate a practical route.

ACCESSIBILITY FEEDBACK

Tell us when a barrier gets in your way.

Email the page URL, the task you were trying to complete and what happened. Browser, device and assistive-technology details can help if you choose to share them.

Do not include passwords, API keys, confidential records or unnecessary sensitive personal information.

COMMON QUESTIONS

Website accessibility FAQ

Answers about our WCAG target, assistive-technology support and how to request help.

What accessibility standard does the ZARIS website follow?

ZARIS uses WCAG 2.2 Level AA as the target for the public website. This statement does not claim full conformance because a complete formal evaluation has not yet been completed.

Can I use the website with a keyboard?

The website is designed so primary navigation, links, buttons and forms can be reached and operated with a keyboard. If you encounter a keyboard trap, missing focus indicator or unreachable control, please report the page and task to [email protected].

Does the website support screen readers?

The implementation uses semantic HTML, headings, labels, landmarks and accessible names intended to support assistive technologies. Compatibility can vary by browser and screen-reader combination, and a full compatibility matrix has not yet been formally evaluated.

How do I request information in an alternative format?

Email [email protected] with the page URL and the information you need. Describe the format or assistance that would help, without including passwords or unnecessary sensitive information.

Are third-party booking and product pages covered by this statement?

This statement primarily covers the public ZARIS website. External booking, verification, embedded provider and separate product interfaces may have their own accessibility behavior and statements. Report a barrier and we will help identify an available route.

How can I report an accessibility problem?

Email [email protected] with the URL, the task you were trying to complete, what happened and—if you choose—your browser, device and assistive technology. We will review the report and work toward a practical response or alternative.

BUILD THE NEXT STEP

Need help accessing ZARIS information?

Tell us the page, task and barrier. We will review the issue and help identify a practical alternative where available.

ScopeSystemsSafeguards
Request a conversation