Accessibility

F

Heading Hierarchy

Action

50 headings, 5 skip(s)

FIX

50 headings, 5 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 The AI community building the future.
H2 Models
H4 google/gemma-4-31B-it skipped
H4 dealignai/Gemma-4-31B-JANG_4M-CRACK
H4 Jackrong/Qwen3.5-27B-Claude-4.6-Opus-Reasoning-Distilled
H4 netflix/void-model
H4 google/gemma-4-26B-A4B-it
H2 Spaces
H4 OmniVoice skipped
H4 Wan2.2 14B Preview
H4 FireRed Image Edit 1.0 Fast
H4 Qwen Image Multiple Angles 3D Camera
H4 Z Image Turbo
H2 Datasets
H4 ianncity/KIMI-K2.5-1000000x skipped
H4 nohurry/Opus-4.6-Reasoning-3000x-filtered
H4 lambda/hermes-agent-reasoning-traces
H4 open-index/hacker-news
H4 Crownelius/Opus-4.6-Reasoning-3300x
H2 The Home of Machine Learning
H3 The collaboration platform
H3 Move faster
H3 Explore all modalities
H3 Build your portfolio
H2 Accelerate your ML
H3 Team & Enterprise
H3 Inference Providers
H3 Compute
H2 More than 50,000 organizations are using Hugging Face
H4 Ai2 skipped
H4 AI at Meta
H4 Amazon
H4 Google
H4 Intel
H4 Microsoft
H4 Grammarly
H4 Writer
H2 Our Open Source
H4 Transformers skipped
H4 Diffusers
H4 Safetensors
H4 Hub Python Library
H4 Tokenizers
H4 TRL
H4 Transformers.js
H4 smolagents
H4 PEFT
H4 Datasets
H4 Text Generation Inference
H4 Accelerate

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

F

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

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

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

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

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.

D

Lighthouse Accessibility Audits

Action

Score 69/100 — 5 failing, 12 passed

FIX

69

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-full > div.flex > div.flex > button.relative `div.w-full > div.flex > div.flex > button.relative`
div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden `div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden`
div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden `div.absolute > a.bg-linear-to-r > div.flex > button.outline-hidden`

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.

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
Starting at $0.60/hour for GPU `div.shadow-xs > div.px-5 > div.flex > p.text-smd`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
google/gemma-4-31B-it `a.flex > div.w-full > header.flex > h4.text-md`
OmniVoice `div.text-white > div.flex > div.mb-0.5 > h4.overflow-hidden`
ianncity/KIMI-K2.5-1000000x `a.flex > div.w-full > header.flex > h4.text-md`
Ai2 `a.flex > div.overflow-hidden > div.flex > h4.truncate`
Transformers `div.container > div.relative > a.relative > h4.leading-tight!`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●Form elements have associated labels

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Document has a `<title>` element

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

●Document has a main landmark.

●Identical links have the same purpose.

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

○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 a valid value for its `[lang]` attribute

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

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

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

B

Landmark Structure

24 landmarks

REVIEW

24 landmarks

<main> landmark present

Multiple <main> landmarks (6 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

B

Link & Button Quality

4 issue(s) across 84 links and 5 buttons

REVIEW

4 issue(s) across 84 links and 5 buttons

1 link(s) open in new tab without warning

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

Got: https://endpoints.huggingface.co

4 button(s) with no accessible text

83 link(s) with descriptive text

84 links

0 empty

0 generic text

1 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://endpoints.huggingface.co	Inference Endpoints	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

84 links and buttons have descriptive text

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

https://endpoints.huggingface.co

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

B

404 Error Page

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

B

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.

A+

Alt Text Quality

All 28 images OK

PASS

All 28 images OK

2 decorative image(s) correctly marked

26 image(s) with good alt text

28 images 26 good alt text 2 decorative

All images have appropriate alt text.

A

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	(Search models, datasets, users...)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The AI community bui…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Models	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Spaces	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Datasets	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The Home of Machine …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Accelerate your ML	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More than 50,000 org…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our Open Source	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The collaboration pl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Move faster	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Explore all modaliti…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Build your portfolio	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Team & Enterprise	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Inference Providers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Compute	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Hugging Face – The…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Hugging Face	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Models	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Datasets	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Spaces	21.00:1	4.5:1	#000000	#FFFFFF	Pass

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.