Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DTabindex Anti-PatternsAction1 positive, 163 -1-on-focusableFIX
FFavicon & BrandingAction2 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy20 headings, 1 skip(s)REVIEW
- H2 Selecciona idioma
- H2 Otras webs del Ayuntamiento de Barcelona
- H1 Instrucciones para usuarios de teclado
- H1 Mercats de Barcelona duplicate H1
- H1 Instructions for screen readers and keyboard users duplicate H1
- H1 Mercats a un clic duplicate H1
- H3 Enlaces relacionados: skipped
- H2 Seccions principals
- H2 Adreça
- H2 Contacte
- H2 Butlletins
- H2 Síguenos en:
- H3 ¿Qué es una cookie?
- H3 ¿Para qué utilizamos las cookies?
- H3 Consentimiento en el uso de las cookies
- H3 ¿Qué tipo de cookies utilizamos?
- H3 Cambios en la política de cookies
- H3 ¿Puedo eliminar las cookies?
- H3 ¿Qué pasa si bloqueo las cookies?
- H3 Cómo gestionar sus preferencias sobre cookies
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
CLink & Button QualityAction4 issue(s) across 190 links and 35 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.barcelona.cat/es/ | Logo Ayuntamiento de Barcelona | new tab | Add '(opens in new tab)' to text |
| https://ajuntament.barcelona.cat/es/ | El Ayuntamiento | new tab | Add '(opens in new tab)' to text |
| https://ajuntament.barcelona.cat/es/cana… | Contacto | new tab | Add '(opens in new tab)' to text |
| https://seuelectronica.ajuntament.barcel… | Trámites | new tab | Add '(opens in new tab)' to text |
| https://seuelectronica.ajuntament.barcel… | Trabaja en el Ayuntamiento | new tab | Add '(opens in new tab)' to text |
| https://www.barcelona.cat/infobarcelona/… | Noticias | new tab | Add '(opens in new tab)' to text |
| https://guia.barcelona.cat/es/ | Agenda | new tab | Add '(opens in new tab)' to text |
| https://geoportal.barcelona.cat/planolbc… | Mapa | new tab | Add '(opens in new tab)' to text |
| https://www.barcelona.cat/com-shi-va/es/ | Cómo llegar | new tab | Add '(opens in new tab)' to text |
| https://inscripcions-ajuntament.barcelon… | Contacto Abrir en una ventana… | new tab | Add '(opens in new tab)' to text |
| https://inscripcions-ajuntament.barcelon… | Contacto Abrir en una ventana… | new tab | Add '(opens in new tab)' to text |
| https://www.youtube-nocookie.com/embed/u… | Reproduce el video 1 | img no alt | Add alt attribute to the image |
| (empty) | empty | Add link text or aria-label | |
| https://www.mercatsaunclic.barcelona/ | Mercats a un clic Abrir en una… | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/MercatsBCN/ | Facebook. Abrir en una ventana… | new tab | Add '(opens in new tab)' to text |
| https://www.flickr.com/photos/mercatsdeb… | Flickr. Abrir en una ventana n… | new tab | Add '(opens in new tab)' to text |
| https://instagram.com/MercatsBCN | Instagram. Abrir en una ventan… | new tab | Add '(opens in new tab)' to text |
| https://www.youtube.com/@mercatsbcn | Youtube. Abrir en una ventana … | new tab | Add '(opens in new tab)' to text |
| https://www.barcelona.cat/es | Abrir en una ventana nueva | new tab | Add '(opens in new tab)' to text |
| https://support.microsoft.com/es-es/wind… | Internet Explorer | new tab | Add '(opens in new tab)' to text |
| https://support.google.com/chrome/answer… | Chrome | new tab | Add '(opens in new tab)' to text |
| https://support.mozilla.org/es/kb/habili… | Firefox | new tab | Add '(opens in new tab)' to text |
| https://support.apple.com/es-es/HT201265 | Safari | new tab | Add '(opens in new tab)' to text |
| https://help.opera.com/en/latest/web-pre… | Opera | new tab | Add '(opens in new tab)' to text |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
a#skip-gallery-node-85
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://www.barcelona.cat/es/; https://ajuntament.barcelona.cat/es/; https://ajuntament.barcelona.cat/es/canales-de-comunicacion-ciudadana; https://seuelectronica.ajuntament.barcelona.cat/oficinavirtual/es/; https://seuelectronica.ajuntament.barcelona.cat/processosselectius/es/; https://www.barcelona.cat/infobarcelona/es/; https://guia.barcelona.cat/es/; https://geoportal.barcelona.cat/planolbcn/es/; https://www.barcelona.cat/com-shi-va/es/; https://inscripcions-ajuntament.barcelona.cat/index.php/157249?lang=es (+12 more)
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
button#cboxPrevious; button#cboxNext; button#cboxSlideshow
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
B404 Error PageHTTP 404, custom pageREVIEW
ALandmark Structure15 landmarksPASS
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
A+Heading Text QualityAll 20 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityAll 17 images OKPASS
A+Form AccessibilityAll 4 controls labeledPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #bcnbrand-search-input | text | Busca en la web | for/id |
| #lw-category-checkbox-preferences | checkbox | none | |
| #lw-category-checkbox-analytics | checkbox | none | |
| #lw-category-checkbox-marketing | checkbox | none |
A+Form Input Types1 input(s) using type=text where a specific type would helpPASS
A+Form Input Quality4 form control(s) checked, no input-semantic issuesPASS
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
A+Document LanguageLang attribute set to "es"PASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 87 visible text node(s) render at >= 12 CSS pixelsPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Instrucciones para u… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Instructions for scr… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Mercats a un clic | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Selecciona idioma | 6.49:1 | 3.0:1 | #000000 | #069DB4 | Pass |
| h2 Otras webs del Ayunt… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Seccions principals | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Adreça | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Contacte | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Butlletins | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Síguenos en: | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Enlaces relacionados… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Mercats a un clic | … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| button Castellano | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Selecciona un idioma | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Català | 7.13:1 | 4.5:1 | #000000 | #07A5BE | Pass |
| a Castellano | 7.37:1 | 4.5:1 | #000000 | #08A8C0 | Pass |
| a English | 7.53:1 | 4.5:1 | #000000 | #09A9C9 | Pass |
| span Busca en la web | 8.27:1 | 4.5:1 | #000000 | #17B2CB | Pass |
| label Busca en la web | 17.80:1 | 4.5:1 | #000000 | #D7F1F6 | Pass |
| span Otras webs | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
ALighthouse Accessibility AuditsScore 90/100 — 3 failing, 28 passedPASS
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Names and labels
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.bcnbrand-navs-wrapper > nav.bcnbrand-navbar-search > div#bcnbrand-search-dropdown > button#bcnbrand-search-toggle div.bcnbrand-navs-wrapper > nav.bcnbrand-navbar-search > div#bcnbrand-search-dropdown > button#bcnbrand-search-toggle |
div.bcnbrand-navs-wrapper > nav.bcnbrand-navbar-shortcuts > div#bcnbrand-shortcuts-dropdown > button#bcnbrand-shortcuts-toggle div.bcnbrand-navs-wrapper > nav.bcnbrand-navbar-shortcuts > div#bcnbrand-shortcuts-dropdown > button#bcnbrand-shortcuts-toggle |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Navigation
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Pasar al contenido principal body.page-node-85 > a.visually-hidden |
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Enlaces relacionados: div.col-md-6 > div.field > div.paragraph > h3 |
These are opportunities to improve keyboard navigation in your application.