Read the summary: the situation, the risk and what to do, in a minute.
Send this link to whoever maintains your website: the issues go from most to least serious, with where they are and how to fix them.
Save this link: it's your access to the report. Share it only with people you want to see it.
In short
For decision-makers, in a minute.
Status: there are things a screen reader can't name or that can't be used without a mouse; start with those.
Risk: if the website sells or provides services to consumers (e-commerce, banking, transport…), Spain's Law 11/2023 requires it to be accessible, unless the service is provided by a micro-enterprise, and we found no information about the website's accessibility. A user can complain, and the administration can impose penalties. If this applies to you, ask your adviser.
First: buttons with no name (menu, search, close…) that can't be used with a screen reader.
What to do: pass this report to whoever maintains the website, fix the issues in the order they appear and publish the statement.
Before you start
The law refers to technical accessibility standards based on a list of guidelines called WCAG (the reference standard, UNE-EN 301549, covers version 2.1, level AA, and we add the new parts of 2.2 that can be measured, such as button size). A machine can check roughly a third of that list, and that's what this report measures.
The rest has to be reviewed by a person: for example, whether the whole website can be used with the keyboard alone, whether it reads in a logical order or whether the image descriptions say something useful.
Issues that stop you from using the website come first, then the rest, from most to least serious. For each one you get what it means, how to fix it and examples taken from your own website. What we measure and what we don't.
This is how your home page begins for someone who can't see it
«Link: Café de Muestra, inicio.»
«Link: Shop.»
«Link: Cafés.»
«Link: About us.»
«Link: Contacto.»
«Button: Buscar.»
«Button: Carrito.»
«Image: Taza de café recién hecho. Recién tostado cada lunes.»
«Button: ‹.»
«Button: ›.»
«Link: IMG_2034.jpg.»
«Link: Leer más.»
The first links, buttons and images, as a screen reader names them (it also reads the text and headings between them). Each “no name” is something that people who can't see the screen can't use.
Using the website with the keyboard only
Many people don't use a mouse: blind people, people with limited hand movement or who navigate with a switch. We went through your pages pressing the Tab key, as they would.
Home page
https://cafedemuestra.example/
·Recommendation: Recommendation: There's no link to skip to the content. The page has another way to skip the menu (marked areas), but a link at the start helps keyboard users a lot.
✓Correct: Correct: We didn't find any place where the focus gets trapped.
✗Issue: Issue: On 15 or more elements you can't see where the focus is. Keyboard users get lost. Fix: don't remove the focus outline (outline: none) or replace it with another clearly visible one.
✓Correct: Correct: Focus doesn't go into hidden elements.
✗Issue: Issue: 1 thing can be clicked with the mouse but not used with the keyboard, for example: «Ver ofertas». Fix: use real buttons and links (<button>, <a href>) instead of a clickable <div> or <span>.
No visible focus, for example: «Café de Muestra, inicio», «Shop», «Cafés», «About us».
Page /producto.html
https://cafedemuestra.example/producto.html
·Recommendation: Recommendation: There's no link to skip to the content. The page has another way to skip the menu (marked areas), but a link at the start helps keyboard users a lot.
✓Correct: Correct: We didn't find any place where the focus gets trapped.
✗Issue: Issue: On 13 elements you can't see where the focus is. Keyboard users get lost. Fix: don't remove the focus outline (outline: none) or replace it with another clearly visible one.
✓Correct: Correct: Focus doesn't go into hidden elements.
✓Correct: Correct: We didn't find anything that can be clicked with the mouse but not used with the keyboard (custom-built things, such as menus or carousels, are worth testing by hand).
No visible focus, for example: «Café de Muestra, inicio», «Shop», «Cafés», «About us».
Page /contacto.html
https://cafedemuestra.example/contacto.html
·Recommendation: Recommendation: There's no link to skip to the content. The page has another way to skip the menu (marked areas), but a link at the start helps keyboard users a lot.
✓Correct: Correct: We didn't find any place where the focus gets trapped.
✗Issue: Issue: On 12 elements you can't see where the focus is. Keyboard users get lost. Fix: don't remove the focus outline (outline: none) or replace it with another clearly visible one.
✓Correct: Correct: Focus doesn't go into hidden elements.
✓Correct: Correct: We didn't find anything that can be clicked with the mouse but not used with the keyboard (custom-built things, such as menus or carousels, are worth testing by hand).
No visible focus, for example: «Café de Muestra, inicio», «Shop», «Cafés», «About us».
The images, one by one
We reviewed 6 images on your website one by one, comparing each with its description.
3 don't have a useful description. Here is the one we suggest: check it and copy it into the alt attribute.
The suggestions are written by a machine looking at the image: check them before using them. The comments in this review are in the language the analysis was requested in (Español).
Description that doesn't help
Es un nombre de archivo y no dice qué producto es.
Now: alt="IMG_2034.jpg"
Suggestion: alt="Bolsa de café de Colombia Huila, 250 gramos"
No description
No tiene texto alternativo y muestra un producto.
Now: no alt attribute
Suggestion: alt="Bolsa de café de Etiopía Yirgacheffe, 250 gramos"
Description that doesn't help
La palabra «foto» no explica qué producto se muestra.
Now: alt="foto"
Suggestion: alt="Bolsa de café descafeinado por proceso de agua, 250 gramos"
And 3 images with a good description.
What your buttons and links say
Screen reader users hear the name of every button and link. We reviewed the 23 that appear on your pages.
11 are hard to understand: they are in another language, use technical jargon, repeat each other or don't say where they lead. Fix: change the text or the aria-label to the one we suggest. The comments in this review are in the language the analysis was requested in (Español).
Another language · link
Now it says: “Shop” (3 times). Está en inglés y la página en español.
Suggestion: “Inicio”
Another language · link
Now it says: “About us” (3 times). Está en inglés y lleva a la página de contacto.
Suggestion: “Contacto”
Doesn't say where it leads · button
Now it says: “‹”. Un símbolo no dice qué hace el botón.
Suggestion: “Anterior”
Doesn't say where it leads · button
Now it says: “›”. Un símbolo no dice qué hace el botón.
Suggestion: “Siguiente”
Technical jargon · link
Now it says: “IMG_2034.jpg”. Es el nombre de un archivo, no dice adónde lleva.
Suggestion: “[Destino del enlace]”
Doesn't say where it leads · link
Now it says: “Leer más” (4 times). No dice qué se va a leer.
Suggestion: “Leer más sobre nuestros cafés”
Doesn't say where it leads · link
Now it says: “foto”. No dice qué muestra ni adónde lleva.
Suggestion: “[Descripción de la foto y destino]”
Another language · button
Now it says: “Subscribe” (3 times). Está en inglés y la página en español.
Suggestion: “Suscribirme”
Another language · button
Now it says: “Add to cart”. Está en inglés y la página en español.
Suggestion: “Añadir al carrito”
Doesn't say where it leads · link
Now it says: “Click here”. Está en inglés y no dice adónde lleva.
Suggestion: “Volver a la página de inicio”
Another language · button
Now it says: “Send”. Está en inglés y la página en español.
Suggestion: “Enviar mensaje”
Links that don't say where they lead
Screen readers let you jump from link to link. If ten links say “Read more”, the person can't tell which is which. Fix: make the text say where it goes (“Read more about shipping”) or add an aria-label.
«Leer más» · 4 times
«Click here» · 1 time
Accessibility statement
We didn't find it. Spain's Law 11/2023 requires the businesses within its scope to explain, in their general terms and conditions or an equivalent document and in an accessible format, how their service meets the accessibility requirements; the usual approach is an “Accessibility” page linked from the footer. Public administrations must also publish a statement, linked from every page, saying to what extent they comply, what content isn't accessible, when it was assessed and how to report a problem.
Here is a draft with the details from this report. Fill in what's in square brackets, check that everything is true and publish it.
Before publishing it, have a person review what this report doesn't cover: complete processes (searching, buying, signing up, paying), form error messages, pop-ups, videos and downloadable documents. If they find more issues, add them to the list.
Note: if your service falls within the scope of Spain's Law 11/2023 and doesn't comply, the law requires you to correct this and to inform the competent authority. Check with your adviser before publishing it.
Your draft: Accessibility statement
[Your company name] is committed to making its website cafedemuestra.example accessible, in accordance with Spain's Law 11/2023. As its technical reference it uses the UNE-EN 301549 standard, which includes the WCAG 2.1 level AA guidelines; we have also reviewed the new WCAG 2.2 criteria.
Description of the service
[Briefly describe your service, how it is provided and how it is used with a screen reader, keyboard or magnification.]
[To be reviewed by an expert before publishing.]
Compliance status
This website is not compliant with WCAG 2.1 level AA, for the reasons given below.
Non-accessible content
Buttons with no name (menu, search, close…) that can't be used with a screen reader.
Form fields with no label: screen reader users don't know what to type.
Empty links: a blind person hears “link” without knowing where it leads.
The website stops you from pinch-zooming on mobile.
Fields whose only name is the example text inside them: it disappears when you start typing, and some screen readers don't even read it.
Images with no description: a screen reader can't tell what they show.
Some images don't have a suitable description.
Some buttons and links have names that don't make sense with a screen reader.
On some elements you can't see where the focus is when navigating with the keyboard.
There are elements that can be clicked with the mouse but not used with the keyboard.
We are working to fix it before [planned date].
Preparation of this statement
Statement prepared on 2026-11-01 by self-assessment: automated analysis against WCAG 2.2 A and AA, automated keyboard-use tests and automated review of images and of the names of buttons and links[, and manual review of …].
Notes and contact details
If you find an accessibility problem or need the information in another format, email us at [email] or call us on [phone]. We will reply within [time limit: 20 working days for public administrations; for businesses, the one you set].
How to complain
If you think this service doesn't meet the accessibility requirements, you can file a complaint with [the competent authority for accessibility or consumer affairs].
The issues, one by one
1. Buttons with no name (menu, search, close…) that can't be used with a screen reader
Critical · 1 element on 1 of 3 pages · rule button-name
How to fix it. Give each button a name: visible text or aria-label ("Add to cart", "Close", "Search").
5. Fields whose only name is the example text inside them
It disappears when you start typing, and some screen readers don't even read it.
Serious · 6 elements on 3 of 3 pages · rule wa-placeholder
How to fix it. Add a visible <label> to each field (or, if it can't be visible, an aria-label). The placeholder can stay as an example, but it doesn't replace the label.
Critical · 1 element on 1 of 3 pages · rule image-alt
How to fix it. Add an alt attribute to each <img> describing what the image contributes (e.g. alt="Blue running shoe, side view"). If it's purely decorative, an empty alt="".
7. Low-contrast text, hard to read for people with low vision
Serious · 13 elements on 3 of 3 pages · rule color-contrast
How to fix it. Darken the text or lighten the background up to a contrast of 4.5:1 (3:1 for large text). The report shows each color pair that fails.
https://cafedemuestra.example/Code: Code: <p class="promo">Envío gratis a partir de 35 € · Tostamos cada lunes en pequeños lotes</p>Text #9a8775 on background #fffaf2: contrast 3.31:1, 4.5:1 needed.
https://cafedemuestra.example/contacto.htmlCode: Code: <p class="promo">Respondemos en menos de 24 horas laborables.</p>Text #9a8775 on background #fffaf2: contrast 3.31:1, 4.5:1 needed.
9. The page runs off the right edge when zoomed in or on a small phone
People who enlarge the text have to scroll sideways on every line.
Serious · 1 element on 1 of 3 pages · rule wa-reflow
How to fix it. Make the layout adapt to a width of 320 px: no fixed pixel widths, images with max-width: 100% and wide tables or blocks with their own scrolling.
https://cafedemuestra.example/ (on a mobile screen)Code: Code: <html> (the page overflows to the right at 320 px)
10. Headings that skip levels
The screen reader suggests that part of the page is missing.
Moderate · good practice · 1 element on 1 of 3 pages · rule heading-order
How to fix it. Use headings in order (<h1>, then <h2>, <h3>…) without skipping levels; change the size with CSS, not with the level.
