Skip to content
https://opengroup.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-qt4hsd
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://opengroup.org/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://opengroup.org/manifest.json

Manifest contains invalid JSON.

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
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 4 <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
Heading Hierarchy
15 headings
REVIEW
15 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 User menu - for logged out user
  • H2 The TOGAF® Standard, a standard of The Open Group
  • H2 The Portfolio of Digital Open Standards
  • H2 The Open Group Library
  • H2 The Architect's Toolkit
  • H2 Certifications
  • H2 About Us
  • H2 (empty)
  • H2 Discover
  • H2 News
  • H2 Blog
  • H2 On-Demand
  • H3 The Open Group: Leading the development of open, vendor-neutral technology standards and certifications
  • H3 Boundaryless Information Flow™ achieved through global interoperability in a secure, reliable, and timely manner
  • H2 footer_menu

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h3 Boundaryless Information Flow™ achieve…
1.03:1
#F8F8F8
on
#F2F5F7
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 User menu - for logg…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The TOGAF® Standard…19.18:13.0:1
#000000
#F2F5F7
Pass
h2 The Portfolio of Dig…19.18:13.0:1
#000000
#F2F5F7
Pass
h2 The Open Group Libra…19.18:13.0:1
#000000
#F2F5F7
Pass
h2 The Architect's Tool…19.18:13.0:1
#000000
#F2F5F7
Pass
h2 Certifications19.18:13.0:1
#000000
#F2F5F7
Pass
h2 About Us19.18:13.0:1
#000000
#F2F5F7
Pass
h2 Discover19.18:13.0:1
#000000
#F2F5F7
Pass
h2 footer_menu19.18:13.0:1
#000000
#F2F5F7
Pass
h3 Boundaryless Informa…1.03:13.0:1
#F8F8F8
#F2F5F7
Fail
title www.opengroup.org21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
a Log In21.00:14.5:1
#000000
#FFFFFF
Pass
a Create Account21.00:14.5:1
#000000
#FFFFFF
Pass
span www.opengroup.org21.00:14.5:1
#000000
#FFFFFF
Pass
a About Us21.00:14.5:1
#000000
#FFFFFF
Pass
a Who We Are21.00:14.5:1
#000000
#FFFFFF
Pass
a Executive Team21.00:14.5:1
#000000
#FFFFFF
Pass
a Governing Board21.00:14.5:1
#000000
#FFFFFF
Pass
a Elected Member Repre…21.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.

A
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN ASIDE 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+
Alt Text Quality
All 18 images OK
PASS
All 18 images OK
Info::
3 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
18 images 15 good alt text 3 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#edit-keys--2searchSearchfor/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_Ae7_Ghy6rqxRIxuhY2u473reTvhEsBGca6aarFPR77Y.css?delta=4&language=en&theme=opengroupcss&include=eJxlkOFuwyAMhF-IhEdCBlzKBjayTbO8_dJtbdXsj3W67-STLjKbmsAIEUQq-9I4QlvU9lapuHjmHVWhoIbtWg3_c-KMLn1irsYSICWWXJn8U60XYTKk7A4DfeI-mJBM1_OvZelI8zeWZQ5oK3zA15uRKzQursHO00KctWUUbxsnbkEx2dH4oLlq4hvK7o_CgzseSEV4jqTqX-0p0zs6baJzoFyqXv1ThTvDv010V8PuIyi6W8VN_c9dO-fZ8BuXlJMq
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/default/files/css/css_Ae7_Ghy6rqxRIxuhY2u473reTvhEsBGca6aarFPR77Y.css?delta=4&language=en&theme=opengroupcss&include=eJxlkOFuwyAMhF-IhEdCBlzKBjayTbO8_dJtbdXsj3W67-STLjKbmsAIEUQq-9I4QlvU9lapuHjmHVWhoIbtWg3_c-KMLn1irsYSICWWXJn8U60XYTKk7A4DfeI-mJBM1_OvZelI8zeWZQ5oK3zA15uRKzQursHO00KctWUUbxsnbkEx2dH4oLlq4hvK7o_CgzseSEV4jqTqX-0p0zs6baJzoFyqXv1ThTvDv010V8PuIyi6W8VN_c9dO-fZ8BuXlJMq ✓Inline @media print Not detected ✗
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 26 passed
PASS
93

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

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#block-opengroupcss-testsuperfishmenu3 > div.content > div.sf-accordion-toggle > a#superfish-test-superfish-menu-3-toggle div#block-opengroupcss-testsuperfishmenu3 > div.content > div.sf-accordion-toggle > a#superfish-test-superfish-menu-3-toggle

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
Contact nav#block-footer-menu > ul.clearfix > li.nav-item > a.nav-link
Standards Process nav#block-footer-menu > ul.clearfix > li.nav-item > a.nav-link
Sitemap nav#block-footer-menu > ul.clearfix > li.nav-item > a.nav-link
System Status nav#block-footer-menu > ul.clearfix > li.nav-item > a.nav-link

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
●Buttons have an accessible name
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
●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-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
○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
○Links are distinguishable without relying on color.
○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
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback