Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 5 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, custom page

FIX

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 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

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

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

Heading Hierarchy

11 headings, 2 skip(s)

REVIEW

11 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Digitize and grow your business
H2 Embrace the challenges and the opportunities of the future. We'll make it simple for you.
H2 NORRIQ aims to revolutionize financial consulting
H2 We are NORRIQ
H4 Industry knowledge. Business understanding. Technology insight. skipped
H2 News from NORRIQ
H2 Want to know more?
H4 Please contact us skipped
H4 Why complicate things?
H4 Get in touch
H4 Legal

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

8 issue(s) across 22 links and 10 buttons

REVIEW

8 issue(s) across 22 links and 10 buttons

8 link(s) with no accessible text

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

Got: https://norriq.com/nfs; /competences/enterprise-resource-planning; /competences/product-information-management; /competences/ecommerce-web-development; /competences/customer-engagement-industry-services; /competences/bi-analytics; /competences/ai-automation; /competences/apps-accelerators

14 link(s) with descriptive text

22 links

8 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://norriq.com/nfs	(empty)	empty	Add link text or aria-label
/competences/enterprise-resource-plannin…	(empty)	empty	Add link text or aria-label
/competences/product-information-managem…	(empty)	empty	Add link text or aria-label
/competences/ecommerce-web-development	(empty)	empty	Add link text or aria-label
/competences/customer-engagement-industr…	(empty)	empty	Add link text or aria-label
/competences/bi-analytics	(empty)	empty	Add link text or aria-label
/competences/ai-automation	(empty)	empty	Add link text or aria-label
/competences/apps-accelerators	(empty)	empty	Add link text or aria-label

24 links and buttons have descriptive text

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

https://norriq.com/nfs; /competences/enterprise-resource-planning; /competences/product-information-management; /competences/ecommerce-web-development; /competences/customer-engagement-industry-services; /competences/bi-analytics; /competences/ai-automation; /competences/apps-accelerators

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

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 Digitize and grow your business

1.28:1

#000000

#1C2022

needs 3.0:1 (large text)

32px · above the fold

h2 Embrace the challenges and the opportuni…

1.57:1

#000000

#312F2B

needs 3.0:1 (large text)

24px · above the fold

h2 NORRIQ aims to revolutionize financial c…

1.31:1

#000000

#25211E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We are NORRIQ

1.31:1

#000000

#25211E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 News from NORRIQ

1.31:1

#000000

#25211E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Want to know more?

1.31:1

#000000

#25211E

needs 3.0:1 (large text)

24px · bottom of viewport

title We are the NORRIQ Group | Welcome

1.11:1

#000000

#0C1116

needs 4.5:1 (normal text)

16px · top of page (header area)

span NORRIQ Global

1.24:1

#000000

#1A1D22

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Competences

1.11:1

#000000

#0C1116

needs 4.5:1 (normal text)

16px · top of page (header area)

a Customers

1.11:1

#000000

#0C1116

needs 4.5:1 (normal text)

16px · top of page (header area)

a News

1.11:1

#000000

#0C1116

needs 4.5:1 (normal text)

16px · above the fold

a About NORRIQ

1.11:1

#000000

#0C1116

needs 4.5:1 (normal text)

16px · above the fold

a Career

1.01:1

#000000

#010102

needs 4.5:1 (normal text)

16px · above the fold

span Contact

2.10:1

#000000

#404343

needs 4.5:1 (normal text)

16px · above the fold

video Your browser does not support the video …

2.10:1

#000000

#404343

needs 4.5:1 (normal text)

16px · above the fold

p Why complicate things?

2.10:1

#000000

#404342

needs 4.5:1 (normal text)

16px · above the fold

span Read more about NORRIQ

1.49:1

#000000

#2D2B28

needs 4.5:1 (normal text)

16px · mid-page

p Financial Services

1.58:1

#000000

#322F2B

needs 4.5:1 (normal text)

16px · mid-page

p NORRIQ Financial Services: Transforming …

1.56:1

#000000

#322E2A

needs 4.5:1 (normal text)

16px · mid-page

button Learn more (opens in a new window)

1.55:1

#000000

#312E29

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Digitize and grow yo…	1.28:1	3.0:1	#000000	#1C2022	Fail
h2 Embrace the challeng…	1.57:1	3.0:1	#000000	#312F2B	Fail
h2 NORRIQ aims to revol…	1.31:1	3.0:1	#000000	#25211E	Fail
h2 We are NORRIQ	1.31:1	3.0:1	#000000	#25211E	Fail
h2 News from NORRIQ	1.31:1	3.0:1	#000000	#25211E	Fail
h2 Want to know more?	1.31:1	3.0:1	#000000	#25211E	Fail
title We are the NORRIQ Gr…	1.11:1	4.5:1	#000000	#0C1116	Fail
span NORRIQ Global	1.24:1	4.5:1	#000000	#1A1D22	Fail
a Competences	1.11:1	4.5:1	#000000	#0C1116	Fail
a Customers	1.11:1	4.5:1	#000000	#0C1116	Fail
a News	1.11:1	4.5:1	#000000	#0C1116	Fail
a About NORRIQ	1.11:1	4.5:1	#000000	#0C1116	Fail
a Career	1.01:1	4.5:1	#000000	#010102	Fail
span Contact	2.10:1	4.5:1	#000000	#404343	Fail
video Your browser does no…	2.10:1	4.5:1	#000000	#404343	Fail
p Why complicate thing…	2.10:1	4.5:1	#000000	#404342	Fail
span Read more about NORR…	1.49:1	4.5:1	#000000	#2D2B28	Fail
p Financial Services	1.58:1	4.5:1	#000000	#322F2B	Fail
p NORRIQ Financial Ser…	1.56:1	4.5:1	#000000	#322E2A	Fail
button Learn more (opens in…	1.55:1	4.5:1	#000000	#312E29	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.

Lighthouse Accessibility Audits

Score 84/100 — 5 failing, 26 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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters