Illustration of Juan Esteban’s runic monogram rendered in a three-dimensional architectural style within a frame, set against a light background.

Guides

Web accessibility for cultural projects: legal requirements and verification

A cultural website may feature clear text and a refined aesthetic yet remain unusable without a mouse, with screen magnification or via a screen reader. It may also pass an automated test and fail when a person attempts to purchase a ticket.

Web accessibility is not achieved by installing a plugin or reaching a score. It requires that information and operations be perceivable, operable, understandable and compatible with various assistive technologies.

This guide defines the Spanish framework and proposes a practical verification process. It does not replace a legal or technical audit where a specific obligation exists.

Applicable standards

There is no single law for all cultural websites. One must identify who provides the service, what operation it offers and whether public funding or procurement is involved.

Public sector

Royal Decree 1112/2018 applies to websites and mobile applications of public sector bodies. It includes administrations, public universities, libraries, museums and other services within its scope.

It mandates accessibility, a public statement, communication mechanisms, requests for accessible information, complaints, claims and periodic reviews. Disproportionate burden must be assessed and explained; it is not an automatic exemption.

The harmonised legal reference remains EN 301 549 v3.2.1, based on WCAG 2.1 level AA. In September 2026, EN 301 549 v4.1.1 was published, incorporating WCAG 2.2. The new version does not yet replace the previous one as a legal reference while the European Commission has not cited it in the Official Journal. Preparing for WCAG 2.2 avoids redoing procurement, testing and documentation.

Private services

Act 11/2023 transposes Directive (EU) 2019/882 on the accessibility requirements for products and services. From 28 June 2025, it extends to, among other cases, e-commerce directed at consumers. A publication shop, ticket sale or booking entirely online may be included depending on the service and the entity providing it.

Not every private website is subject to these requirements simply by existing or selling culture. The specific service must be examined. Micro-enterprises providing services are exempt when they employ fewer than ten people and their annual turnover or balance sheet does not exceed two million euros. The exemption does not necessarily cover obligations derived from public procurement, subsidies, equality regulations or commitments assumed by contract.

Funding and procurement

A call for applications, a public contract or an agreement may require accessibility even if the organisation is not directly subject to the general regime. Royal Decree 1112/2018 contains criteria for sites and applications with public funding. The terms and conditions matter as much as the legal form.

Follow the actual tasks

The audit must traverse what a person needs to do:

  • Find schedules, prices and access conditions.
  • Identify the building, transport and accessible entrance.
  • Purchase or return a ticket.
  • Book a place.
  • Register for an open call.
  • Attach documentation.
  • Read guidelines in PDF.
  • Watch a video or listen to audio.
  • Request information in an accessible format.

A homepage may be correct while the calendar, CAPTCHA, map or payment gateway blocks the process. Responsibility does not disappear because the component belongs to a provider.

Twelve-step verification

1. Navigate only with keyboard

Use Tab, Shift+Tab, Enter, space and arrow keys. You must be able to reach menus, dialogues, carousels, search, calendar, session selection, cookie consent and payment. Focus must not become trapped. A modal must close without a mouse.

2. Verify visible focus

Each interactive element requires a perceptible indicator. The order must follow the reading logic and not jump between distant areas without explanation.

3. Zoom to 200%

Text and controls must remain usable without loss of information. Also check reflow in a narrow window and browser zoom.

4. Review contrast and colour usage

WAVE, axe DevTools, Accessibility Insights or Lighthouse detect some failures. Also check focus, borders, icons, text over images and error messages. Colour cannot be the only signal for availability, price, error or selected seat.

5. Read the structure

A coherent H1 and a hierarchy of headings must exist. Lists must be lists and tables require headings. Do not simulate structure with size or bold text.

6. Evaluate names and labels

Each field requires a persistent label. The visible text of a button must match its accessible name. Repeating "More information" without context hinders link navigation.

7. Force errors

Submit empty forms, invalid dates and rejected payments. The error must be expressed in text, associated with the field, retain valid data and explain how to correct it. For purchases, registrations or assignment of rights, allow review and correction before submission.

8. Check images

An informative image requires an ALT that conveys its function. A decorative one must be excluded from accessible content. If a poster contains text, publish that information also in HTML or via an equivalent alternative; copying the entire poster into the ALT rarely works.

9. Review audio and video

Recorded videos with speech require subtitles. Relevant visual content may necessitate audio description or an alternative. Audio requires transcription. Controls must be keyboard-operable and possess clear labels.

10. Test with screen reader

On Windows, NVDA is free; on macOS and iOS, VoiceOver is integrated. Verify titles, regions, headings, links, forms, errors and state changes. A brief test does not replace expert users, yet it uncovers defects that a visual analysis fails to reveal.

11. Audit PDF and documents

A PDF may appear correct while lacking tags, reading order, language, title, headings or alternative text. PAC assists in verifying PDF/UA, yet manual review is required. Where possible, provide an HTML version as well.

12. Complete a real operation

Purchase a test ticket, submit an application or book an activity without a mouse. Include payment, authentication, codes sent via email and receipt download.

What an overlay does not resolve

Widgets that promise to 'make a website accessible' via an automatic layer may modify contrast, size or presentation. They do not necessarily correct the HTML, keyboard navigation, errors, PDFs, external gateways or an application's structure.

EN 301 549 v4.1.1 requires evaluating overlays as part of the complete product. Installing one does not demonstrate conformity.

Declaration and communication channel

Public organisations must publish an accessibility statement and offer avenues to report non-compliance, request accessible information and lodge complaints. A useful statement includes:

  • Scope of the site and covered applications.
  • Compliance status.
  • Non-accessible content and the reason.
  • Date and method of evaluation.
  • Contact channel.
  • Complaint procedure.

Do not declare full compliance without an audit. The statement also serves to record pending work and correction dates.

How to commission an accessible website

Include in the contract or tender specifications:

  • Required standard and version.
  • Level of conformity.
  • Scope: web, shop, bookings, PDF, video and third-party components.
  • Automated and manual tests.
  • Browsers and assistive technologies.
  • Report with criteria, evidence, severity and correction.
  • Review after changes.
  • Access to code and documentation.
  • Provider liability for defects.

Requesting 'WCAG compliance' without version, level or scope leaves too much margin.

Checklist before publishing

  • Everything functions with a keyboard.
  • Focus is visible and follows a logical order.
  • No keyboard traps.
  • Zooming to 200% does not lose information.
  • Contrast reviewed for text, controls and states.
  • An H1 and correct heading structure.
  • Fields with labels and instructions.
  • Errors identified and correctable.
  • ALT and alternatives for posters.
  • Subtitles, transcriptions and accessible controls.
  • Tagged PDFs or HTML alternative.
  • Purchase, booking or application tested from start to finish.
  • Declaration and contact updated when required.

Sources


Discover more from Juan A. Esteban

Subscribe to receive the latest posts by email.

Español English (UK)