Skip to content
https://obsproject.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
F
Alt Text Quality
Action
5 of 26 images have issues
FIX
5 of 26 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
10 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
26 images 11 good alt text 10 decorative 5 missing
IssueCount
missing5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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::
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
3 landmarks
REVIEW
3 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
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

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
5 headings, 1 skip(s)
REVIEW
5 headings, 1 skip(s)
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 OBS Studio
  • H3 Select macOS Version skipped
  • H1 Features duplicate H1
  • H1 Create Professional Productions duplicate H1
  • H1 Collaborative Creativity duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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 Error | OBS ✓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::
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 OBS Studio
1.43:1
#000000
on
#162458
needs 3.0:1 (large text)
32px · mid-page
h1 Features
1.18:1
#000000
on
#0C1633
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Create Professional Productions
1.18:1
#000000
on
#0C1633
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Collaborative Creativity
1.18:1
#000000
on
#0C1633
needs 3.0:1 (large text)
32px · bottom of viewport
h3 Select macOS Version
1.67:1
#000000
on
#202D6F
needs 3.0:1 (large text)
19px · bottom of viewport
title Open Broadcaster Software | OBS
1.63:1
#000000
on
#1C2B71
needs 4.5:1 (normal text)
16px · top of page (header area)
div OBS
1.63:1
#000000
on
#1C2B71
needs 4.5:1 (normal text)
16px · top of page (header area)
div Open Broadcaster Software
1.63:1
#000000
on
#1C2B71
needs 4.5:1 (normal text)
16px · top of page (header area)
span ®️
1.63:1
#000000
on
#1C2B71
needs 4.5:1 (normal text)
16px · top of page (header area)
span Discord
1.63:1
#000000
on
#1C2B71
needs 4.5:1 (normal text)
16px · above the fold
span Twitter
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · above the fold
span Mastodon
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · above the fold
span GitHub
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · above the fold
i Contribute
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · above the fold
a Home
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · above the fold
a Download
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · above the fold
a News
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · above the fold
a Help
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · above the fold
a Forum
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · mid-page
span Latest Release
1.43:1
#000000
on
#162458
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 OBS Studio1.43:13.0:1
#000000
#162458
Fail
h1 Features1.18:13.0:1
#000000
#0C1633
Fail
h1 Create Professional …1.18:13.0:1
#000000
#0C1633
Fail
h1 Collaborative Creati…1.18:13.0:1
#000000
#0C1633
Fail
h3 Select macOS Version1.67:13.0:1
#000000
#202D6F
Fail
title Open Broadcaster Sof…1.63:14.5:1
#000000
#1C2B71
Fail
div OBS1.63:14.5:1
#000000
#1C2B71
Fail
div Open Broadcaster Sof…1.63:14.5:1
#000000
#1C2B71
Fail
span ®️1.63:14.5:1
#000000
#1C2B71
Fail
span Discord1.63:14.5:1
#000000
#1C2B71
Fail
span Twitter1.43:14.5:1
#000000
#162458
Fail
span Mastodon1.43:14.5:1
#000000
#162458
Fail
span GitHub1.43:14.5:1
#000000
#162458
Fail
i Contribute1.43:14.5:1
#000000
#162458
Fail
a Home1.43:14.5:1
#000000
#162458
Fail
a Download1.43:14.5:1
#000000
#162458
Fail
a News1.43:14.5:1
#000000
#162458
Fail
a Help1.43:14.5:1
#000000
#162458
Fail
a Forum1.43:14.5:1
#000000
#162458
Fail
span Latest Release1.43:14.5:1
#000000
#162458
Fail

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 71/100 — 7 failing, 14 passed
REVIEW
71

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Windows div.pagewidth > div.main_blurb > div#latestVersions > div.latest_icon
macOS div.pagewidth > div.main_blurb > div#latestVersions > div.latest_icon
Linux div.pagewidth > div.main_blurb > div#latestVersions > div.latest_icon

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.

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
Contribute div#SocialButtons > div#ContributeButton > a > i.icon-heart

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Resources section div.fourth_blurb > div.blurb_text > p > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#SocialButtons > div#DiscordButton > a > img.icon-discord div#SocialButtons > div#DiscordButton > a > img.icon-discord
div#SocialButtons > div#MastodonButton > a > img.icon-mastodon div#SocialButtons > div#MastodonButton > a > img.icon-mastodon
div.pagewidth > div.main_blurb > div.demo_obs-window > img div.pagewidth > div.main_blurb > div.demo_obs-window > img
div.footer_left > div.footer_row > a > img.icon-discord div.footer_left > div.footer_row > a > img.icon-discord

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.

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
Čeština footer#footer > div.languages > p > a
Dansk footer#footer > div.languages > p > a
Deutsch footer#footer > div.languages > p > a
Euskara footer#footer > div.languages > p > a
ру́сский footer#footer > div.languages > p > a
Svenska footer#footer > div.languages > p > a
українська footer#footer > div.languages > p > a
中文(简体) footer#footer > div.languages > p > 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.

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
Ideas div.footer_extra > div.footer_right > div.footer_items > a
○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
●`[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
●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
●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
○Buttons have an accessible name
○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
○Form elements have associated labels
○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.
○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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback