Accessibility Statement

Effective date: September 7, 2026

1. Commitment

Ruzaani is committed to making ruzaani.com and its public digital content usable by as many people as reasonably possible, including people who use assistive technologies or interact with digital services through alternative input, display, or navigation methods.

Ruzaani designs and develops its public website with the objective of conforming to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

This statement describes the accessibility standard Ruzaani applies, the scope of that commitment, the measures used to support accessibility, and the procedure for reporting barriers.

Ruzaani is a trade name operated by Fernando Alberto Ocampo Romay, with domicile at Hidalgo 914, Centro, Coatzacoalcos, Veracruz 96400, Mexico.

2. Accessibility standard

Ruzaani uses WCAG 2.2 Level AA as the principal accessibility reference for its public digital services.

The website is designed so that essential information and functionality do not depend solely on color, animation, pointer input, or a particular screen size. Navigation, forms, error messages and other essential functions are intended to remain operable through a keyboard and compatible with commonly used assistive technologies.

Ruzaani treats accessibility as part of the design and implementation of the service rather than as a separate presentation layer added after development.

Unless and until a complete conformance evaluation supports a stronger statement, this Accessibility Statement describes Ruzaani's accessibility objective and implementation standard and should not be interpreted as a representation that every page, document, third-party component, or possible user configuration has been independently certified as fully conformant with WCAG 2.2 Level AA.

3. Website structure and navigation

Ruzaani's website is designed to use semantic page structure, meaningful headings, landmarks, labels, links, and controls so that content can be understood and navigated without relying solely on visual presentation.

Interactive functions are intended to be usable through keyboard navigation, with visible focus indication and a logical focus order. Where an operation changes the state of a page without a full page reload, important changes such as validation failures, submission status, or other material updates are intended to be communicated in a form available to assistive technologies.

Content remains intended to be understandable when zoomed or reflowed within the ranges required by the applicable accessibility standard, without forcing unnecessary horizontal navigation or loss of essential information.

4. Contact forms

Contact forms are designed to provide programmatically associated labels, instructions, validation information and error identification rather than relying on placeholder text or visual position alone.

Required fields should be identified without relying solely on color. Where a submission contains errors, Ruzaani aims to identify the affected fields and provide enough information to correct them. Important submission and confirmation states should be available to assistive technologies.

If the contact form presents a barrier, a person may email [email protected] for assistance with accessing the same information or making contact.

5. Visual presentation

Ruzaani aims to maintain sufficient contrast between text, controls, indicators, and their backgrounds in accordance with WCAG 2.2 Level AA.

Color may be used to reinforce meaning but is not intended to be the sole means of communicating a status, distinction, result, warning, or action.

Text and interface components are designed to support browser zoom and responsive reflow. Content should remain usable across common desktop and mobile viewport sizes without requiring a particular display resolution.

Where motion or animation is used, it is intended to serve a functional purpose rather than being necessary to understand the content. Ruzaani aims to honor user preferences that request reduced motion.

6. Tables, charts and diagrams

Ruzaani may use tables, diagrams, charts, and visual result displays to communicate structured information.

Material information represented visually is intended to be accompanied by an accessible textual or structured equivalent sufficient to communicate the relevant meaning without requiring the user to perceive color, position, shape, or graphical relationships alone.

Tables are intended to use appropriate structural relationships between headers and data. Complex visualizations are reviewed according to whether the same information can be obtained through assistive technology or a meaningful alternative presentation.

7. Content language

Ruzaani publishes content in reviewed language versions and identifies the language of each page in a form that can be recognized by user agents and assistive technologies.

Where a page contains a material fragment in another language, the fragment should be identified appropriately where doing so is necessary for correct pronunciation or interpretation by assistive technology.

8. Downloadable documents

When Ruzaani provides downloadable documents, it aims to use meaningful structure, logical reading order, identifiable headings, accessible links, suitable table structure and text alternatives where needed.

PDF/UA principles may guide PDF preparation, but a document is not represented as certified or fully conformant unless the relevant validation has been performed. The current website does not provide the former assessment PDF generator.

If a supplied document presents a barrier, an accessible alternative may be requested through the contact route in this statement.

9. Third-party content and services

Certain functions may depend on third-party infrastructure, embedded functionality, external websites, or services not designed or controlled entirely by Ruzaani.

Ruzaani seeks to select and configure third-party services in a manner compatible with its accessibility objectives where those services form part of the user experience. However, Ruzaani cannot guarantee the accessibility of a separate third-party website, application, interface, or document that it does not control.

A link to a third-party service does not constitute a representation that the external service conforms to WCAG 2.2 or another accessibility standard.

Where an essential Ruzaani function depends on a third-party component that creates a material accessibility barrier, Ruzaani will seek a reasonable technical or alternative means of providing access where practicable.

10. Evaluation and review

Accessibility review should include automated checks and manual examination of keyboard navigation, headings and labels, focus behavior, contrast in light and dark presentation, zoom and reflow, form errors, reduced motion and screen-reader interaction. Downloadable documents require their own checks.

Automated testing alone does not establish conformance. The scope and limitations of any evaluation must remain clear, including the content, devices and assistive technologies examined.

This statement sets out the accessibility objective. It does not claim that an independent complete WCAG 2.2 AA evaluation has been performed. Material releases and reported barriers should inform subsequent review and remediation.

11. Limitations and priorities

Complete conformance across every page, downloadable document and combination of browser and assistive technology has not been established. External websites and documents supplied by others may also present barriers outside Ruzaani's direct control.

A reported problem affecting navigation, access to service information or the ability to make contact receives priority over a cosmetic inconsistency. Ruzaani will assess the barrier, seek a practical correction and offer a reasonable alternative where available.

The absence of a listed issue should not be interpreted as a claim that no barriers exist. Reports through [email protected] help identify the content or function that needs attention.

12. Accessibility assistance and alternative formats

A person who cannot access information or complete a function because of an accessibility barrier may request assistance or an alternative accessible format.

Ruzaani will make reasonable efforts to provide the same material information or function through an accessible alternative where the original format creates a barrier and an alternative can reasonably be provided.

A request for an alternative format does not require disclosure of a medical diagnosis or detailed health information. The request need only provide enough information to identify the affected content or function and explain the practical accessibility barrier or alternative format needed.

13. Reporting an accessibility barrier

Accessibility problems may be reported to [email protected].

A report should, where reasonably possible, identify the page, document or function affected and describe the problem encountered. Information about the browser, device, assistive technology, or interaction method may be provided where useful for reproducing the issue, but is not required unless necessary to investigate the problem.

Ruzaani will review reported barriers and determine the appropriate corrective action based on the nature of the issue, its effect on access to essential content or functionality, the available technical solution, and the time reasonably required to implement and verify the correction.

Accessibility reports are used for remediation and quality improvement and are not treated as marketing inquiries.

14. Personal information in accessibility requests

An accessibility request may require Ruzaani to process contact information and information describing the technical barrier encountered.

Users should avoid providing unnecessary medical or other sensitive personal information when reporting an accessibility issue. A diagnosis is ordinarily unnecessary to investigate a technical accessibility problem or provide an alternative format.

Personal data submitted through an accessibility request is processed in accordance with the Privacy Notice.

15. Changes to this Accessibility Statement

The Accessibility Statement published at ruzaani.com/accessibility/ is the current version and becomes effective on the date stated at the beginning of the document.

Ruzaani may revise this statement to reflect changes to the website, accessibility testing, applicable standards, available technologies, identified limitations, or accessibility practices. Revisions are communicated by publishing the updated statement with a new effective date.

16. Language

Ruzaani may publish this Accessibility Statement in more than one language. Where legally permissible, the English version governs interpretation in the event of an inconsistency between published language versions, without limiting mandatory rights available under applicable law.

17. Contact

Questions, accessibility reports, and requests for an accessible alternative may be addressed to:

Ruzaani Operated by Fernando Alberto Ocampo Romay Hidalgo 914, Centro Coatzacoalcos, Veracruz 96400 Mexico [email protected]