Skip to content
https://osticket.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Heading Hierarchy
Action
20 headings, 3 skip(s)
FIX
20 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Try out the best cloud-hosted help desk platform for 30 days
  • H4 Thank you for signing up for a 30-day free trial! skipped
  • H1 Subscribe to osTicket Mailing Lists
  • H5 DOWNLOAD skipped
  • H5 INSTALL SOFTWARE
  • H5 Ready To Use
  • H5 Need a Cloud-Hosted Solution Instead?
  • H4 SOME OF OUR FEATURES
  • H5 Dashboard Reports
  • H5 Ticket Filters
  • H5 Configurable Help Topic
  • H5 Customer Support Portal
  • H5 Service Level Agreements
  • H5 And Much More!
  • H4 We're not the only ones excited about osTicket...
  • H5 Thousands of customers in over 190 countries trust and use osTicket for customer support.
  • H1 Get Started For Free Today! duplicate H1
  • H5 No Credit Card or Commitment Required skipped
  • H3 Make Happy Customers
  • H4 Navigation

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

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

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

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
10 of 11 controls have issues
REVIEW
10 of 11 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::
9 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="su-fname" id="signUpFName">; <input type="text" name="su-lname" id="signUpLName">; <input type="text" name="su-comp" id="signUpCompName">; <input type="text" name="su-url" id="signUpCompUrl">; <input type="email" name="su-email" id="signUpEmail">; <input type="text" name="name" id="ostDFName">; <input type="text" name="name" id="ostDLName">; <input type="email" name="email" id="ostDEmail">; <input type="text" name="company" id="finalDComp">
Info::
1 control(s) properly labeled
11 controls
1 labeled
9 placeholder only
1 unlabeled
ControlTypeLabelMethod
#industryselectIndustry:for/id
#signUpLNametext(Last Name)placeholder only
#signUpCompNametext(Company Name)placeholder only
#signUpCompUrltext(subdomain)placeholder only
#signUpEmailemail(Work Email Address)placeholder only
#signUpFNametext(First Name)placeholder only
#ostDFNametext(First Name)placeholder only
#ostDLNametext(Last Name)placeholder only
#ostDEmailemail(Email Address)placeholder only
#finalDComptext(Company)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" name="su-fname" id="signUpFName">; <input type="text" name="su-lname" id="signUpLName">; <input type="text" name="su-comp" id="signUpCompName">; <input type="text" name="su-url" id="signUpCompUrl">; <input type="email" name="su-email" id="signUpEmail">; <input type="text" name="name" id="ostDFName">; <input type="text" name="name" id="ostDLName">; <input type="email" name="email" id="ostDEmail">; <input type="text" name="company" id="finalDComp">

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 Page not found – osTicket | Support Ticketing System ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
h1 Subscribe to osTicket Mailing Lists
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Get Started For Free Today!
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
32px · bottom of viewport
h3 Make Happy Customers
1.48:1
#000000
on
#2B2B2B
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Subscribe to osTicke…1.48:13.0:1
#000000
#2B2B2B
Fail
h1 Get Started For Free…1.48:13.0:1
#000000
#2B2B2B
Fail
h2 Try out the best clo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Make Happy Customers1.48:13.0:1
#000000
#2B2B2B
Fail
title osTicket | Support T…21.00:14.5:1
#000000
#FFFFFF
Pass
div .supportsystem.com14.71:14.5:1
#000000
#ACE2E0
Pass
option Choose an industry8.54:14.5:1
#000000
#2FB7B2
Pass
option Education14.71:14.5:1
#000000
#ACE2E0
Pass
option Healthcare21.00:14.5:1
#000000
#FFFFFF
Pass
option Technology (SaaS)21.00:14.5:1
#000000
#FFFFFF
Pass
option Government Facilitie…21.00:14.5:1
#000000
#FFFFFF
Pass
option Hospitality21.00:14.5:1
#000000
#FFFFFF
Pass
option Manufacturing21.00:14.5:1
#000000
#FFFFFF
Pass
option Logistics21.00:14.5:1
#000000
#FFFFFF
Pass
option Finance21.00:14.5:1
#000000
#FFFFFF
Pass
option Human Resources21.00:14.5:1
#000000
#FFFFFF
Pass
option Automotive21.00:14.5:1
#000000
#FFFFFF
Pass
option Real Estate21.00:14.5:1
#000000
#FFFFFF
Pass
option Legal Services13.40:14.5:1
#000000
#9ED9DB
Pass
option NGO’s & Nonprofits12.31:14.5:1
#000000
#8DD2D5
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 4 failing, 15 passed
REVIEW
82

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.

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
Make. Happy. Customers. div.container > div.slider-content > div.slider-content-text > span
LEARN MORE div.slider-content > div.main-slider-btn-wrap > a.btn > span.text
Simply select what features you need in the downloads section div.kc-col-container > div.kc-elm > div.info-box-content > div.info-box-text
Install our software fast with our easy-to-follow installation process div.kc-col-container > div.kc-elm > div.info-box-content > div.info-box-text
Our easy-to-use software will help you get started in no time div.kc-col-container > div.kc-elm > div.info-box-content > div.info-box-text
Try SupportSystem! div.kc-col-container > div.kc-elm > div.info-box-content > a.read-more
Our rich and simple dashboard keeps you up-to-date on your help desk statistics div.kc_wrapper > div.kc-elm > div.info-box-content > div.info-box-text
Our powerful ticket filtering system makes sure the right tickets goes to the r… div.kc_wrapper > div.kc-elm > div.info-box-content > div.info-box-text
Add, edit, and delete your help desk topics that suit your preference div.kc_wrapper > div.kc-elm > div.info-box-content > div.info-box-text
Robust customer support portal system to help your business maintain happy cust… div.kc_wrapper > div.kc-elm > div.info-box-content > div.info-box-text
Simply set your business hours and our system will handle the rest leaving you … div.kc_wrapper > div.kc-elm > div.info-box-content > div.info-box-text
osTicket comes pack with tons of awesome features you have to try out yourself div.kc_wrapper > div.kc-elm > div.info-box-content > div.info-box-text
View All Features div.kc_wrapper > div.kc-elm > a.btn > span.text
GET STARTED div.kc_wrapper > div.kc-elm > a.btn > span.text
GET STARTED div.kc-col-container > div.kc-elm > a.btn > span.text
osTicket is a widely used and trusted open source support ticketing system. Eas… div.row > div.col-lg-7 > div.heading > p.heading-text
Features div.menus-wrap > ul#menu-footer-menu-1 > li > a
Editions div.menus-wrap > ul#menu-footer-menu-1 > li > a
Cloud-hosted div.menus-wrap > ul#menu-footer-menu-1 > li > a
Forum div.menus-wrap > ul#menu-footer-menu-1 > li > a
Blog div.menus-wrap > ul#menu-footer-menu-1 > li > a
About osTicket div.menus-wrap > ul#menu-footer-menu-2 > li > a
Careers div.menus-wrap > ul#menu-footer-menu-2 > li > a
FAQ div.menus-wrap > ul#menu-footer-menu-2 > li > a
Contact div.menus-wrap > ul#menu-footer-menu-2 > li > a
Privacy div.menus-wrap > ul#menu-footer-menu-2 > li > a
Terms div.menus-wrap > ul#menu-footer-menu-2 > li > a
Sitemap div.menus-wrap > ul#menu-footer-menu-2 > li > a
Copyright © 2026 osTicket.com, an Enhancesoft product div.container > div.row > div.col-lg-12 > span.site-copyright-text
Enhancesoft div.row > div.col-lg-12 > span.site-copyright-text > a

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
Enhancesoft div.row > div.col-lg-12 > span.site-copyright-text > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
No Credit Card or Commitment Required div.kc-elm > div.kc-col-container > header.kc-elm > h5.heading-text

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.container > div.header-content-wrapper > div.logo > a.full-block-link div.container > div.header-content-wrapper > div.logo > a.full-block-link
div.row > div.col-lg-7 > div.socials > a.social__item div.row > div.col-lg-7 > div.socials > a.social__item
div.row > div.col-lg-7 > div.socials > a.social__item div.row > div.col-lg-7 > div.socials > a.social__item
div.row > div.col-lg-7 > div.socials > a.social__item div.row > div.col-lg-7 > div.socials > a.social__item
div.row > div.col-lg-7 > div.socials > a.social__item div.row > div.col-lg-7 > div.socials > a.social__item
div.row > div.col-lg-7 > div.socials > a.social__item div.row > div.col-lg-7 > div.socials > a.social__item
div.row > div.col-lg-12 > svg.back-to-top > a.smooth-scroll div.row > div.col-lg-12 > svg.back-to-top > a.smooth-scroll

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.

○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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 use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<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.
○Identical links have the same purpose.
○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+
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer
A
Alt Text Quality
1 of 13 images have issues
PASS
1 of 13 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
10 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
13 images 2 good alt text 10 decorative 1 missing
IssueCount
missing1 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

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

Send Feedback