Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 2 REVIEW 7 FIX

Mobile-Readable Font Sizes

Action

49% of visible text renders at >= 12 CSS px (66 below threshold)

FIX

49% of visible text renders at >= 12 CSS px (66 below threshold)

66 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 9.0px ("Index"); <span> 9.0px ("Origo pg / 2026"); <a> 10.0px ("Start a project"); <div> 10.0px ("Origin / 001"); <a> 10.0px ("Explore our work").

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://origopg-mwnz8lgk.manus.space/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://origopg-mwnz8lgk.manus.space/manifest.json

Manifest contains invalid JSON.

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: #171716

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Heading Text Quality

1 heading-text-quality issue(s) detected

REVIEW

1 heading-text-quality issue(s) detected

1 heading(s) contain placeholder / generic text

Some headings contain placeholder or generic text patterns that often leak through from CMS templates / WYSIWYG defaults / unfinished drafts. Affected (first 1): - H3: "Test" Replace with descriptive text that summarizes the section's content. Search engines use heading text to understand page structure; placeholder text contributes nothing to relevance signals.

Got: 1 placeholder heading(s)

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 Everything

1.57:1

#000000

#302F2D

needs 3.0:1 (large text)

32px · mid-page

h2 Ideas become useful

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The first system

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Every big thing

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A clear line from

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Independence

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Have something

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Let's build

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Discover

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Define

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Build

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Test

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Review

1.53:1

#000000

#2E2D2B

needs 3.0:1 (large text)

19px · bottom of viewport

title Origo pg — Everything has an origin.

1.36:1

#000000

#252423

needs 4.5:1 (normal text)

16px · top of page (header area)

a Our story

1.32:1

#000000

#232221

needs 4.5:1 (normal text)

16px · top of page (header area)

a What we build

1.30:1

#000000

#212120

needs 4.5:1 (normal text)

16px · top of page (header area)

a Projects

1.30:1

#000000

#212120

needs 4.5:1 (normal text)

16px · top of page (header area)

a How we work

1.37:1

#000000

#262524

needs 4.5:1 (normal text)

16px · above the fold

a Start a project

1.44:1

#000000

#2A2926

needs 4.5:1 (normal text)

16px · above the fold

span Index

1.20:1

#000000

#1A1A18

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Everything	1.57:1	3.0:1	#000000	#302F2D	Fail
h2 Ideas become useful	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h2 The first system	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h2 Every big thing	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h2 A clear line from	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h2 The Independence	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h2 Have something	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h2 Let's build	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h3 Discover	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h3 Define	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h3 Build	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h3 Test	1.53:1	3.0:1	#000000	#2E2D2B	Fail
h3 Review	1.53:1	3.0:1	#000000	#2E2D2B	Fail
title Origo pg — Everyth…	1.36:1	4.5:1	#000000	#252423	Fail
a Our story	1.32:1	4.5:1	#000000	#232221	Fail
a What we build	1.30:1	4.5:1	#000000	#212120	Fail
a Projects	1.30:1	4.5:1	#000000	#212120	Fail
a How we work	1.37:1	4.5:1	#000000	#262524	Fail
a Start a project	1.44:1	4.5:1	#000000	#2A2926	Fail
span Index	1.20:1	4.5:1	#000000	#1A1A18	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

5 landmarks

PASS

5 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

A+

Heading Hierarchy

13 headings

PASS

13 headings

Single H1 present

H1 Everythinghas an origin.
H2 Ideas become usefulwhen they have a place to go.
H2 The first systemis taking shape.
H2 Every big thinghas a beginning.
H2 A clear line fromquestion to delivery.
H3 Discover
H3 Define
H3 Build
H3 Test
H3 Review
H2 The IndependenceChallenge.
H2 Have somethingworth building?
H2 Let's buildfrom here.

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

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
inline-name	input	Your name	none
inline-email	email	Email	none
inline-message	textarea	What are you trying to build?	none

A+

Link & Button Quality

34 links, 2 buttons — all OK

PASS

34 links, 2 buttons — all OK

34 link(s) with descriptive text

34 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

36 links and buttons have descriptive text

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

3 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

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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+

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.

Lighthouse Accessibility Audits

Score 90/100 — 2 failing, 21 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
START A PROJECT `div.hero-copy > div.reveal > div.hero-actions > a.action-link`
01 / 26 `div.container > div.reveal > div.hero-visual > div.visual-index`
EXPLORE `footer.site-footer > div.footer-top > div.footer-nav-wrap > p.eyebrow`
START HERE `footer.site-footer > div.footer-top > div.footer-nav-wrap > p.eyebrow`
© 2026 ORIGO PG `div.site-shell > footer.site-footer > div.footer-bottom > span`
BUILT FROM WHERE IT BEGINS. `div.site-shell > footer.site-footer > div.footer-bottom > span`
PRIVACY POLICY — DRAFT `footer.site-footer > div.footer-bottom > div.footer-legal > a`
TERMS — DRAFT `footer.site-footer > div.footer-bottom > div.footer-legal > a`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●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

●No element has a `[tabindex]` value greater than 0

●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

○`[accesskey]` values are unique

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

○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

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

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

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

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

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