Skip to content
https://owasp.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
4 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 4 <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
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <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 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

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
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="searchString" id="searchString">; <input type="search" name="searchString" id="searchString">
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchStringsearchsearch inputaria-label
#searchStringsearch(Search OWASP.org)placeholder only
#searchStringsearch(Search OWASP.org)placeholder only

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

<input type="search" name="searchString" id="searchString">; <input type="search" name="searchString" id="searchString">

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

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 404 - Not Found | OWASP Foundation ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA 1 pass AA only
h1 Explore the world
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
32px · bottom of viewport
h1 of cyber security
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Are you an OWASP Member?
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
24px · bottom of viewport
h2 7ASecurity Platinum Corporate Supporter
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
24px · bottom of viewport
h2 It’s our 25th Anniversary! Get ready f…
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Spotlight: Automattic
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Corporate Supporters
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Upcoming at OWASP
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Recent OWASP News & Opinions
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Upcoming Conferences
2.12:1
#000000
on
#434343
needs 3.0:1 (large text)
19px · bottom of viewport
title OWASP Foundation, the Open Source Founda…
2.08:1
#000000
on
#233E81
needs 4.5:1 (normal text)
16px · top of page (header area)
p Please support the OWASP mission to impr…
2.08:1
#000000
on
#233E81
needs 4.5:1 (normal text)
16px · top of page (header area)
a Donate Now!
2.08:1
#000000
on
#233E81
needs 4.5:1 (normal text)
16px · top of page (header area)
button PROJECTS
2.08:1
#000000
on
#233E81
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Explore the world2.12:13.0:1
#000000
#434343
Fail
h1 of cyber security2.12:13.0:1
#000000
#434343
Fail
h2 Are you an OWASP Mem…2.12:13.0:1
#000000
#434343
Fail
h2 7ASecurity Platinum …2.12:13.0:1
#000000
#434343
Fail
h2 It’s our 25th Anni…2.12:13.0:1
#000000
#434343
Fail
h2 Spotlight: Automatti…2.12:13.0:1
#000000
#434343
Fail
h2 Corporate Supporters2.12:13.0:1
#000000
#434343
Fail
h3 Upcoming at OWASP2.12:13.0:1
#000000
#434343
Fail
h3 Recent OWASP News & …2.12:13.0:1
#000000
#434343
Fail
h3 Upcoming Conferences2.12:13.0:1
#000000
#434343
Fail
title OWASP Foundation, th…2.08:14.5:1
#000000
#233E81
Fail
p Please support the O…2.08:14.5:1
#000000
#233E81
Fail
a Donate Now!2.08:14.5:1
#000000
#233E81
Fail
button PROJECTS2.08:14.5:1
#000000
#233E81
Fail
a Browse All Projects.…5.38:14.5:1
#000000
#6982AB
Pass
a Contribute to projec…9.29:14.5:1
#000000
#98AFC7
Pass
a OWASP Top Ten9.29:14.5:1
#000000
#98AFC7
Pass
a OWASP Application Se…9.29:14.5:1
#000000
#98AFC7
Pass
a OWASP GenAI Security…21.00:14.5:1
#000000
#FFFFFF
Pass
a OWASP AI Exchange21.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 77/100 — 6 failing, 22 passed
REVIEW
77

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
header > div.header-wrapper > nav.alt-nav > a.menu-toggler header > div.header-wrapper > nav.alt-nav > a.menu-toggler
nav.alt-nav > ul.mobile-menu > li > a.menu-toggler nav.alt-nav > ul.mobile-menu > li > a.menu-toggler

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.

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 > form > div.search-div > button#search-button div > form > div.search-div > button#search-button

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.main-wrapper > div > section#upcoming > iframe div.main-wrapper > div > section#upcoming > iframe

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
Donate Now! header > div#banner > p > a
Donate header > div.mobile > div > a.cta-button
Join header > div.mobile > div > a.cta-button
More details section#featured_events > div#ev0 > p > a
Jordan Harband and Przemyslaw (Rogue) Roguski div.main-wrapper > section.homepage-blog > p.author > a
, April 15, 2026 div.main-wrapper > section.homepage-blog > p.author > span
...read more main > div.main-wrapper > section.homepage-blog > a
Start a project div > div.idea-container > div.start > a.cta-button
Announcing the Retirement of OWASP Meetup Platform section.news-events > ul > li > a
, January 13, 2026 section.news-events > ul > li > span
The OWASP Foundation appoints Stacey Ebbs as Communications & Marketing Manager section.news-events > ul > li > a
, November 19, 2025 section.news-events > ul > li > span
OWASP Certified Secure Software Developer section.news-events > ul > li > a
, October 3, 2025 section.news-events > ul > li > span
GSoC 2025 Recap section.news-events > ul > li > a
, October 1, 2025 section.news-events > ul > li > span
OWASP Global AppSec EU 2026 - Vienna, Austria section.news-events > ul > li > a
, June 22-26, 2026 section.news-events > ul > li > span
OWASP Global AppSec USA 2026 - San Francisco, CA section.news-events > ul > li > a
, November 2-6, 2026 section.news-events > ul > li > span
OWASP Global AppSec EU 2027 - Vienna, Austria section.news-events > ul > li > a
, June 21-25, 2027 section.news-events > ul > li > span
OWASP Global AppSec USA 2027 - Atlanta, GA section.news-events > ul > li > a
, September 20-24, 2027 section.news-events > ul > li > span
Edit on GitHub div.repo > a > div.reset-3c756112--menuItemIcon-206eb252 > span
Become a corporate supporter div.member-wrapper > section.member-list > div.member-cta > a.callout-link
General Disclaimer footer > section.footer-wrapper > p.disclaimer > a

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header-wrapper > nav.alt-nav > ul.mobile-menu > li div.header-wrapper > nav.alt-nav > ul.mobile-menu > li
search input div.header-wrapper > nav.alt-nav > ul.mobile-menu > li
MAKE A DONATION div.header-wrapper > nav.alt-nav > ul.mobile-menu > li
BECOME A MEMBER div.header-wrapper > nav.alt-nav > ul.mobile-menu > li
SITEMAP div.header-wrapper > nav.alt-nav > ul.mobile-menu > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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 > form > div.search-div > button#search-button div > form > div.search-div > button#search-button

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>`
●`[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.
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`<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.
○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+
Heading Hierarchy
10 headings
PASS
10 headings
Info::
Single H1 present
  • H1 Explore the worldof cyber security
  • H2 Are you an OWASP Member?
  • H2 7ASecurity Platinum Corporate Supporter
  • H2 It’s our 25th Anniversary! Get ready for an unforgettable experience at the OWASP Global AppSec EU Conference!
  • H2 Bridging the Gap in Product Lifecycle Management: How OpenEoX and CLE Work Together
  • H3 Upcoming at OWASP
  • H3 Recent OWASP News & Opinions
  • H3 Upcoming Conferences
  • H2 Spotlight: Automattic
  • H2 Corporate Supporters
A
Alt Text Quality
11 of 17 images have issues
PASS
11 of 17 images have issues
Warning::
11 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
17 images 5 good alt text 1 decorative 11 generic
IssueCount
generic11 image(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback