Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

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

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.

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.

Link & Button Quality

Action

8 issue(s) across 82 links and 15 buttons

REVIEW

8 issue(s) across 82 links and 15 buttons

1 link(s) with no accessible text

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

Got: /

1 link(s) open in new tab without warning

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

Got: https://render.com/privacy

7 button(s) with no accessible text

80 link(s) with descriptive text

82 links

1 empty

0 generic text

1 new tab

7 empty buttons

Element	Text	Issue	Suggested Fix
https://render.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link 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
<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

88 links and buttons have descriptive text

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

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

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

https://render.com/privacy

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

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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: 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 Mode✓ Dark Mode Supported

color-scheme meta light dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Lighthouse Accessibility Audits

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.max-md:min-h-[400px] > div.relative > button.shrink-0 `div.flex > div.max-md:min-h-[400px] > div.relative > button.shrink-0`
div.flex > div.max-md:min-h-[400px] > div.relative > button.shrink-0 `div.flex > div.max-md:min-h-[400px] > div.relative > button.shrink-0`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
INSTANCE TYPE: `div.relative > div.absolute > div.font-mono > span.text-gray-400`
Autoscaling `div.col-span-1 > ul.flex > li > a.ease`
Private Networking `div.col-span-1 > ul.flex > li > a.ease`
Render Postgres `div.col-span-1 > ul.flex > li > a.ease`
Render Key Value `div.col-span-1 > ul.flex > li > a.ease`
Persistent Disks `div.col-span-1 > ul.flex > li > a.ease`
Infrastructure As Code `div.col-span-1 > ul.flex > li > a.ease`
Preview Environments `div.col-span-1 > ul.flex > li > a.ease`
Zero Downtime Deploys `div.col-span-1 > ul.flex > li > a.ease`
Render API `div.col-span-1 > ul.flex > li > a.ease`
Static Sites `div.col-span-1 > ul.flex > li > a.ease`
Web Services `div.col-span-1 > ul.flex > li > a.ease`
Private Services `div.col-span-1 > ul.flex > li > a.ease`
Background Workers `div.col-span-1 > ul.flex > li > a.ease`
Cron Jobs `div.col-span-1 > ul.flex > li > a.ease`
Render Postgres `div.col-span-1 > ul.flex > li > a.ease`
Render Key Value `div.col-span-1 > ul.flex > li > a.ease`
Deploy Docker Images `div.col-span-1 > ul.flex > li > a.ease`
Blog `div.col-span-1 > ul.flex > li > a.ease`
Changelog `div.col-span-1 > ul.flex > li > a.ease`
Docs `div.col-span-1 > ul.flex > li > a.ease`
Pricing `div.col-span-1 > ul.flex > li > a.ease`
Render for Startups `div.col-span-1 > ul.flex > li > a.ease`
Articles `div.col-span-1 > ul.flex > li > a.ease`
Security `div.col-span-1 > ul.flex > li > a.ease`
Community `div.col-span-1 > ul.flex > li > a.ease`
Privacy Policy `div.col-span-1 > ul.flex > li > a.ease`
DMCA Policy `div.col-span-1 > ul.flex > li > a.ease`
DPA `div.col-span-1 > ul.flex > li > a.ease`
Acceptable Use `div.col-span-1 > ul.flex > li > a.ease`
Terms of Use `div.col-span-1 > ul.flex > li > a.ease`
About `div.col-span-1 > ul.flex > li > a.ease`
Careers `div.col-span-1 > ul.flex > li > a.ease`
Brand Kit `div.col-span-1 > ul.flex > li > a.ease`
Press `div.col-span-1 > ul.flex > li > a.ease`
Contact `div.col-span-1 > ul.flex > li > a.ease`

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

●Image elements have `[alt]` attributes

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

Landmark Structure

4 landmarks

PASS

4 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

28 headings

PASS

28 headings

Single H1 present

H1 Your fastest path to production forany workload
H2 Click, click, done.
H3 Select a service
H3 Deploy your code
H3 Render does the rest
H3 Deploy apps and agents with zero ops
H3 Intuitive hosting and private networking for web services, Postgres databases, cron jobs, workflows, static sites, background jobs, key value stores, private services, WebSockets, edge caches, isolate
H3 Full-stack previews for every pull request
H3 Load-based autoscaling that handles 100x traffic bursts and beyond
H3 Durable, highly parallel workflows as code
H3 Enterprise-grade Postgres databases
H3 Integrated logs and monitoring for builds, deploys and live services
H2 Intuitive infrastructure, designed for builders
H3 Native language runtimes
H3 Infrastructure as code
H3 Isolated environments
H3 Object storage
H3 Redis-compatible Key Value
H3 WebSockets
H3 Edge caching
H3 Fully-managed TLS
H2 Stay secure and resilient by default
H3 Private networking
H3 Built-in DDoS protection
H3 Managed compliance
H3 Audit controls
H3 Encryption at rest
H3 Unique user identification

A+

Alt Text Quality

All 54 images OK

PASS

All 54 images OK

10 decorative image(s) correctly marked

44 image(s) with good alt text

54 images 44 good alt text 10 decorative

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	Method
#osano-cm-dialog-toggle--category_MARKETING	checkbox	none
#osano-cm-dialog-toggle--category_PERSONALIZATION	checkbox	none
#osano-cm-dialog-toggle--category_ANALYTICS	checkbox	none

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 Your fastest path to…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Click, click, done.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Intuitive infrastruc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Stay secure and resi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Select a service	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Deploy your code	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Render does the rest	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Intuitive hosting an…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Full-stack previews …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Load-based autoscali…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Durable, highly para…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Enterprise-grade Pos…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Integrated logs and …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Native language runt…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Infrastructure as co…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Isolated environment…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Object storage	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Redis-compatible Key…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 WebSockets	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Edge caching	21.00:1	3.0:1	#000000	#FFFFFF	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.

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