Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DMobile-Readable Font SizesAction67% of visible text renders at >= 12 CSS px (36 below threshold)FIX
F404 Error PageActionSoft 404 detectedFIX
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
FFavicon & BrandingAction1 icon(s) detectedFIX
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
ALandmark Structure6 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 Hierarchy12 headingsPASS
- H1 La mesa está puesta.
- H2 Desayuno marroquí, desde primera hora
- H2 Para empezar, para compartir
- H2 De la cocina a la mesa
- H2 Pistacho, miel y agua de azahar
- H2 Una cocina de familia, en la calle de Londres
- H2 Tu mesa, tu pedido, en un minuto
- H2 Dónde estamos
- H3 Horario
- H3 Horario
- H3 Dirección
- H3 Reservar
A+Heading Text QualityAll 12 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityAll 9 images OKPASS
A+Form AccessibilityNo form controlsPASS
ALink & Button Quality36 links, 8 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.google.com/maps/search/?api=… | Abrir en Google Maps | new tab | Add '(opens in new tab)' to text |
| https://www.google.com/maps/search/?api=… | Calle de Londres 52Torrejón d… | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/ya_habibi_madr… | @ya_habibi_madrid | new tab | Add '(opens in new tab)' to text |
| https://www.google.com/maps/search/?api=… | Abrir en Google Maps | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/ya_habibi_madr… | new tab | Add '(opens in new tab)' to text | |
| https://www.google.com/maps/search/?api=… | Calle de Londres 52Torrejón d… | new tab | Add '(opens in new tab)' to text |
| https://www.google.com/maps/search/?api=… | Abrir en Google Maps | new tab | Add '(opens in new tab)' to text |
Add '(opens in new tab)' to link text or aria-label.
https://www.google.com/maps/search/?api=1&query=Ya+Habibi%2C+Calle+de+Londres…; https://www.google.com/maps/search/?api=1&query=Ya+Habibi%2C+Calle+de+Londres…; https://www.instagram.com/ya_habibi_madrid/; https://www.google.com/maps/search/?api=1&query=Ya+Habibi%2C+Calle+de+Londres…; https://www.instagram.com/ya_habibi_madrid/; https://www.google.com/maps/search/?api=1&query=Ya+Habibi%2C+Calle+de+Londres…; https://www.google.com/maps/search/?api=1&query=Ya+Habibi%2C+Calle+de+Londres…
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
A+Form Input TypesNo form controls on this pagePASS
A+Form Input QualityNo form controls on this pagePASS
A+Mobile Keyboard & AutofillNo form controls -- mobile keyboard check is N/APASS
A+Document LanguageLang attribute set to "es"PASS
A+Tabindex Anti-Patterns1 explicit tabindex attribute(s) checked, no anti-patternsPASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth2 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 La mesa está puesta… | 18.65:1 | 3.0:1 | #000000 | #F7F1E3 | Pass |
| h2 Desayuno marroquí, … | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h2 Para empezar, para c… | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h2 De la cocina a la me… | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h2 Pistacho, miel y agu… | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h2 Una cocina de famili… | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h2 Tu mesa, tu pedido, … | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h2 Dónde estamos | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h3 Horario | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h3 Horario | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h3 Dirección | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| h3 Reservar | 18.15:1 | 3.0:1 | #000000 | #F4EEE0 | Pass |
| title Ya Habibi — Restau… | 18.76:1 | 4.5:1 | #000000 | #F7F2E3 | Pass |
| span Ya Habibi | 18.76:1 | 4.5:1 | #000000 | #F7F2E3 | Pass |
| span Cocina libanesa | 18.65:1 | 4.5:1 | #000000 | #F7F1E3 | Pass |
| a Inicio | 18.65:1 | 4.5:1 | #000000 | #F7F1E3 | Pass |
| a Menú | 18.65:1 | 4.5:1 | #000000 | #F7F1E3 | Pass |
| a Opiniones | 18.65:1 | 4.5:1 | #000000 | #F7F1E3 | Pass |
| a Reservar | 18.65:1 | 4.5:1 | #000000 | #F7F1E3 | Pass |
| a Contacto | 18.65:1 | 4.5:1 | #000000 | #F7F1E3 | 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.
A+Lighthouse Accessibility AuditsScore 96/100 — 2 failing, 20 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.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
03 — COCINA section.relative > div.container > div.reveal > p.overline |
05 — RESERVA div.relative > div.relative > div > p.overline |
Elige día, hora y comensales, con o sin pedido anticipado. Paga online el depós… div.relative > div.relative > div > p.mt-4 |
Ver menú div.relative > div.relative > div.flex > a.inline-flex |
HORARIO footer#contacto > div.container > div > h3.overline |
DIRECCIÓN footer#contacto > div.container > div > h3.overline |
RESERVAR footer#contacto > div.container > div > h3.overline |
Todos los precios incluyen IVA. Alérgenos disponibles en el menú. footer#contacto > div.border-t > div.container > p |
Ya Habibi · Torrejón de Ardoz div.border-t > div.container > div.flex > span |
Panel div.border-t > div.container > div.flex > a.underline |
These are opportunities to improve the legibility of your content.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Ya Habibi
COCINA LIBANESA div.flex > header.sticky > div.container > a |