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 3 REVIEW 6 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-ss87os

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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

Got: https://localai.hex7.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

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

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

Action

70% of visible text renders at >= 12 CSS px (34 below threshold)

REVIEW

70% of visible text renders at >= 12 CSS px (34 below threshold)

34 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: <span> 8.0px ("PRIVATE INTELLIGENCE"); <span> 8.0px ("CATALONIA"); <span> 11.0px ("Private Local AI"); <span> 11.0px ("Human support, private infrastructure, p..."); <span> 11.0px ("IA Local Privada").

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 Local AI — IA Local. Private, on-site …

1.11:1

#000000

#0B120E

needs 3.0:1 (large text)

32px · top of page (header area)

h2 Run intelligence on your own hardware.

1.11:1

#000000

#0B120E

needs 3.0:1 (large text)

24px · mid-page

h2 Su inteligencia, en su propio hardware.

1.11:1

#000000

#0B120E

needs 3.0:1 (large text)

24px · mid-page

h2 Votre intelligence, sur votre propre mat…

1.11:1

#000000

#0B120E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Su intel·lig artificial, en su propio m…

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Connect it to everything you have.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Connecta con todo lo que tienes.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Connectez-le à tout ce que vous avez.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Connecta amb todo lo que tienes.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your documents, answerable.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sus documentos, preguntables.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ves documents, interrogables.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sus documentos, preguntables.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 In the room, within the law.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Dentro de la sala, dentro de la ley.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Dans la salle, dans la loi.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Dins de la sala, dins de la llei.

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

24px · bottom of viewport

h3 llama.cpp

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 FreeToken

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Strata

1.11:1

#000000

#0A120D

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Local AI — IA Loca…	1.11:1	3.0:1	#000000	#0B120E	Fail
h2 Run intelligence on …	1.11:1	3.0:1	#000000	#0B120E	Fail
h2 Su inteligencia, en …	1.11:1	3.0:1	#000000	#0B120E	Fail
h2 Votre intelligence, …	1.11:1	3.0:1	#000000	#0B120E	Fail
h2 Su intel·lig artifi…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Connect it to everyt…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Connecta con todo lo…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Connectez-le à tout…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Connecta amb todo lo…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Your documents, answ…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Sus documentos, preg…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Ves documents, inter…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Sus documentos, preg…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 In the room, within …	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Dentro de la sala, d…	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Dans la salle, dans …	1.11:1	3.0:1	#000000	#0A120D	Fail
h2 Dins de la sala, din…	1.11:1	3.0:1	#000000	#0A120D	Fail
h3 llama.cpp	1.11:1	3.0:1	#000000	#0A120D	Fail
h3 FreeToken	1.11:1	3.0:1	#000000	#0A120D	Fail
h3 Strata	1.11:1	3.0:1	#000000	#0A120D	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

40 headings

PASS

40 headings

Single H1 present

H1 Local AI — IA Local. Private, on-site AI systems for organisations across Catalonia and the Perpignan–Barcelona corridor.
H2 Run intelligence on your own hardware.
H2 Su inteligencia, en su propio hardware.
H2 Votre intelligence, sur votre propre matériel.
H2 Su intel·lig artificial, en su propio maquinari.
H3 llama.cpp
H3 FreeToken
H3 Strata
H3 Avalon
H3 Mixture of Experts
H3 DDR over VRAM
H3 Uncensored Models
H3 GSQ · RCO quantization
H2 Connect it to everything you have.
H2 Connecta con todo lo que tienes.
H2 Connectez-le à tout ce que vous avez.
H2 Connecta amb todo lo que tienes.
H3 Blender MCP
H3 CADcraft MCP
H3 Artcraft MCP
H3 SearXNG MCP
H2 Your documents, answerable.
H2 Sus documentos, preguntables.
H2 Ves documents, interrogables.
H2 Sus documentos, preguntables.
H3 RAGMill
H3 GuardRAG
H3 ZettaBrain
H2 In the room, within the law.
H2 Dentro de la sala, dentro de la ley.
H2 Dans la salle, dans la loi.
H2 Dins de la sala, dins de la llei.
H3 No International Transfer
H3 Your Accountability, Whole
H3 The Schrems II Lesson
H3 Best Practice: Local
H3 The Air-Gap Insulation
H3 GDPR by Design
H3 SOC 2 · ISO 27001 · HIPAA
H3 The CLOUD Act Trap

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

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: - H1: 125 chars

Got: 1 >120-char heading(s)

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

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

2 links, 5 buttons — all OK

PASS

2 links, 5 buttons — all OK

2 link(s) with descriptive text

2 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

7 links and buttons have descriptive text

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 "en"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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

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, 20 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
COPYRIGHT © 2026 HEXSEVEN INTERNET SOLUTIONS `body > main.stage > footer.pagefoot > p`

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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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

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

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