Browse & Analyze

Browse recent website audits and performance trends

Explore technology stacks detected across the web

Side-by-side technology comparisons and market share

Curated technology stacks and the sites that use them

Editorial deep-dives on the state of web performance

Browse and download favicons from analyzed websites

Learn

Common questions about BeaverCheck scores and checks

How we calculate scores across 100+ checks

The story behind BeaverCheck and the team

Practical guides to fix common web performance issues

Migration Guides

Step-by-step guides for moving between web technologies

Definitions for performance, SEO, and web platform terms

Contrast Checker

Check WCAG color contrast ratios between any two colors

Inspect HTTP response headers for any URL

Analyze SSL/TLS certificate details and chain

Look up DNS records for any domain

Redirect Checker

Trace the full redirect chain for any URL

Real-user INP and Core Web Vitals from Google's Chrome UX Report.

RESTful API for programmatic website audits

Embed an auto-updating health score badge on your site

https://web.gencat.cat

Accessibility

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

SCORE

74

GRADE

C

FIX

7

REVIEW

4

PASS

13

INFO

0

Checks

24

13 PASS 4 REVIEW 7 FIX

D

Landmark Structure

Action

5 landmarks

FIX

5 landmarks

No <main> landmark found

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

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

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

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

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, 20 -1-on-focusable

FIX

0 positive, 20 -1-on-focusable

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

tabindex="-1" on naturally-focusable <button>

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

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 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

Search

Skip Link

Labeled Navigation 3 <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

Link & Button Quality

Action

4 issue(s) across 246 links and 6 buttons

REVIEW

4 issue(s) across 246 links and 6 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /ca/inici/actualitat/tot-comenca-a-casa; /ca/inici/actualitat/estiu; /ca/inici/actualitat/tot-comenca-a-casa; /ca/inici/actualitat/estiu

11 link(s) open in new tab without warning

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

Got: https://ovt.gencat.cat/carpetaciutadana360/mfe-main-app/#/acces; https://pressupostos2026.cat/; https://canalempresa.gencat.cat/; https://ovt.gencat.cat/gsitfc/AppJava/generic/conqxsGeneric.do?webFormId=391&…; https://www.facebook.com/gencat/; https://www.instagram.com/gencat/; https://www.linkedin.com/company/generalitat-de-catalunya/; https://www.tiktok.com/@gencat; https://x.com/gencat; https://gen.cat/telegram (+1 more)

231 link(s) with descriptive text

246 links

4 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://ovt.gencat.cat/carpetaciutadana3…	Àrea privada S'obre en …	new tab	Add '(opens in new tab)' to text
https://pressupostos2026.cat/	Pressupostos 2026 - gencat.cat	new tab	Add '(opens in new tab)' to text
https://canalempresa.gencat.cat/	Empreses i professionals - gen…	new tab	Add '(opens in new tab)' to text
/ca/inici/actualitat/tot-comenca-a-casa	(empty)	empty	Add link text or aria-label
/ca/inici/actualitat/estiu	(empty)	empty	Add link text or aria-label
/ca/inici/actualitat/tot-comenca-a-casa	(empty)	empty	Add link text or aria-label
/ca/inici/actualitat/estiu	(empty)	empty	Add link text or aria-label
https://ovt.gencat.cat/gsitfc/AppJava/ge…	S'obre en una nova pestanya …	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/gencat/	S'obre en una nova pestanya	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/gencat/	S'obre en una nova pestanya	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/general…	S'obre en una nova pestanya	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@gencat	S'obre en una nova pestanya	new tab	Add '(opens in new tab)' to text
https://x.com/gencat	S'obre en una nova pestanya	new tab	Add '(opens in new tab)' to text
https://gen.cat/telegram	S'obre en una nova pestanya	new tab	Add '(opens in new tab)' to text
https://gen.cat/whatsapp	S'obre en una nova pestanya	new tab	Add '(opens in new tab)' to text

237 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/ca/inici/actualitat/tot-comenca-a-casa; /ca/inici/actualitat/estiu; /ca/inici/actualitat/tot-comenca-a-casa; /ca/inici/actualitat/estiu

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://ovt.gencat.cat/carpetaciutadana360/mfe-main-app/#/acces; https://pressupostos2026.cat/; https://canalempresa.gencat.cat/; https://ovt.gencat.cat/gsitfc/AppJava/generic/conqxsGeneric.do?webFormId=391&…; https://www.facebook.com/gencat/; https://www.instagram.com/gencat/; https://www.linkedin.com/company/generalitat-de-catalunya/; https://www.tiktok.com/@gencat; https://x.com/gencat; https://gen.cat/telegram (+1 more)

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

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

C

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 El portal únic de la Generalitat de Cat…

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Dispositiu per l'eclipsi solar

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Actualitat

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Destaquem

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Directe a

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Necessites ajuda?

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Ajuts per crear franges de protecció co…

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Un de cada quatre vehicles matriculats f…

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 El nou vehicle que garanteix les comunic…

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Vaga a l'Aeroport del Prat: coneix els t…

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ajuts per crear franges de protecció co…

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Un de cada quatre vehicles matriculats f…

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 El nou vehicle que garanteix les comunic…

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Vaga a l'Aeroport del Prat: coneix els t…

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tot comença a casa

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 A l'estiu...

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tot comença a casa

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 A l'estiu...

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ciutadania

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 La Generalitat

1.66:1

#000000

on

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 El portal únic de l…	1.66:1	3.0:1	#000000	#333333	Fail
h2 Dispositiu per l'ecl…	1.66:1	3.0:1	#000000	#333333	Fail
h2 Actualitat	1.66:1	3.0:1	#000000	#333333	Fail
h2 Destaquem	1.66:1	3.0:1	#000000	#333333	Fail
h2 Directe a	1.66:1	3.0:1	#000000	#333333	Fail
h2 Necessites ajuda?	1.66:1	3.0:1	#000000	#333333	Fail
h3 Ajuts per crear fran…	1.66:1	3.0:1	#000000	#333333	Fail
h3 Un de cada quatre ve…	1.66:1	3.0:1	#000000	#333333	Fail
h3 El nou vehicle que g…	1.66:1	3.0:1	#000000	#333333	Fail
h3 Vaga a l'Aeroport de…	1.66:1	3.0:1	#000000	#333333	Fail
h3 Ajuts per crear fran…	1.66:1	3.0:1	#000000	#333333	Fail
h3 Un de cada quatre ve…	1.66:1	3.0:1	#000000	#333333	Fail
h3 El nou vehicle que g…	1.66:1	3.0:1	#000000	#333333	Fail
h3 Vaga a l'Aeroport de…	1.66:1	3.0:1	#000000	#333333	Fail
h3 Tot comença a casa	1.66:1	3.0:1	#000000	#333333	Fail
h3 A l'estiu...	1.66:1	3.0:1	#000000	#333333	Fail
h3 Tot comença a casa	1.66:1	3.0:1	#000000	#333333	Fail
h3 A l'estiu...	1.66:1	3.0:1	#000000	#333333	Fail
h3 Ciutadania	1.66:1	3.0:1	#000000	#333333	Fail
h3 La Generalitat	1.66:1	3.0:1	#000000	#333333	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.

B

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 22 passed

REVIEW

84

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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wrapper > div.header-top__wrapper > div.mobile-actions > div.nav-mobile `div.wrapper > div.header-top__wrapper > div.mobile-actions > div.nav-mobile`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Powered by `div#ppms_cm_popup_overlay > div#ppms_cm_popup_wrapper > div#ppms_cm_footer > span#ppms_cm_footer__powered_by`

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.hero-banner__content > div.hero-banner__search > div.hero-search__wrapper > input#search-input-hero `div.hero-banner__content > div.hero-banner__search > div.hero-search__wrapper > input#search-input-hero`

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.hero-banner__content > div.hero-banner__search > div.hero-search__wrapper > a.button `div.hero-banner__content > div.hero-banner__search > div.hero-search__wrapper > a.button`
div#swiper-wrapper-4b6a0969f08f80d6 > div.gencat-card__manual-card > div.gencat-card__footer > a.gencat-card__link `div#swiper-wrapper-4b6a0969f08f80d6 > div.gencat-card__manual-card > div.gencat-card__footer > a.gencat-card__link`
div#swiper-wrapper-4b6a0969f08f80d6 > div.gencat-card__manual-card > div.gencat-card__footer > a.gencat-card__link `div#swiper-wrapper-4b6a0969f08f80d6 > div.gencat-card__manual-card > div.gencat-card__footer > a.gencat-card__link`

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

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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○Skip links are focusable.

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

A+

Heading Hierarchy

21 headings

PASS

21 headings

Single H1 present

H1 El portal únic de la Generalitat de Catalunya
H2 Dispositiu per l'eclipsi solar
H2 Actualitat
H3 Ajuts per crear franges de protecció contra incendis
H3 Un de cada quatre vehicles matriculats fins al juliol és elèctric
H3 El nou vehicle que garanteix les comunicacions en situacions d'emergència
H3 Vaga a l'Aeroport del Prat: coneix els teus drets com a passatger
H3 Ajuts per crear franges de protecció contra incendis
H3 Un de cada quatre vehicles matriculats fins al juliol és elèctric
H3 El nou vehicle que garanteix les comunicacions en situacions d'emergència
H3 Vaga a l'Aeroport del Prat: coneix els teus drets com a passatger
H2 Destaquem
H3 Tot comença a casa
H3 A l'estiu...
H3 Tot comença a casa
H3 A l'estiu...
H2 Directe a
H3 Ciutadania
H3 La Generalitat
H3 Seu electrònica
H2 Necessites ajuda?

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

1 of 49 images have issues

PASS

1 of 49 images have issues

1 image(s) with generic alt text

24 decorative image(s) correctly marked

24 image(s) with good alt text

49 images 24 good alt text 24 decorative 1 generic

Issue	Count
generic	1 image(s)

A

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="text" name="hero-banner-search" id="search-input-hero">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#header-search-input-0	text	Cerca	for/id
#search-input-hero	text	(none)	none

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

<input type="text" name="hero-banner-search" id="search-input-hero">

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

A

Form Input Types

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

PASS

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

Input "header-search-input-0" should use type="search" (currently type="text")

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

Input "hero-banner-search" should use type="search" (currently type="text")

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

A+

Form Input Quality

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

PASS

2 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 "ca"

PASS

Lang attribute set to "ca"

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

Got: ca

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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+

Mobile-Readable Font Sizes

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

PASS

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

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

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback