This site was built with the idea that information about AI tools also reaches people who use assistive technologies or who navigate by keyboard alone. This statement covers what has been done, what is outstanding and how to report a barrier that has not been resolved.
The reference framework is the W3C Web Content Accessibility Guidelines (WCAG) 2.1 at AA level, and Royal Decree 1112/2018, which incorporates the basic accessibility conditions. On a private site this is not a legal obligation, but the commitment is taken on anyway.
1. Measures adopted
- Semantic HTML. Headings use real heading elements rather than styles that imitate one, so a screen reader can move between sections.
- Links identified by their text. There is no "click here" or "read more" with no context. External links open in a new tab and are marked with an icon and a screen-reader notice.
- Sufficient contrast. Body text meets at least a 4.5:1 contrast ratio and large text at least 3:1, in both light and dark mode.
- The site works without JavaScript in the essentials. Content, navigation and pricing tables are rendered on the server. JavaScript only adds the interactive calculators and the search, which are enhancements to text that is already readable.
- Light and dark mode. Both can be chosen and the preference is remembered, so someone with low vision can adjust the contrast to suit them.
- Labelled form fields. Calculator fields have associated labels and results are announced to screen readers, so the interface does not rely on sight alone.
- System preferences are respected. `prefers-reduced-motion` is honoured, so animations are switched off when the system asks for reduced motion.
- A useful error page. The 404 page offers links to the homepage, the search engine and the main sections instead of a bare message.
2. Known limitations
The site has been reviewed manually and no serious barriers have been found, but it is worth being straight about the weak points:
- Pricing pages are real tables. On small screens they scroll horizontally rather than shrinking the text, which can be awkward with some screen readers if you are not navigating with the arrow keys.
- The calculators are the most JavaScript-dependent part. They work offline, but they need the script to have run, and results are shown on screen rather than in an announcer live region.
- No external audit with users with disabilities has been carried out. The review is technical and static, and does not substitute for testing with real people.
- The English and Spanish versions are reviewed separately, and the English version can lag behind on some corrections.
3. How to assess the site
You can check all of this without installing anything:
- Move through the page with the keyboard, using only Tab and Enter, with no mouse. Everything should be reachable and activable.
- Check that focus is visible. As you tab, the focused element should be clearly highlighted. If it is not, there is a real usability problem.
- Use a screen reader. On Windows, Narrator with Windows+Ctrl+Enter. What matters is that the heading structure makes sense.
- Increase text size to 200% and check that content is neither cut off nor overlapping.
- Check contrast with a browser extension, and confirm that focus states are visible.
4. Reporting a barrier
If you find something that prevents or makes it hard to read the content, write to alvarocimadevillawebs@gmail.com with the page and what happens. It will be addressed within a reasonable period and, when fixed, logged on the corrections page.
This site does not display the official accessibility symbols, because that implies a formal audit that has not been carried out. It is better to claim only what can be substantiated.