Skip to content
https://threatmodeler.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
83
GRADE
B
FIX
4
REVIEW
4
PASS
16
INFO
0
Checks
24
16 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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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.
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 | ThreatModeler ✓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, 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 THAT’S AGENTIC
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
32px · bottom of viewport
h2 How it works
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Powered by
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h2 true innovation
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The ThreatModeler Intelligence Platform
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We make threat modeling a team sport
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h2 With the ThreatModeler platform, you get…
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Proven solutions.
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Proven results.
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted Partners
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Let’s talk
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Generate enterprise-ready models in minu…
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Identify and prioritize risks in seconds
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Accelerate mitigation with guided insigh…
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Prioritize
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
19px · bottom of viewport
h3 RESPOND
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
19px · bottom of viewport
h3 SEE
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ThreatModeler
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
19px · bottom of viewport
h3 IaC-Assist
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CloudModeler
1.51:1
#000000
on
#102865
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 THAT’S AGENTIC1.51:13.0:1
#000000
#102865
Fail
h2 How it works1.51:13.0:1
#000000
#102865
Fail
h2 Powered by1.51:13.0:1
#000000
#102865
Fail
h2 true innovation1.51:13.0:1
#000000
#102865
Fail
h2 The ThreatModeler In…1.51:13.0:1
#000000
#102865
Fail
h2 We make threat model…1.51:13.0:1
#000000
#102865
Fail
h2 With the ThreatModel…1.51:13.0:1
#000000
#102865
Fail
h2 Proven solutions.1.51:13.0:1
#000000
#102865
Fail
h2 Proven results.1.51:13.0:1
#000000
#102865
Fail
h2 Trusted Partners1.51:13.0:1
#000000
#102865
Fail
h2 Let’s talk1.51:13.0:1
#000000
#102865
Fail
h3 Generate enterprise-…1.51:13.0:1
#000000
#102865
Fail
h3 Identify and priorit…1.51:13.0:1
#000000
#102865
Fail
h3 Accelerate mitigatio…1.51:13.0:1
#000000
#102865
Fail
h3 Prioritize1.51:13.0:1
#000000
#102865
Fail
h3 RESPOND1.51:13.0:1
#000000
#102865
Fail
h3 SEE1.51:13.0:1
#000000
#102865
Fail
h3 ThreatModeler1.51:13.0:1
#000000
#102865
Fail
h3 IaC-Assist1.51:13.0:1
#000000
#102865
Fail
h3 CloudModeler1.51:13.0:1
#000000
#102865
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.

A+
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Promo banner" MAIN CONTENTINFO footer
A+
Heading Hierarchy
31 headings
PASS
31 headings
Info::
Single H1 present
  • H4 Industry Solutions
  • H4 Solutions by Role
  • H4 Industry Solutions
  • H4 Solutions by Role
  • H1 THAT’S AGENTIC
  • H2 One Platform. Complete Coverage.
  • H2 Confidence at enterprise scale
  • H3 Generate enterprise-ready models in minutes
  • H3 Identify and prioritize risks in seconds
  • H3 Accelerate mitigation with guided insights
  • H2 How it works
  • H3 Prioritize
  • H3 RESPOND
  • H3 SEE
  • H2 Powered by true innovation
  • H3 Intelligent Automation
  • H3 Continuous Awareness
  • H3 Guided Insights
  • H3 360° Visibility
  • H2 A secure-by-design platform built for scale
  • H3 ThreatModeler
  • H3 IaC-Assist
  • H3 CloudModeler
  • H2 The ThreatModeler Intelligence Platform
  • H2 We make threat modeling a team sport
  • H2 With the ThreatModeler platform, you get:
  • H2 Proven solutions.Proven results.
  • H2 Trusted Partners
  • H2 Let’s talk
  • H3 ABOUT THREATMODELER
  • H3 GET IN TOUCH
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
4 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 4 all-caps heading(s)
A+
Alt Text Quality
All 92 images OK
PASS
All 92 images OK
Info::
44 decorative image(s) correctly marked
Info::
48 image(s) with good alt text
92 images 48 good alt text 44 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/3 iframe(s) missing title; 0 placeholder(s)
PASS
1/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://fast.wistia.net/embed/iframe/wfhttkppwk?seo=false&videoFoam=true")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 23 visible text node(s) render at >= 12 CSS pixels
PASS
All 23 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 29 passed
PASS
100

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.

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
REQUEST A DEMO div.lg:pe-9 > div.flex > div.mb-2 > a.button-40q
EXPLORE THE PLATFORM div.flex > div.flex > div.mb-2 > a.button-40q
TAKE A TOUR div.text-black > div.flex > div.static > a.button-40q
READ CASE STUDY div.flex > div.flex > div.flex > a.button-40q
REQUEST A DEMO div.flex > div.flex > div.mb-2 > a.button-40q
○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
●Buttons have an accessible name
●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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback