Skip to content
https://hackster.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Hackster
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name Hackster ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name Hackster Icons 6 icon(s)
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::
1 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 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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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 (missing!) 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

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
Heading Hierarchy
4 headings
REVIEW
4 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 About Us
  • H3 Legal Thingies
  • H3 Find Us On Social
  • H3 Visit Our Avnet Family

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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Hackster.io ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
20 icon(s) detected
REVIEW
20 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Info::
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: hackster
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 Detected ✓Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
h3 About Us
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Legal Thingies
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Find Us On Social
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Visit Our Avnet Family
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 About Us1.66:13.0:1
#000000
#333333
Fail
h3 Legal Thingies1.66:13.0:1
#000000
#333333
Fail
h3 Find Us On Social1.66:13.0:1
#000000
#333333
Fail
h3 Visit Our Avnet Fami…1.66:13.0:1
#000000
#333333
Fail
title Hackster.io - The co…21.00:14.5:1
#000000
#FFFFFF
Pass
div Projects21.00:14.5:1
#000000
#FFFFFF
Pass
div Leave Feedback21.00:14.5:1
#000000
#FFFFFF
Pass
a Log in18.26:14.5:1
#000000
#EFEFEF
Pass
a Sign up21.00:14.5:1
#000000
#FFFFFF
Pass
a Projects21.00:14.5:1
#000000
#FFFFFF
Pass
a Projects21.00:14.5:1
#000000
#FFFFFF
Pass
a Channels21.00:14.5:1
#000000
#FFFFFF
Pass
a Channels21.00:14.5:1
#000000
#FFFFFF
Pass
a News21.00:14.5:1
#000000
#FFFFFF
Pass
a Contests21.00:14.5:1
#000000
#FFFFFF
Pass
a Events21.00:14.5:1
#000000
#FFFFFF
Pass
a Videos21.00:14.5:1
#000000
#FFFFFF
Pass
p Hackster Staff Picks21.00:14.5:1
#000000
#FFFFFF
Pass
p News Article21.00:14.5:1
#000000
#FFFFFF
Pass
a EW26: A Field Report…21.00:14.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.

C
Lighthouse Accessibility Audits
Action
Score 72/100 — 6 failing, 15 passed
REVIEW
72

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.

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.cards__body__F1VX8 > div > span.project_card__author__sz77c > button.tooltip__btn__LUywc div.cards__body__F1VX8 > div > span.project_card__author__sz77c > button.tooltip__btn__LUywc

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 > div.hckui__layout__flexJustifySpaceBetween > label.hckui__layout__fullWidth > input.hckui__util__srOnly div > div.hckui__layout__flexJustifySpaceBetween > label.hckui__layout__fullWidth > input.hckui__util__srOnly
div > div.hckui__layout__flexJustifySpaceBetween > label.hckui__layout__fullWidth > input.hckui__util__srOnly div > div.hckui__layout__flexJustifySpaceBetween > label.hckui__layout__fullWidth > input.hckui__util__srOnly
div > div.hckui__layout__flexJustifySpaceBetween > label.hckui__layout__fullWidth > input.hckui__util__srOnly div > div.hckui__layout__flexJustifySpaceBetween > label.hckui__layout__fullWidth > input.hckui__util__srOnly

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.horizontal_scroll__itemsContainer__lzrLR > div.promoted_content__mobileView__cZ0rX > div.promoted_content__mobileCard__lcyFf > a.promoted_content__mobileImageWrapper__jttTt div.horizontal_scroll__itemsContainer__lzrLR > div.promoted_content__mobileView__cZ0rX > div.promoted_content__mobileCard__lcyFf > a.promoted_content__mobileImageWrapper__jttTt
div.horizontal_scroll__itemsContainer__lzrLR > div.promoted_content__mobileView__cZ0rX > div.promoted_content__mobileCard__lcyFf > a.promoted_content__mobileImageWrapper__jttTt div.horizontal_scroll__itemsContainer__lzrLR > div.promoted_content__mobileView__cZ0rX > div.promoted_content__mobileCard__lcyFf > a.promoted_content__mobileImageWrapper__jttTt
div.horizontal_scroll__itemsContainer__lzrLR > div.view_all__scrollerItemProject__JYIQp > div.project_card__card__aQbxM > a.project_card__imageContainer__ouaOv div.horizontal_scroll__itemsContainer__lzrLR > div.view_all__scrollerItemProject__JYIQp > div.project_card__card__aQbxM > a.project_card__imageContainer__ouaOv
div.horizontal_scroll__itemsContainer__lzrLR > div.view_all__scrollerItemProject__JYIQp > div.project_card__card__aQbxM > a.project_card__imageContainer__ouaOv div.horizontal_scroll__itemsContainer__lzrLR > div.view_all__scrollerItemProject__JYIQp > div.project_card__card__aQbxM > a.project_card__imageContainer__ouaOv
div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a
div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a
div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a
div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a
div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a
div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a
div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a
div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a div.view_all__scrollerItem__QQtka > div.simple_logo_card__card__zThaA > div.simple_logo_card__image__QGVFP > a

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
Sign up div.nav-row > div.hckui__layout__wrapper1170 > div.nav-inner > a.hckui__buttons__lg

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.cards__body__F1VX8 > div > span.project_card__author__sz77c > button.tooltip__btn__LUywc div.cards__body__F1VX8 > div > span.project_card__author__sz77c > button.tooltip__btn__LUywc
Hackster Overview div.responsive-footer-section > ul.list-unstyled > li > a
Hackster for Business div.responsive-footer-section > ul.list-unstyled > li > a
Hackster Pro div.responsive-footer-section > ul.list-unstyled > li > a
Help Articles div.responsive-footer-section > ul.list-unstyled > li > a
Brand Resources div.responsive-footer-section > ul.list-unstyled > li > a
Sitemap div.responsive-footer-section > ul.list-unstyled > li > a
Terms of Service div.responsive-footer-section > ul.list-unstyled > li > a
Contest Rules div.responsive-footer-section > ul.list-unstyled > li > a
Code of Conduct div.responsive-footer-section > ul.list-unstyled > li > a
Privacy Policy div.responsive-footer-section > ul.list-unstyled > li > a
Facebook div.responsive-footer-section > ul.list-unstyled > li > a
Instagram div.responsive-footer-section > ul.list-unstyled > li > a
LinkedIn div.responsive-footer-section > ul.list-unstyled > li > a
X div.responsive-footer-section > ul.list-unstyled > li > a
Avnet div > ul.list-unstyled > li > a
Premier Farnell div > ul.list-unstyled > li > a
element14 div > ul.list-unstyled > li > a
Newark div > ul.list-unstyled > li > a

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.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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 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
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○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.
A
Alt Text Quality
3 of 6 images have issues
PASS
3 of 6 images have issues
Warning::
3 image(s) with filename as alt text
Info::
3 image(s) with good alt text
6 images 3 good alt text 3 generic
IssueCount
filename3 image(s)
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="searchInput">
Info::
3 control(s) properly labeled
4 controls
3 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
lightradionone
deviceradionone
darkradionone
#searchInputtext(Search)placeholder only

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

<input type="text" id="searchInput">

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

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

Send Feedback