Skip to content
JX Systems
Language: EspañolQuoteGet your quote

Accessibility

Accessibility statement

We want anyone to be able to use this site, including with a keyboard, a screen reader, zoom or contrast settings. Here we explain where it stands today, how we checked it and what is still missing.

Status

Partially conformant with WCAG 2.2 level AA.

Our own evaluation of October 2, 2026. The known limitations and what we have not tested yet are described on this page.

Statement date:
Last reviewed:

Our commitment

JX Systems wants its website to be usable without barriers. We use the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, and the European standard EN 301 549 for websites as our reference.

This statement covers this site, in Spanish and in English. It does not cover the websites and systems we build for our clients, or the documents we send by email, such as proposals and invoices.

Conformance status

This site is partially conformant with WCAG 2.2 level AA: it meets most of its criteria, but it has the limitations explained below and it has not yet been tested with real screen readers or in every browser.

How we evaluated it

On October 2, 2026 we carried out our own evaluation of the site (not an audit by an independent third party), fixed what we found and checked it again:

  • Automated testing with axe-core of the WCAG 2.0, 2.1 and 2.2 rules (levels A and AA) on the 88 pages the site had then (43 per language and the two error pages), on desktop (1,280 px wide) and on mobile (390 px). After the fixes no failures were left.
  • A keyboard walk-through of 21 pages per language, on desktop and on mobile: 5,276 tab stops, all of them with a visible focus indicator.
  • Color contrast: calculation of the colors of the site and pixel sampling of the text that sits on gradients or photos.
  • Small screens and zoom: no horizontal scrolling on any of the 88 pages at 320 px wide (the same as a 400% zoom) or at the other widths tested, up to 1,920 px.
  • Text enlarged to 150% and 200%, and wider spacing between letters, words and lines (criterion 1.4.12).
  • The quote, contact, booking and audit forms: labels, error messages and how they are announced, and focus when they are submitted.
  • System preferences: reduced motion and forced colors (Windows high contrast mode), on a sample of pages.

What we have not tested yet

  • Real screen readers (NVDA, JAWS, VoiceOver or TalkBack) and testing with people who use assistive technologies: what each page announces was inferred from its code and its accessibility tree.
  • Other browsers: every test was run with Chromium (Microsoft Edge), not with Safari (on macOS or iOS) or Firefox.
  • The cookie notice: it only appears when analytics is turned on, and it is not on yet. We reviewed its code, not how it works on the live site.

Known limitations

These are the parts of the site that we know are not fully accessible yet:

  • Enlarged text without zoom. If you increase only the text size to 200% (in the browser or phone settings, without zooming the page), some cards cut off part of their text, for example the plan cards on Memberships. With browser zoom the content adapts without being cut off.
  • Borders of some options. The time slots of the booking calendar and the option cards of the forms have a low-contrast border. Each option can be recognized by its text, and it changes color when you choose it.
  • Footer links. They are about 32 px tall: they meet the 24 px minimum of WCAG 2.2 (criterion 2.5.8), but they are smaller than the 44 px we use on the rest of the site.

Third-party content

Some steps happen outside this site: WhatsApp, the bank or service you use to pay by transfer and, if we offer one in the future, an external booking calendar. Their accessibility depends on each provider and we have not evaluated it.

Tell us about a barrier

If you find something you cannot use on this site, or you need the information on a page in another way, write to us:

  • On WhatsApp, at +56938826061. You can also use the WhatsApp button that appears on every page.

Tell us which page you were on, what you were trying to do and what happened. A person on our team replies, usually right away or within 12 hours; when many requests come in, within 24 hours.

While we fix it, you can ask us through the same channel for what you were looking for on that page: a quote, a consultation or any information on the site.

About this statement

We prepared this statement on October 2, 2026 with the results of the evaluation described above. Last reviewed: October 2, 2026.

We will update it when the site changes in an important way or when we fix any of the known limitations.