Pihasa Assistant Knowledge Base

Accessibility Statement

How accessible this site is, how that was tested, and how to report a barrier.

Last updated: 12 September 2026

1. Our commitment

SOPORTES PARA TUBERÍAS PIPE HANGERS, S.A. (Pihasa) wants this documentation to be usable by everyone, including people who browse with a keyboard only, a screen reader, magnification, or with colour vision deficiency. This statement describes how accessible the site currently is, how that was measured, and what to do if you hit a barrier.

2. Conformance status

This site aims to conform to Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Based on the evaluation described in section 4, the site is considered fully conformant with Level AA: no known Level A or AA failures remain.

Conformance is a moving target. If content or code changes without re-testing, this status may no longer be accurate, so the date above matters.

3. What makes the site accessible

  • Semantic structure. One <h1> per page, headings in order without skipped levels, real landmarks (header, nav, main, footer) and a “Skip to content” link as the first focusable element.
  • Keyboard operable throughout. Every control – navigation, search, FAQ accordions, article links – works without a mouse. The search dialog keeps focus inside it while open and returns focus to the button that opened it when you press Esc.
  • Visible focus. A high-contrast focus ring is drawn on every interactive element, and never suppressed.
  • Contrast. All text meets or exceeds the 4.5:1 ratio required at Level AA (3:1 for large text), in both the light and dark colour schemes.
  • Colour is never the only signal. Links inside body text are underlined, so they remain identifiable without perceiving colour.
  • Reflow. Pages work at 320 CSS pixels wide (400% zoom) with no horizontal scrolling. Data tables, which need a two-dimensional layout, scroll inside their own container and can be reached and scrolled with the keyboard.
  • Text spacing. Increasing line height, letter spacing and word spacing to the values in WCAG 1.4.12 does not clip or hide any content.
  • Respects your settings. The site honours your operating system’s light or dark preference and scales with your browser’s font size.
  • Status messages. Search results are exposed as a polite live region, so screen reader users are told when results change without losing their place.
  • Images. Screenshots and interface icons carry text alternatives, and figures have captions describing what they show.
  • No cookies, no pop-ups, no time limits, no motion. Nothing interrupts you and nothing moves on its own.

4. How this was evaluated

This statement is based on a self-evaluation carried out by the team that built the site. It has not been reviewed by an independent third party.

The evaluation combined automated and manual testing across the home page, article pages, category pages, the FAQ, the download page, the legal pages and the error page, in both light and dark colour schemes:

  • Automated testing with axe-core, restricted to WCAG 2.0/2.1 Level A and AA rules. Result: no violations.
  • Contrast ratios calculated for every colour pair in the design system, in both schemes.
  • Keyboard-only walkthroughs, including focus order, focus containment in the search dialog and focus restoration on close.
  • Reflow checked at a 320 pixel viewport, and the WCAG 1.4.12 text-spacing overrides applied to every page type.
  • Heading hierarchy and landmark structure checked page by page.

5. Known limitations

We would rather tell you about these than have you discover them:

  • No independent audit and no user testing. Automated tools catch only part of what matters. We have not yet tested with people who use assistive technology daily, and we have not commissioned an external certification.
  • Screenshots carry meaning that text cannot fully replace. The interface screenshots have alternative text and captions, but a few show dense datasheet fields whose detail is not reproduced in prose. If a screenshot is blocking you, contact us and we will describe its content.
  • Inline interface icons. Small icons reproduced inline in the articles are decorative repetitions of the adjacent text label and are exposed as such; they add nothing for screen reader users.
  • External sites. Links leave this site for the company website and third-party software vendors. We do not control their accessibility.
  • The software itself. This statement covers the documentation website only, not the Pihasa Assistant desktop application.

6. Feedback

If you find a barrier, or you need something on this site in a different format, please tell us. We treat accessibility reports as defects, not as suggestions.

Tell us the page address, what you were trying to do, and the browser and assistive technology you were using. We aim to acknowledge reports within five working days.

7. If you are not satisfied

If you contact us about an accessibility barrier and are not satisfied with the response, you can escalate the matter. In Spain, complaints about accessibility may be directed to the competent authority under Royal Decree 1112/2018 for public sector sites; for private sector sites, consumer protection and equal treatment bodies apply, including the Spanish Office for Non-Discrimination Attention (Oficina de Atención a la Discriminación).

8. Technical specification

Accessibility of this site relies on HTML, CSS, WAI-ARIA and JavaScript. The site is fully readable and navigable with JavaScript disabled; only the search dialog requires it, and every article remains reachable through the category pages and the in-page contents tree.