Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 1 REVIEW 6 FIX

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Vercel Security Checkpoint ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ 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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #0a0a0a

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 ModePartial Dark Mode

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 ✗

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

h2 WE DON'T JUST

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WE GRADE IT.

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 GRAND MOTEL OS

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

19px · mid-page

h3 SENTINELOPS

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

19px · mid-page

h3 BINGUS

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 PHISHING URL DETECTION

1.06:1

#000000

#0A0A0A

needs 3.0:1 (large text)

19px · bottom of viewport

title Qevon — Software Engineering Studio

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

span evon

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

a WORK

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

a SERVICES

1.07:1

#000000

#0D0B0A

needs 4.5:1 (normal text)

16px · above the fold

a ABOUT

1.09:1

#000000

#120D0A

needs 4.5:1 (normal text)

16px · above the fold

a CONTACT

1.12:1

#000000

#1B0F0B

needs 4.5:1 (normal text)

16px · above the fold

a START A PROJECT →

1.12:1

#000000

#1A0F0B

needs 4.5:1 (normal text)

16px · above the fold

span AVAILABLE FOR NEW PROJECTS

1.08:1

#000000

#120C0B

needs 4.5:1 (normal text)

16px · above the fold

p We design, engineer and deploy software …

1.06:1

#000000

#0C0A0A

needs 4.5:1 (normal text)

16px · above the fold

a START A PROJECT →

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

a VIEW OUR WORK →

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

span SCROLL TO EXPLORE

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · above the fold

span PROOF, NOT PROMISES

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 WE DON'T JUST	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h2 WE GRADE IT.	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h3 GRAND MOTEL OS	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h3 SENTINELOPS	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h3 BINGUS	1.06:1	3.0:1	#000000	#0A0A0A	Fail
h3 PHISHING URL DETECTI…	1.06:1	3.0:1	#000000	#0A0A0A	Fail
title Qevon — Software E…	1.06:1	4.5:1	#000000	#0A0A0A	Fail
a Skip to content	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span evon	1.06:1	4.5:1	#000000	#0A0A0A	Fail
a WORK	1.06:1	4.5:1	#000000	#0A0A0A	Fail
a SERVICES	1.07:1	4.5:1	#000000	#0D0B0A	Fail
a ABOUT	1.09:1	4.5:1	#000000	#120D0A	Fail
a CONTACT	1.12:1	4.5:1	#000000	#1B0F0B	Fail
a START A PROJECT →	1.12:1	4.5:1	#000000	#1A0F0B	Fail
span AVAILABLE FOR NEW PR…	1.08:1	4.5:1	#000000	#120C0B	Fail
p We design, engineer …	1.06:1	4.5:1	#000000	#0C0A0A	Fail
a START A PROJECT →	1.06:1	4.5:1	#000000	#0A0A0A	Fail
a VIEW OUR WORK →	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span SCROLL TO EXPLORE	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span PROOF, NOT PROMISES	1.06:1	4.5:1	#000000	#0A0A0A	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Skip link target(s) don't exist on page: #root

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

9 headings

PASS

9 headings

Single H1 present

H1 WE BUILD DIGITALPRODUCTS THATMEAN BUSINESS.
H2 WHAT WE'VESHIPPED.
H3 GRAND MOTEL OS
H3 SENTINELOPS
H3 BINGUS
H3 PHISHING URL DETECTION
H2 FROM IDEATO PRODUCTION.
H2 WE DON'T JUSTSHIP SOFTWARE.WE GRADE IT.
H2 GOT SOMETHINGWORTH BUILDING?

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

4 image(s) with good alt text

4 images 4 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

32 links, 3 buttons — all OK

PASS

32 links, 3 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://github.com/Qevon-Digital; https://www.instagram.com/qevondigital/; https://www.linkedin.com/company/qoven

29 link(s) with descriptive text

32 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://github.com/Qevon-Digital	GitHub	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/qevondigital/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/qoven	LinkedIn	new tab	Add '(opens in new tab)' to text

32 links and buttons have descriptive text

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

https://github.com/Qevon-Digital; https://www.instagram.com/qevondigital/; https://www.linkedin.com/company/qoven

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

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

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

No form controls on this page

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 71 visible text node(s) render at >= 12 CSS pixels

PASS

All 71 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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 20 passed

PASS

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
PROJECT DETAILS → `section.max-w-[1440px] > div > div.flex > a.text-sm`
01 `div.p-6 > div.flex > div > span.text-xs`
Software / Web / Operations `a.block > div.relative > div.p-6 > p.text-xs`
Point of sale, inventory and customers in one system — stock moves as orders do… `a.block > div.relative > div.p-6 > p.text-sm`
02 `div.p-6 > div.flex > div > span.text-xs`
Security / DevOps / Tooling `a.block > div.relative > div.p-6 > p.text-xs`
Point it at a repo. It runs 29 checks across 6 categories and scores production… `a.block > div.relative > div.p-6 > p.text-sm`
03 `div.p-6 > div.flex > div > span.text-xs`
Social / Mobile / Web `a.block > div.relative > div.p-6 > p.text-xs`
A location-based social platform — posts and connections anchored to real place… `a.block > div.relative > div.p-6 > p.text-sm`
04 `div.p-6 > div.flex > div > span.text-xs`
AI / ML / Security `a.block > div.relative > div.p-6 > p.text-xs`
A hybrid LSTM + CNN model that classifies URLs as phishing or legitimate from 9… `a.block > div.relative > div.p-6 > p.text-sm`
01 `div > a.flex > div.flex > span.text-xs`
Full-stack, systems, APIs `a.flex > div.flex > div > div.text-xs`
02 `div > a.flex > div.flex > span.text-xs`
Design, frontend, UX `a.flex > div.flex > div > div.text-xs`
03 `div > a.flex > div.flex > span.text-xs`
AWS, GCP, Kubernetes, CI/CD `a.flex > div.flex > div > div.text-xs`
04 `div > a.flex > div.flex > span.text-xs`
LLMs, pipelines, RAG `a.flex > div.flex > div > div.text-xs`
05 `div > a.flex > div.flex > span.text-xs`
DevSecOps, pen-testing, compliance `a.flex > div.flex > div > div.text-xs`
06 `div > a.flex > div.flex > span.text-xs`
Dashboards, BI, product analytics `a.flex > div.flex > div > div.text-xs`
07 `div > a.flex > div.flex > span.text-xs`
Migrations, rewrites, replatforming `a.flex > div.flex > div > div.text-xs`
EXPLORE ALL SERVICES → `div.max-w-[1440px] > div > div.mt-12 > a.inline-flex`
SentinelOps is our own production-readiness scanner. It runs 29 checks across s… `section.max-w-[1440px] > div > div.max-w-4xl > p.text-base`
SEE SENTINELOPS → `section.max-w-[1440px] > div > div.max-w-4xl > a.inline-flex`
LET'S BUILD `div.flex-shrink-0 > div > a.group > span`

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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●All heading elements contain content.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[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

○`[role]` values are valid

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

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

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

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