Accessibility statement

1. Our commitment

We want PyRapid to be usable by everyone, including people who browse with a screen reader, keyboard only, zoom or low vision. We use the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, as our reference. It is a goal we are working towards: we do not claim to hold a conformance certification.

2. What we have done

• Semantic structure: a main region, identified navigation and footer, and an orderly heading hierarchy.
• A “Skip to content” link at the start of every page.
• Everything can be used with the keyboard, with a visible focus indicator.
• Forms with associated labels, errors announced to screen readers and autocomplete attributes.
• Anti-bot verification in text (a simple arithmetic question), with no distorted images and no tests that depend on seeing or hearing.
• Declared page language and a language selector (Spanish, English and Portuguese).
• Respect for the system preference to reduce motion, and a layout that adapts to zoom and small screens.
• A dark design with light text, chosen to aim for sufficient contrast between text and background, and decorative icons hidden from screen readers.
• Links that open in a new tab say so.

3. Known limitations

If the administrator enables Google reCAPTCHA, that component belongs to a third party and we do not control its accessibility; it offers an audio alternative. If any check is impossible for you, write to us by email or WhatsApp and we will handle your enquiry without requiring it. Some project images uploaded by the administrator may lack a detailed description.

4. Tell us if you find a barrier

If you have trouble using the site or want content in another format, write to [email protected] stating the page, the problem and, if you know it, the browser and assistive technology you use. We will try to reply and fix it as soon as possible. If you do not get a satisfactory answer, you can turn to the accessibility or consumer-protection body of your country.