Skip to content
https://awwwards.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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
Info::
2 navigation landmark(s) detected
Info::
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 2 <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.
B
Heading Hierarchy
53 headings
REVIEW
53 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Site of the Day Apr 21, 2026 Score 7.32 of 10
  • H3 Ruinart - Digital fresco
  • H2 Latest
  • H3 Nominees
  • H3 HUPR
  • H3 HUPR
  • H3 PieterKoopt®
  • H3 PieterKoopt®
  • H3 Adcker
  • H3 Adcker
  • H2 Winners
  • H3 Recent Sitesof the Day.
  • H3 Shader Development Studio
  • H3 Shader Development Studio
  • H3 The Agency of Love & Logic
  • H3 The Agency of Love & Logic
  • H3 Evolve
  • H3 Evolve
  • H3 Studio X
  • H3 Studio X
  • H3 Max Mara - Jacket Circle
  • H3 Max Mara - Jacket Circle
  • H3 Ravi Klaassens
  • H3 Ravi Klaassens
  • H2 Academy
  • H3 Learn from thebest instructors.
  • H3 Learn UI Design with Figma from Scratch
  • H3 Nordic Design Intensive Course: Complete Branding
  • H3 Innovative Web Design in Figma: A Step-by-Step Process
  • H3 Learn Figma from 0 to 100 (10 Courses)
  • H2 Collections
  • H3 Explore a wide variety of collections.
  • H3 Illustration in Web Design
  • H3 CSS Animations
  • H2 Directory
  • H3 w.creators
  • H2 Báchoo
  • H2 AREA 17
  • H2 Positioner - Hotel Agency
  • H2 Blog
  • H3 Explore thesepopular posts.
  • H3 Shopify vs WooCommerce: What's the better?
  • H3 100 Best Free Fonts for Designers in 2025
  • H3 Trendy Gradients in Web Design
  • H3 30 Great Websites with Parallax Scrolling
  • H2 Market
  • H3 A curated marketplace for digital & physical products
  • H3 Aerin — A Motion-Driven Portfolio Template
  • H3 dom — Architecture & Interior Design Template
  • H3 Sites - Premium Design Agency Template [Framer]
  • H3 Accura — Free Accounting Framer Website Template
  • H3 Submit your website for visibility and recognition
  • H3 Get access to special pro features

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputtext(Search by Inspiration)placeholder only
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

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

<input type="text">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error 404 (Not Found) ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
A+
Alt Text Quality
All 64 images OK
PASS
All 64 images OK
Info::
14 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
64 images 50 good alt text 14 decorative
All images have appropriate alt text.
A
Favicon & Branding
5 icon(s) detected
PASS
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Awwwards
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Awwwards ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Awwwards Display Mode standalone Theme Color #3ea094 Background Color #f4f7f6 Icons 2 icon(s)
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)
ElementRatioRequiredFGBGResult
h2 Latest19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Winners19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Academy19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Collections19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Directory19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Blog19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Market19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Ruinart - Digital fr…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 HUPR19.77:13.0:1
#000000
#F8F8F8
Pass
h3 PieterKoopt®19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Adcker19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Recent Sites19.77:13.0:1
#000000
#F8F8F8
Pass
h3 of the Day.19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Shader Development S…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 The Agency of Love &…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Evolve19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Studio X19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Max Mara - Jacket Ci…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Ravi Klaassens19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Learn from the19.77:13.0:1
#000000
#F8F8F8
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.

A+
Lighthouse Accessibility Audits
Score 98/100 — 3 failing, 26 passed
PASS
98

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Instynct PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
UNCOMMON PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
Shader PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
The Agency of Love & Logic PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
Evolve PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
Jordan Gilroy PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
Adoratorio Studio PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
Sunny Side Up PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
Wondertabs PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
360&5 PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link
cpluscandco PRO li > div.users-credits__item > figure.avatar-name > a.avatar-name__link

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Name Sunny Side Up PRO View Wondertabs PRO View 360&5 PRO View cp… div.block > div.inner > div.box-table > table.tb-dotteds
○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
●Form elements have associated labels
●`[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 use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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.
○No element has a `[tabindex]` value greater than 0
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback