Skip to content
https://silkandwillow.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV 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

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

B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only
title Google
1.94:1
#000000
on
#2B3E5B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Sobre Google
1.37:1
#000000
on
#042353
needs 4.5:1 (normal text)
16px · top of page (header area)
a Tienda
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
a Gmail
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
a Imágenes
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
span Iniciar sesión
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
div Elige sobre qué quieres dar tu opinión
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
span Ver más
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
div Eliminar
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
div Eliminar
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a Más información
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
div Denunciar predicciones inadecuadas
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
div Ofrecido por Google en:
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a català
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page
a galego
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page
a euskara
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page
a English
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page
div España
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page
a Publicidad
3.39:1
#000000
on
#616161
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Antes de ir a Google3.39:13.0:1
#000000
#616161
Pass
title Google1.94:14.5:1
#000000
#2B3E5B
Fail
a Sobre Google1.37:14.5:1
#000000
#042353
Fail
a Tienda3.66:14.5:1
#000000
#666666
Fail
a Gmail3.66:14.5:1
#000000
#666666
Fail
a Imágenes3.66:14.5:1
#000000
#666666
Fail
span Iniciar sesión3.66:14.5:1
#000000
#666666
Fail
div Elige sobre qué qui…3.66:14.5:1
#000000
#666666
Fail
span Ver más3.66:14.5:1
#000000
#666666
Fail
div Eliminar3.66:14.5:1
#000000
#666666
Fail
div Eliminar3.66:14.5:1
#000000
#666666
Fail
a Más información3.66:14.5:1
#000000
#666666
Fail
div Denunciar prediccion…3.66:14.5:1
#000000
#666666
Fail
div Ofrecido por Google …3.66:14.5:1
#000000
#666666
Fail
a català3.66:14.5:1
#000000
#666666
Fail
a galego3.66:14.5:1
#000000
#666666
Fail
a euskara3.66:14.5:1
#000000
#666666
Fail
a English3.66:14.5:1
#000000
#666666
Fail
div España3.66:14.5:1
#000000
#666666
Fail
a Publicidad3.39:14.5:1
#000000
#616161
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 Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 Antes de ir a Google
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
10 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
11 images 1 good alt text 10 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#APjFqbtextareaBuscararia-label
btnKsubmitBuscar con Googlearia-label
btnIsubmitVoy a tener suertearia-label
btnKsubmitBuscar con Googlearia-label
btnIsubmitVoy a tener suertearia-label
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 8 passed
PASS
100

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.

○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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Document has a main landmark.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○Heading elements appear in a sequentially-descending order
○`<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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○Links have a discernible name
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Touch targets have sufficient size and spacing.
○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
○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.
○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