Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 4 REVIEW 6 FIX

Landmark Structure

Action

11 landmarks

FIX

11 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

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

Mobile-Readable Font Sizes

Action

32% of visible text renders at >= 12 CSS px (415 below threshold)

FIX

32% of visible text renders at >= 12 CSS px (415 below threshold)

415 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> 11.5px ("New"); <span> 10.0px ("app.squid.dev"); <span> 11.0px ("Squid workspace"); <small> 9.0px ("WORK"); <span> 11.0px ("Feed").

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://squid-next-five.vercel.app/site.webmanifest contains invalid JSON. Browsers cannot parse it.

Got: https://squid-next-five.vercel.app/site.webmanifest

Manifest contains invalid JSON.

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

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

Heading Hierarchy

29 headings, 2 skip(s)

REVIEW

29 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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 Plan, build and ship with a brain behind it.
H3 Sprint 1 skipped
H2 Your project is scattered across six tools.
H2 Squid brings it into one workspace.
H2 One place for the whole delivery.
H3 Product backlog
H3 Sprint 1
H3 Process map
H3 The pulse of the project
H2 Everything a delivery team needs. Nothing it doesn’t.
H3 Ready, computed
H3 A timer on every task
H3 Only what matters
H3 Evidence from CI
H3 Growth that’s earned
H3 The agent drafts. You decide.
H3 Ask Kraken
H3 The code, next to the work
H3 Meet without leaving
H2 Ask the one who has read everything.
H2 One story, from idea to production.
H3 Start from the architecture
H2 Task tracking is only the beginning.
H3 Task trackers
H3 suid
H2 Be first in line.
H4 Product skipped
H4 Features
H4 Get started

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

Mobile Keyboard & Autofill

Action

2/4 eligible field(s) missing autocomplete or inputmode

REVIEW

2/4 eligible field(s) missing autocomplete or inputmode

2 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" id="wl-email">, <input type="email" id="wl-email-2">

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Heading Text Quality

All 29 heading(s) have substantive, well-formed text

PASS

All 29 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

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
#wl-email	email	Email	for/id
#wl-email-2	email	Email	for/id
#wl-using	select	What do you use today?	for/id

A+

Link & Button Quality

25 links, 3 buttons — all OK

PASS

25 links, 3 buttons — all OK

25 link(s) with descriptive text

25 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

28 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+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <input>

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

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
h2 Your project is scat…	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h2 Squid brings it into	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h2 One place for the	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h2 Everything a deliver…	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h2 Ask the one who has	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h2 One story, from idea	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h2 Task tracking is onl…	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h2 Be first in	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Sprint 1	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Product backlog	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Sprint 1	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Process map	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 The pulse of the pro…	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Ready, computed	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 A timer on every tas…	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Only what matters	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Evidence from CI	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Growth that’s earn…	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 The agent drafts. Yo…	20.12:1	3.0:1	#000000	#FBFAF7	Pass
h3 Ask Kraken	20.12:1	3.0:1	#000000	#FBFAF7	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.

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 22 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
in Tracker `div.ld-tool > div.ld-tool-h > span.ld-tool-n > small.was`
in Docs `div.ld-tool > div.ld-tool-h > span.ld-tool-n > small.was`
in Diagrams `div.ld-tool > div.ld-tool-h > span.ld-tool-n > small.was`
in CI logs `div.ld-tool > div.ld-tool-h > span.ld-tool-n > small.was`
in Chat `div.ld-tool > div.ld-tool-h > span.ld-tool-n > small.was`
in Spreadsheet `div.ld-tool > div.ld-tool-h > span.ld-tool-n > small.was`
app.squid.dev `div.ld-frame > div.ld-window > div.ld-window-bar > span`
WORK `div.ld-fit-in > div.ld-app > aside.ld-app-side > small`
Feed `div.ld-fit-in > div.ld-app > aside.ld-app-side > span`
Dashboard `div.ld-fit-in > div.ld-app > aside.ld-app-side > span`
Plan `div.ld-fit-in > div.ld-app > aside.ld-app-side > span`
Sprints `div.ld-fit-in > div.ld-app > aside.ld-app-side > span`
PROJECT `div.ld-fit-in > div.ld-app > aside.ld-app-side > small`
Process `div.ld-fit-in > div.ld-app > aside.ld-app-side > span`
Reports `div.ld-fit-in > div.ld-app > aside.ld-app-side > span`
Team `div.ld-fit-in > div.ld-app > aside.ld-app-side > span`
PRODUCT BACKLOG `div.ld-app > div.ld-app-main > div.ld-app-top > span`
INITIATIVE · EPIC · FEATURE · STORY `div.ld-app-main > div.ld-app-content > div.ld-app-heading > span.ld-app-kicker`
Work shaped by readiness, architecture and delivery rules. `div.ld-app-main > div.ld-app-content > div.ld-app-heading > p`
Refinement `div.ld-app-main > div.ld-app-content > div.ld-app-tabs > span`
Backlog hygiene `div.ld-app-main > div.ld-app-content > div.ld-app-tabs > span`
WORK ITEM `div.ld-app-content > div.ld-app-table > div.ld-app-table-h > span`
TYPE `div.ld-app-content > div.ld-app-table > div.ld-app-table-h > span`
SCOPE `div.ld-app-content > div.ld-app-table > div.ld-app-table-h > span`
STATE `div.ld-app-content > div.ld-app-table > div.ld-app-table-h > span`
EP-01 `div.ld-app-table > div.ld-app-table-row > span > small`
Epic `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
8 stories `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
ST-31 `div.ld-app-table > div.ld-app-table-row > span > small`
Story `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
5 criteria `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
ST-42 `div.ld-app-table > div.ld-app-table-row > span > small`
Story `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
3 criteria `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
ST-38 `div.ld-app-table > div.ld-app-table-row > span > small`
Story `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
4 criteria `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
Refine `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span.ld-app-state`
EP-02 `div.ld-app-table > div.ld-app-table-row > span > small`
Epic `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
6 stories `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span`
Plan `div.ld-app-content > div.ld-app-table > div.ld-app-table-row > span.ld-app-state`
01 / 9 Gate `div.ld-pin > div.ld-stage > div.ld-stage-t > span.ld-stage-k`
Ready gate 118 / 118 rules `section.ld-strip > div.ld-marquee > div.ld-marquee-in > span.ld-chip`
Sprint 1 committed · 114 pts `section.ld-strip > div.ld-marquee > div.ld-marquee-in > span.ld-chip`
CI #482 passed `section.ld-strip > div.ld-marquee > div.ld-marquee-in > span.ld-chip`
Ready gate 118 / 118 rules `section.ld-strip > div.ld-marquee > div.ld-marquee-in > span.ld-chip`
Branch feat/invite-email `section.ld-strip > div.ld-marquee > div.ld-marquee-in > span.ld-chip`
Meeting Sprint review · live `section.ld-strip > div.ld-marquee > div.ld-marquee-in > span.ld-chip`
The brain for software delivery — backlog, architecture, sprints and evidence i… `footer.ld-foot > div.ld-foot-top > div.ld-foot-brand > p`
PRODUCT `div.ld-foot-top > nav.ld-foot-cols > div > h4`
FEATURES `div.ld-foot-top > nav.ld-foot-cols > div > h4`
GET STARTED `div.ld-foot-top > nav.ld-foot-cols > div > h4`
© 2026 Coderatory. All rights reserved. `div.ld > footer.ld-foot > div.ld-foot-bottom > span`
Squid is made by Coderatory `div.ld > footer.ld-foot > div.ld-foot-bottom > span`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sprint 1 `div.ld-app-content > div.ld-app-heading > div.ld-app-title > h3`
PRODUCT `div.ld-foot-top > nav.ld-foot-cols > div > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.sourceserif_8a4f041b-module__MP8VTa__variable `html.sourceserif_8a4f041b-module__MP8VTa__variable`

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

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

●Select elements have associated label elements.

●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

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

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

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

○Image elements have `[alt]` attributes

○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

○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

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