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 3 REVIEW 5 FIX

Mobile-Readable Font Sizes

Action

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

FIX

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

42 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: <a> 11.0px ("Capabilities"); <a> 11.0px ("Services"); <a> 11.0px ("Studio"); <a> 11.0px ("Contact"); <a> 11.0px ("Start a project").

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

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

Link & Button Quality

4 issue(s) across 28 links and 11 buttons

REVIEW

4 issue(s) across 28 links and 11 buttons

2 link(s) open in new tab without warning

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

Got: https://cookiedatabase.org/tcf/purposes/; https://pixelit.ro

4 button(s) with no accessible text

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

Got: button.cmplz-category-toggle (#72 on page); button.cmplz-category-toggle (#85 on page); button.cmplz-category-toggle (#98 on page); button.cmplz-category-toggle (#112 on page)

26 link(s) with descriptive text

28 links

0 empty

0 generic text

2 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://cookiedatabase.org/tcf/purposes/	Read more about TCF purposes o…	new tab	Add '(opens in new tab)' to text
https://pixelit.ro	pixelit.ro ↗	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

33 links and buttons have descriptive text

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

https://cookiedatabase.org/tcf/purposes/; https://pixelit.ro

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.cmplz-category-toggle (#72 on page); button.cmplz-category-toggle (#85 on page); button.cmplz-category-toggle (#98 on page); button.cmplz-category-toggle (#112 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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Pixelit ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Landmark Structure

14 landmarks

PASS

14 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

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

23 headings

PASS

23 headings

Single H1 present

H1 Websites, platforms and digital products. Built to work.
H2 What we build...and make work
H3 Content Platforms
H3 Digital Products
H3 Integrations & Portals
H3 Commerce & Services
H2 The right expertisefor the right project
H3 Technical planning
H3 UX & UI design
H3 Web development
H3 APIs & integrations
H3 Migration & modernisation
H3 Maintenance & support
H2 Small team with big ideas.
H2 Five movesforward.
H3 Discover
H3 Plan
H3 Design
H3 Develop
H3 Launch
H2 Tools withpurpose.
H2 Have a project in mind?
H2 Tell us aboutyour project.

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 9 controls have issues

PASS

1 of 9 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit">

8 control(s) properly labeled

9 controls

8 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#cmplz-functional-optin	checkbox	Functional	for/id
#cmplz-preferences-optin	checkbox	Preferences	for/id
#cmplz-statistics-optin	checkbox	Statistics	for/id
#cmplz-marketing-optin	checkbox	Marketing	for/id
your-name	text	Your name *	none
your-email	email	Email address *	none
your-organisation	text	Organisation	none
your-message	textarea	Tell us about your project *	none
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+

Form Input Types

9 form control(s) checked, no type mismatches

PASS

9 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

9 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-US"

PASS

Lang attribute set to "en-US"

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

Got: en-US

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

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 Websites, platforms …	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h2 What we build	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h2 The right expertise	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h2 Small team	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h2 with big	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h2 Five moves	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h2 Tools with	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h2 Have a project	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h2 Tell us about	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 Content Platforms	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 Digital Products	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 Integrations & Porta…	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 Commerce & Services	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 Technical planning	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 UX & UI design	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 Web development	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 APIs & integrations	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 Migration & modernis…	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 Maintenance & suppor…	13.05:1	3.0:1	#000000	#CDCCC6	Pass
h3 Discover	13.05:1	3.0:1	#000000	#CDCCC6	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 92/100 — 2 failing, 25 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
ideas. `div.site-container > div.studio-grid > h2#studio-title > em`
01 `div.studio-grid > div.studio-copy > div.studio-quip > span`

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

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

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[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 are distinguishable without relying on color.

●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

●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

○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

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