Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 5 REVIEW 3 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Form Accessibility

Action

5 of 8 controls have issues

REVIEW

5 of 8 controls have issues

5 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

3 control(s) properly labeled

8 controls

3 labeled

0 placeholder only

5 unlabeled

Control	Type	Label	Method
select	select	Language Translate Widget	aria-label
#a2a_copy_link_text	text	Copy link	for/id
#a2apage_find	text	Encuentra al instante cualquier servicio para añadir a	for/id
#goog-gt-votingInputSrcLang	text	(none)	none
#goog-gt-votingInputTrgLang	text	(none)	none
#goog-gt-votingInputSrcText	text	(none)	none
#goog-gt-votingInputTrgText	text	(none)	none
#goog-gt-votingInputVote	text	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Iframe Accessibility

2/5 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/5 iframe(s) missing title; 0 placeholder(s)

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.

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.

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

title Spiral | Our own tourism methodology in …

1.73:1

#000000

#6B093D

needs 4.5:1 (normal text)

16px · top of page (header area)

font Official start of our activities: Octobe…

1.73:1

#000000

#6B093D

needs 4.5:1 (normal text)

16px · top of page (header area)

font Skip to content

1.16:1

#000000

#300419

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

font Start

1.07:1

#000000

#1D0301

needs 4.5:1 (normal text)

16px · top of page (header area)

font The Spiral Method

1.25:1

#000000

#410604

needs 4.5:1 (normal text)

16px · above the fold

font Services

1.31:1

#000000

#460A08

needs 4.5:1 (normal text)

16px · above the fold

font About us

1.59:1

#000000

#630C07

needs 4.5:1 (normal text)

16px · above the fold

font Spiral Logbook

1.24:1

#000000

#3F0705

needs 4.5:1 (normal text)

16px · above the fold

font Questions and answers

1.34:1

#000000

#4B0806

needs 4.5:1 (normal text)

16px · above the fold

font Contact

1.71:1

#000000

#6E0908

needs 4.5:1 (normal text)

16px · above the fold

font SPIRAL, PATH TOWARDS THE INVISIBLE

2.15:1

#000000

#88140A

needs 4.5:1 (normal text)

16px · above the fold

font Information and transmission services fo…

1.46:1

#000000

#570B07

needs 4.5:1 (normal text)

16px · above the fold

font We design experiences and content to obs…

2.03:1

#000000

#7E1811

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

font "Stone Armchair", a work by Vicente More…

1.84:1

#000000

#760F08

needs 4.5:1 (normal text)

16px · mid-page

font Discover our services

2.32:1

#000000

#931108

needs 4.5:1 (normal text)

16px · mid-page

font Book route

2.47:1

#000000

#99150C

needs 4.5:1 (normal text)

16px · mid-page

font At Espiral, we have developed our own to…

1.89:1

#000000

#7A0E05

needs 4.5:1 (normal text)

16px · mid-page

font The Spiral Method starts with what's in …

2.49:1

#000000

#99180E

needs 4.5:1 (normal text)

16px · mid-page

font Tourism services for businesses and trav…

2.44:1

#000000

#981408

needs 4.5:1 (normal text)

16px · mid-page

font Our services include:

2.13:1

#000000

#881106

needs 4.5:1 (normal text)

16px · mid-page

2 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)

Element	Ratio	Required	FG	BG	Result
title Spiral \| Our own tou…	1.73:1	4.5:1	#000000	#6B093D	Fail
font Official start of ou…	1.73:1	4.5:1	#000000	#6B093D	Fail
font Skip to content	1.16:1	4.5:1	#000000	#300419	Fail
font Start	1.07:1	4.5:1	#000000	#1D0301	Fail
font The Spiral Method	1.25:1	4.5:1	#000000	#410604	Fail
font Services	1.31:1	4.5:1	#000000	#460A08	Fail
font About us	1.59:1	4.5:1	#000000	#630C07	Fail
font Spiral Logbook	1.24:1	4.5:1	#000000	#3F0705	Fail
font Questions and answer…	1.34:1	4.5:1	#000000	#4B0806	Fail
font Contact	1.71:1	4.5:1	#000000	#6E0908	Fail
font SPIRAL, PATH TOWARDS…	2.15:1	4.5:1	#000000	#88140A	Fail
font Information and tran…	1.46:1	4.5:1	#000000	#570B07	Fail
font We design experience…	2.03:1	4.5:1	#000000	#7E1811	Fail
font "Stone Armchair", a …	1.84:1	4.5:1	#000000	#760F08	Fail
font Discover our service…	2.32:1	4.5:1	#000000	#931108	Fail
font Book route	2.47:1	4.5:1	#000000	#99150C	Fail
font At Espiral, we have …	1.89:1	4.5:1	#000000	#7A0E05	Fail
font The Spiral Method st…	2.49:1	4.5:1	#000000	#99180E	Fail
font Tourism services for…	2.44:1	4.5:1	#000000	#981408	Fail
font Our services include…	2.13:1	4.5:1	#000000	#881106	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+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

4 headings

PASS

4 headings

Single H1 present

H1 SPIRAL, PATH TOWARDS THE INVISIBLE
H2 Information and transmission services for the territory from the province of Jaén
H3 We design experiences and content to observe the environment from new perspectives
H2 Our services include:

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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 8 images OK

PASS

All 8 images OK

1 decorative image(s) correctly marked

7 image(s) with good alt text

8 images 7 good alt text 1 decorative

All images have appropriate alt text.

Link & Button Quality

27 links, 4 buttons — all OK

PASS

27 links, 4 buttons — all OK

6 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /#email; /#whatsapp; https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fespiralturismo…; https://www.addtoany.com/add_to/pinterest?linkurl=https%3A%2F%2Fespiralturism…; https://translate.google.com; https://www.addtoany.com

21 link(s) with descriptive text

27 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/#email	E-mail	new tab	Add '(opens in new tab)' to text
/#whatsapp	WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.addtoany.com/add_to/facebook…	Share	new tab	Add '(opens in new tab)' to text
https://www.addtoany.com/add_to/pinteres…	Save	new tab	Add '(opens in new tab)' to text
https://translate.google.com	Translate	new tab	Add '(opens in new tab)' to text
https://www.addtoany.com	AddToAny	new tab	Add '(opens in new tab)' to text

25 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

/#email; /#whatsapp; https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fespiralturismo…; https://www.addtoany.com/add_to/pinterest?linkurl=https%3A%2F%2Fespiralturism…; https://translate.google.com; https://www.addtoany.com

Why this matters

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 Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "query" should use type="search" (currently type="text")

Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

8 form control(s) checked, no input-semantic issues

PASS

8 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

7 explicit tabindex attribute(s) checked, no anti-patterns

PASS

7 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 44 visible text node(s) render at >= 12 CSS pixels

PASS

All 44 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found - Espiral Turismo Inductivo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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 96/100 — 1 failing, 21 passed

PASS

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
Discover our services `a.wp-block-button__link > strong > font > font`
Book route `a.wp-block-button__link > strong > font > font`

These are opportunities to improve the legibility of your content.

○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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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.

●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 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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[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

○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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○No element has a `[tabindex]` value greater than 0

○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.

○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.