Skip to content
https://hackerone.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
5 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | HackerOne ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h2 User account menu
1.00:1
#000000
on
#000003
needs 3.0:1 (large text)
24px · above the fold
h2 Main navigation
1.35:1
#000000
on
#262329
needs 3.0:1 (large text)
24px · above the fold · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Not every vulnerabil…14.62:13.0:1
#000000
#D6D7DD
Pass
h1 Fix the ones that do…14.62:13.0:1
#000000
#D6D7DD
Pass
h2 User account menu1.00:13.0:1
#000000
#000003
Fail
h2 Main navigation1.35:13.0:1
#000000
#262329
Fail
h2 Main navigation14.62:13.0:1
#000000
#D6D7DD
Pass
h2 We protect the world…14.62:13.0:1
#000000
#D6D7DD
Pass
h2 One platform, dual f…14.62:13.0:1
#000000
#D6D7DD
Pass
h2 What's new at Hacker…14.62:13.0:1
#000000
#D6D7DD
Pass
h2 Numbers that speak f…14.62:13.0:1
#000000
#D6D7DD
Pass
h2 Real-world impact, b…14.62:13.0:1
#000000
#D6D7DD
Pass
h2 Protecting the world…14.62:13.0:1
#000000
#D6D7DD
Pass
h2 Ready to reduce risk…14.62:13.0:1
#000000
#D6D7DD
Pass
h2 Help build a safer i…14.62:13.0:1
#000000
#D6D7DD
Pass
h3 How Snap is pioneeri…14.62:13.0:1
#000000
#D6D7DD
Pass
h3 Adobe's formula for …14.62:13.0:1
#000000
#D6D7DD
Pass
h3 AI Red Teaming14.62:13.0:1
#000000
#D6D7DD
Pass
h3 Bug Bounty14.62:13.0:1
#000000
#D6D7DD
Pass
h3 Code14.62:13.0:1
#000000
#D6D7DD
Pass
h3 Agentic PTaaS14.62:13.0:1
#000000
#D6D7DD
Pass
h3 Challenge14.62:13.0:1
#000000
#D6D7DD
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
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
2 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "block-hackerone-useraccountmenu-menu" MAIN ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer

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

A+
Heading Hierarchy
21 headings
PASS
21 headings
Info::
Single H1 present
  • H2 User account menu
  • H2 Main navigation
  • H2 Main navigation
  • H1 Not every vulnerability matters. Fix the ones that do.
  • H2 We protect the world's top innovators.
  • H3 How Snap is pioneering AI with HackerOne AI Red Teaming
  • H3 Adobe's formula for staying ahead of risk, with HackerOne's global research community
  • H2 One platform, dual force: 
Human minds + AI power
  • H3 AI Red Teaming
  • H3 Bug Bounty
  • H3 Code
  • H3 Agentic PTaaS
  • H3 Challenge
  • H3 Response
  • H3 Hai
  • H2 What's new at HackerOne
  • H2 Numbers that speak for themselves
  • H2 Real-world impact, backed by CISOs
  • H2 Protecting the world's top innovators
  • H2 Ready to reduce risk continuously?
  • H2 Help build a safer internet
A+
Alt Text Quality
All 27 images OK
PASS
All 27 images OK
Info::
1 decorative image(s) correctly marked
Info::
26 image(s) with good alt text
27 images 26 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#FirstNametext*First Name:for/id
#LastNametext*Last Name:for/id
#Emailemail*Business Email:for/id
#Companytext*Company:for/id
#Titletext*Job Title:for/id
#Security_Objective__cselect*What is your security objective?for/id
#Countryselect*Country:for/id
#honeypottext*Honeypot:for/id
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 29 passed
PASS
92

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
header.text-white > div.mobile-navigation > div.px-6 > button#hamburger-btn header.text-white > div.mobile-navigation > div.px-6 > button#hamburger-btn

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
See how it works div.items-center > div.paragraph > div.cta-component > a.cta-primary
The HackerOne Platform div.section-inner > div.container > div.product-layout-header > div.field
Research Report a.relative > div.cta-card-item-content > div.content-top > div.cta-card-eyebrow
Research Report a.relative > div.cta-card-item-content > div.content-top > div.cta-card-eyebrow

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
●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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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 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
●No element has a `[tabindex]` value greater than 0
●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
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○`<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.
○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.

Send Feedback