Accessibility statement

Scope

This statement applies to andarama.com (the public site), to the viewer that displays published tours and to app.andarama.com (the Studio, the editor). We take as reference Spain's Real Decreto 1112/2018 on the accessibility of public sector websites and the UNE-EN 301 549 standard, which refers to the WCAG 2.1 Level AA guidelines.

Compliance status

Partially conformant with WCAG 2.1 level AA. On the screens evaluated there is no serious or critical failure left that can be detected automatically, and what was checked by hand with the keyboard works, but some aspects have not been checked and there are exceptions, listed below. This is a self-evaluation: no external audit and no testing with screen reader users have been carried out yet.

How it was evaluated

Evaluation of 27 September 2026, with two methods:

• Automated, with axe-core and the WCAG 2.0 and 2.1 level A and AA rules. It is part of the end-to-end tests, runs on every code change and fails on any serious or critical failure. An automated tool only detects part of the possible problems.
• Manual, with the keyboard: going through with Tab, Shift+Tab, Enter, Space and Escape to check the focus order, that focus is visible, that dialogs keep focus and give it back when closed, and that content reflows at 640 pixels wide (the same as 200% zoom on a 1280 screen).

Screens evaluated: on andarama.com, the home page, pricing, training, classroom, the blog, one of its posts and this statement; in the viewer, a published tour with its scene, a hotspot panel, help, the share dialog and the accessible version; in the Studio, sign-in, projects, the media library, the plan page, the editor (scenes and properties, graph, settings, translations, versions and comments) and the publish, export and share dialogs.

What has been checked to conform

• No serious or critical axe failures on the screens evaluated.
• The language of every page is declared in the document, including the viewer and the Studio.
• Viewer: hotspots can be reached with Tab and activated with Enter or Space; panels and dialogs (help, share, final screen, quiz result) keep focus, close with Escape and return focus to the button that opened them; the closed scene menu is out of the tab order.
• Visible focus on every control checked.
• The reduced-motion preference (prefers-reduced-motion) is respected: neither panels nor the menu are animated.
• At 640 pixels wide the site does not require horizontal scrolling and the viewer toolbar folds behind a button that unfolds it again.
• Linear accessible version of the tour, scene changes announced to screen readers and WebVTT subtitles on 360 video and on video hotspots.
• Studio: a “Skip to content” link, dialogs that keep focus and close with Escape, and text with a contrast of at least 4.5:1 on the screens evaluated.

What is not accessible or has not been checked

• Exploring a 360 photo is visual by nature: the alternative is the linear accessible version, whose quality depends on the texts written by whoever creates the tour.
• Alternative text is only required if the publisher turns on “Require alternative text to publish” in the tour settings; otherwise a tour can be published without it.
• Some Studio operations are designed for a mouse or touch screen (placing a hotspot by clicking on the panorama, arranging the graph or the floor plan by dragging) and it has not been checked that all of them have an equivalent keyboard alternative.
• It has not yet been tested with screen readers (VoiceOver, NVDA, JAWS) or with people with disabilities.
• The plans page and payment in the hosted version use forms from an external provider that are not covered by the automated test.
• Embedded third-party content (web pages, YouTube or Vimeo videos, 3D models) depends on its source.
• A tour’s custom themes and colours may not reach the minimum contrast.
• Virtual reality with a headset has no equivalent alternative inside the immersive session.

If you publish tours for a public institution

Each body is responsible for the accessibility of what it publishes. To make a tour as accessible as possible: write alternative text for every scene and every image, give hotspots text, subtitle videos and check the contrast if you change the colours. This statement serves as supplier information for your own.

If your organisation needs it, turn on “Require alternative text to publish” in the tour settings: the Studio will not publish while any scene or hotspot lacks alternative text.

Contact and feedback

If you find an accessibility barrier, or need content in an accessible format, write to us at jl@joseluissaorin.com. We reply within 20 working days at most.

Preparation of this statement

Statement prepared on 27 September 2026 through a self-evaluation by our own team (automated testing with axe and manual keyboard review). Last reviewed: 27 September 2026. It will be reviewed after the external audit and, in any case, every year.