Skip to content
https://Cocinaldia.es

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
7
REVIEW
6
PASS
11
INFO
0
Checks
24
11 PASS 6 REVIEW 7 FIX
D
Landmark Structure
Action
12 landmarks
FIX
12 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Menú" SEARCH MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

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

D
Tabindex Anti-Patterns
Action
0 positive, 23 -1-on-focusable
FIX
0 positive, 23 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="sm-17902417684454683-1">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="sm-17902417684454683-3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
D
Iframe Accessibility
Action
6/8 iframe(s) missing title; 0 placeholder(s)
FIX
6/8 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.google.com/recaptcha/api2/aframe")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://googleads.g.doubleclick.net/pagead/html/r20260923/r20190131/zrt_lookup.…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
27 headings, 3 skip(s)
REVIEW
27 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Sitio web para  cocinillas
  • H2 Mis Gustos.
  • H2 me gusta
  • H2 me desagrada
  • H6 Me encanta cocinar, compartir recetas y trucos.... skipped
  • H3 Siempre me ha atraido esto de cocinar. Aquí os dejo los experimentos culinarios que he ido realizando, unas veces con más éxito que otras... Oido cocina !
  • H6 Si tienes alguna sugerencia, o tienes alguna receta que quieres compartir con todos nosotros, mándanos un e-mail skipped
  • H6 629 878 213
  • H6 info@cocinaldia.es
  • H6 629 878 213
  • H6 info@cocinaldia.es
  • H2 Síguenos
  • H2 Mapa del Sitio
  • H2 Información
  • H2 Ayuda-Contacto
  • H3 629 878 213
  • H3 info@cocinaldia.es
  • H2 SÍGUENOS
  • H2 Mapa Sitio
  • H2 + Info
  • H2 Contacto
  • H3 629 878 213
  • H3 info@cocinaldia.es
  • H3 © 2026 Cocinaldia. Todos los derechos reservados
  • H3 © 2026 Cocinaldia. Todos los derechos reservados
  • H5 Esta web usa cookies skipped
  • H4 Resumen de Privacidad

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

B
Mobile-Readable Font Sizes
98% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
98% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
1 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <a> 11.0px ("Aceptar todo").
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

16 pass 4 fail WCAG AA
title Cocinaldia - Recetas de Cocina
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Ir al contenido
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Inicio
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Sobre mi
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Sitio web para5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Mis5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Gustos.5.24:13.0:1
#000000
#7F7F7F
Pass
h2 me gusta5.24:13.0:1
#000000
#7F7F7F
Pass
h2 me desagrada5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Síguenos5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Mapa del Sitio5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Información5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Ayuda-Contacto5.24:13.0:1
#000000
#7F7F7F
Pass
h2 SÍGUENOS5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Mapa Sitio5.24:13.0:1
#000000
#7F7F7F
Pass
h2 + Info5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Contacto5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Siempre me ha atraid…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 © 2026 Cocinaldia. …5.24:13.0:1
#000000
#7F7F7F
Pass
h3 © 2026 Cocinaldia. …5.24:13.0:1
#000000
#7F7F7F
Pass
title Cocinaldia - Recetas…1.00:14.5:1
#000000
#000000
Fail
a Ir al contenido1.00:14.5:1
#000000
#000000
Fail
a Inicio1.00:14.5:1
#000000
#000000
Fail
a Sobre mi1.00:14.5:1
#000000
#000000
Fail

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
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 154 chars
Got: 1 >120-char heading(s)
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
All 26 images OK
PASS
All 26 images OK
Info::
26 image(s) with good alt text
26 images 26 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#elementor-search-form-390283bcsearchBuscarfor/id
#wt-cli-checkbox-necessarycheckboxNecesariasfor/id
#wt-cli-checkbox-no-necessarycheckboxNo necesariasfor/id
A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "es"
PASS
Lang attribute set to "es"
Info::
<html lang="es"> is set and valid
Got: es
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 29 passed
PASS
92

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
© 2026 Cocinaldia. Todos los derechos reservados div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title
Aceptar todo body.home > div#cookie-law-info-bar > span > a#wt-cli-accept-all-btn

These are opportunities to improve the legibility of your content.

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Si tienes alguna sugerencia, o tienes alguna receta que quieres compartir con t… div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h6.elementor-heading-title
Esta web usa cookies body.home > div#cookie-law-info-bar > h5.cli_messagebar_head

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-widget-container > div.elementor-icon-box-wrapper > div.elementor-icon-box-icon > a.elementor-icon div.elementor-widget-container > div.elementor-icon-box-wrapper > div.elementor-icon-box-icon > a.elementor-icon

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.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback