Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-btmjvx

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://nomicalc.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://nomicalc.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #1f2937

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

1 <nav> landmark(s) found

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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Mobile-Readable Font Sizes

99% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

99% of visible text renders at >= 12 CSS px (1 below threshold)

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: <p> 10.9px ("Bienvenido a bordo").

Favicon & Branding

6 icon(s) detected

REVIEW

6 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

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

h1 NomiCalc – Calculadora de nómina y co…

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

32px · mid-page

h2 NomiCalc

2.10:1

#000000

#21407F

needs 3.0:1 (large text)

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

h2 🧾 ¿Qué es NomiCalc?

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ✈️ Empresas disponibles

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ⚙️ Cómo funciona

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 💰 ¿Por qué usar NomiCalc?

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 📊 Funcionalidades principales

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 🤝 Proyecto creado por y para trabajad…

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 💙 Apoyar el proyecto

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Transparencia y metodología

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Cookies y publicidad

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 ¿Te ayuda NomiCalc?

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ⚠️ Aviso importante

1.06:1

#000000

#09090B

needs 3.0:1 (large text)

19px · bottom of viewport

title NomiCalc – Calculadora de nómina y co…

2.45:1

#000000

#224899

needs 4.5:1 (normal text)

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

p Gestión de turnos laborales Automático…

1.43:1

#000000

#1F2937

needs 4.5:1 (normal text)

16px · top of page (header area)

span Tutorial

1.27:1

#000000

#171F2D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Entrar

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Crear cuenta

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Inicio

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Inicio

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

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
h1 NomiCalc – Calcula…	1.06:1	3.0:1	#000000	#09090B	Fail
h2 NomiCalc	2.10:1	3.0:1	#000000	#21407F	Fail
h2 🧾 ¿Qué es NomiC…	1.06:1	3.0:1	#000000	#09090B	Fail
h2 ✈️ Empresas disp…	1.06:1	3.0:1	#000000	#09090B	Fail
h2 ⚙️ Cómo funcion…	1.06:1	3.0:1	#000000	#09090B	Fail
h2 💰 ¿Por qué usar…	1.06:1	3.0:1	#000000	#09090B	Fail
h2 📊 Funcionalidades…	1.06:1	3.0:1	#000000	#09090B	Fail
h2 🤝 Proyecto creado…	1.06:1	3.0:1	#000000	#09090B	Fail
h2 💙 Apoyar el proye…	1.06:1	3.0:1	#000000	#09090B	Fail
h2 Transparencia y meto…	1.06:1	3.0:1	#000000	#09090B	Fail
h2 Cookies y publicidad	1.06:1	3.0:1	#000000	#09090B	Fail
h3 ¿Te ayuda NomiCalc?	1.06:1	3.0:1	#000000	#09090B	Fail
h3 ⚠️ Aviso importa…	1.06:1	3.0:1	#000000	#09090B	Fail
title NomiCalc – Calcula…	2.45:1	4.5:1	#000000	#224899	Fail
p Gestión de turnos l…	1.43:1	4.5:1	#000000	#1F2937	Fail
span Tutorial	1.27:1	4.5:1	#000000	#171F2D	Fail
span Entrar	1.00:1	4.5:1	#000000	#000000	Fail
span Crear cuenta	1.00:1	4.5:1	#000000	#000000	Fail
span Inicio	1.00:1	4.5:1	#000000	#000000	Fail
span Inicio	1.00:1	4.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 Hierarchy

13 headings

PASS

13 headings

Single H1 present

H2 NomiCalc
H1 NomiCalc – Calculadora de nómina y convenios para trabajadores de rampa
H2 🧾 ¿Qué es NomiCalc?
H2 ✈️ Empresas disponibles
H2 ⚙️ Cómo funciona
H2 💰 ¿Por qué usar NomiCalc?
H2 📊 Funcionalidades principales
H2 🤝 Proyecto creado por y para trabajadores
H2 💙 Apoyar el proyecto
H3 ¿Te ayuda NomiCalc?
H3 ⚠️ Aviso importante
H2 Transparencia y metodología
H2 Cookies y publicidad

A+

Heading Text Quality

All 13 heading(s) have substantive, well-formed text

PASS

All 13 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

1 of 2 images have issues

PASS

1 of 2 images have issues

1 image(s) with generic alt text

1 image(s) with good alt text

2 images 1 good alt text 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

25 links, 10 buttons — all OK

PASS

25 links, 10 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://ko-fi.com/nomicalc; https://discord.com/invite/XwCZQFC2qA; https://instagram.com/nomicalc; https://www.instagram.com/nomicalc/; https://discord.gg/XwCZQFC2qA

20 link(s) with descriptive text

25 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://ko-fi.com/nomicalc	Apoyar con un café	new tab	Add '(opens in new tab)' to text
https://discord.com/invite/XwCZQFC2qA	Únete al Discord	new tab	Add '(opens in new tab)' to text
https://instagram.com/nomicalc	@nomicalc	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/nomicalc/	Instagram	new tab	Add '(opens in new tab)' to text
https://discord.gg/XwCZQFC2qA	Discord	new tab	Add '(opens in new tab)' to text

30 links and buttons have descriptive text

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

https://ko-fi.com/nomicalc; https://discord.com/invite/XwCZQFC2qA; https://instagram.com/nomicalc; https://www.instagram.com/nomicalc/; https://discord.gg/XwCZQFC2qA

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

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "es"

PASS

Lang attribute set to "es"

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

Got: es

A+

Tabindex Anti-Patterns

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

PASS

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

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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+

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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 24 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
Apoyar con un café `main.max-w-4xl > section.mb-8 > div.flex > a.inline-flex`

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○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

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