Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 REVIEW 6 FIX

Link & Button Quality

Action

15 issue(s) across 42 links and 1 buttons

FIX

15 issue(s) across 42 links and 1 buttons

14 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /Contributors/Matthew-Layton; https://github.com/MrMatthewLayton; https://www.linkedin.com/in/mrmatthewlayton/; /Contributors/Laura-Perez-Crespo; https://github.com/pclaura; https://www.linkedin.com/in/laura-p%C3%A9rez-crespo-96447a15b/; /Contributors/Adam-Dry; https://github.com/adamdry; https://www.linkedin.com/in/adam-dry/; /Contributors/Ryan-Gledhill (+4 more)

18 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://angular.dev/; https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor; https://getbootstrap.com/; https://r3.com/get-corda/; https://www.docker.com/; https://dotnet.microsoft.com/en-us/; https://ethereum.org/; https://www.java.com/en/; https://kafka.apache.org/; https://kotlinlang.org/ (+8 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.navbar-toggler (#35 on page)

10 link(s) with descriptive text

42 links

14 empty

0 generic text

18 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://angular.dev/	Angular	new tab	Add '(opens in new tab)' to text
https://dotnet.microsoft.com/en-us/apps/…	Blazor	new tab	Add '(opens in new tab)' to text
https://getbootstrap.com/	Bootstrap	new tab	Add '(opens in new tab)' to text
https://r3.com/get-corda/	Corda	new tab	Add '(opens in new tab)' to text
https://www.docker.com/	Docker	new tab	Add '(opens in new tab)' to text
https://dotnet.microsoft.com/en-us/	.NET	new tab	Add '(opens in new tab)' to text
https://ethereum.org/	Ethereum	new tab	Add '(opens in new tab)' to text
https://www.java.com/en/	Java	new tab	Add '(opens in new tab)' to text
https://kafka.apache.org/	Kafka	new tab	Add '(opens in new tab)' to text
https://kotlinlang.org/	Kotlin	new tab	Add '(opens in new tab)' to text
https://kubernetes.io/	Kubernetes	new tab	Add '(opens in new tab)' to text
https://mui.com/material-ui/	Material UI	new tab	Add '(opens in new tab)' to text
https://neo4j.com/	Neo4j	new tab	Add '(opens in new tab)' to text
https://www.rabbitmq.com/	RabbitMQ	new tab	Add '(opens in new tab)' to text
https://spring.io/	Spring	new tab	Add '(opens in new tab)' to text
https://tailwindcss.com/	Tailwind	new tab	Add '(opens in new tab)' to text
https://www.typescriptlang.org/	TypeScript	new tab	Add '(opens in new tab)' to text
https://webassembly.org/	Web Assembly	new tab	Add '(opens in new tab)' to text
/Contributors/Matthew-Layton	(empty)	empty	Add link text or aria-label
https://github.com/MrMatthewLayton	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/in/mrmatthewlay…	(empty)	empty	Add link text or aria-label
/Contributors/Laura-Perez-Crespo	(empty)	empty	Add link text or aria-label
https://github.com/pclaura	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/in/laura-p%C3%A…	(empty)	empty	Add link text or aria-label
/Contributors/Adam-Dry	(empty)	empty	Add link text or aria-label
https://github.com/adamdry	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/in/adam-dry/	(empty)	empty	Add link text or aria-label
/Contributors/Ryan-Gledhill	(empty)	empty	Add link text or aria-label
https://github.com/RyanGled	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/in/ryan-gledhil…	(empty)	empty	Add link text or aria-label
https://x.com/onix_labs	(empty)	empty	Add link text or aria-label
https://github.com/onix-labs	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

10 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/Contributors/Matthew-Layton; https://github.com/MrMatthewLayton; https://www.linkedin.com/in/mrmatthewlayton/; /Contributors/Laura-Perez-Crespo; https://github.com/pclaura; https://www.linkedin.com/in/laura-p%C3%A9rez-crespo-96447a15b/; /Contributors/Adam-Dry; https://github.com/adamdry; https://www.linkedin.com/in/adam-dry/; /Contributors/Ryan-Gledhill (+4 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://angular.dev/; https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor; https://getbootstrap.com/; https://r3.com/get-corda/; https://www.docker.com/; https://dotnet.microsoft.com/en-us/; https://ethereum.org/; https://www.java.com/en/; https://kafka.apache.org/; https://kotlinlang.org/ (+8 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.navbar-toggler (#35 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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'>.

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title ONIXLabs ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Lighthouse Accessibility Audits

Score 84/100 — 3 failing, 18 passed

REVIEW

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

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
header > nav#navbar > div.container > button.navbar-toggler `header > nav#navbar > div.container > button.navbar-toggler`

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.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
div.d-flex > div.d-flex > div.btn-group > a.btn `div.d-flex > div.d-flex > div.btn-group > a.btn`
footer.text-white-50 > div.d-flex > div.ms-auto > a.btn `footer.text-white-50 > div.d-flex > div.ms-auto > a.btn`
footer.text-white-50 > div.d-flex > div.ms-auto > a.btn `footer.text-white-50 > div.d-flex > div.ms-auto > a.btn`

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
Founder & Architect `div.d-flex > div.d-flex > div.d-flex > span.h6`
Software Engineer `div.d-flex > div.d-flex > div.d-flex > span.h6`
Integration Specialist `div.d-flex > div.d-flex > div.d-flex > span.h6`
Strategic Advisor `div.d-flex > div.d-flex > div.d-flex > span.h6`

These are opportunities to improve the legibility of your content.

○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

●`[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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

○`[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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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

○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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

Heading Hierarchy

34 headings

PASS

34 headings

Multiple H1 headings (30 found)

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

H1 Introducing AERO
H2 Blazing Fast • Infinitely Scalable • Built For Enterprise
H1 Powering Possibility duplicate H1
H2 Code That Connects • Software That Scales
H1 Craftsmanship duplicate H1
H1 Integrity duplicate H1
H1 Performance duplicate H1
H1 Enterprise duplicate H1
H1 Community duplicate H1
H1 Simplicity duplicate H1
H1 Education duplicate H1
H1 Support duplicate H1
H1 Tools That Fit, Built To Last duplicate H1
H2 Pioneering Engineering • Purpose Over Preference
H1 Angular duplicate H1
H1 Blazor duplicate H1
H1 Bootstrap duplicate H1
H1 Corda duplicate H1
H1 Docker duplicate H1
H1 .NET duplicate H1
H1 Ethereum duplicate H1
H1 Java duplicate H1
H1 Kafka duplicate H1
H1 Kotlin duplicate H1
H1 Kubernetes duplicate H1
H1 Material UI duplicate H1
H1 Neo4j duplicate H1
H1 RabbitMQ duplicate H1
H1 Spring duplicate H1
H1 Tailwind duplicate H1
H1 TypeScript duplicate H1
H1 Web Assembly duplicate H1
H1 Champions of Contribution duplicate H1
H2 Bright Minds • Open Source • Built Together

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: 1 all-caps heading(s)

A+

Alt Text Quality

All 42 images OK

PASS

All 42 images OK

42 image(s) with good alt text

42 images 42 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#themeToggle	checkbox	Toggle Dark/Light Mode	none

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 64 visible text node(s) render at >= 12 CSS pixels

PASS

All 64 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Introducing AERO	15.41:1	3.0:1	#000000	#CFE1D8	Pass
h1 Powering Possibility	12.97:1	3.0:1	#000000	#AFD4BC	Pass
h1 Craftsmanship	11.91:1	3.0:1	#000000	#9FCEAD	Pass
h1 Integrity	11.15:1	3.0:1	#000000	#94C9A4	Pass
h1 Performance	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Enterprise	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Community	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Simplicity	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Education	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Support	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Tools That Fit, Buil…	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Angular	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Blazor	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Bootstrap	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Corda	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Docker	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 .NET	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Ethereum	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Java	10.82:1	3.0:1	#000000	#8EC79F	Pass
h1 Kafka	10.82:1	3.0:1	#000000	#8EC79F	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.

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