Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLink & Button QualityAction7 issue(s) across 119 links and 15 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| / | (empty) | empty | Add link text or aria-label |
| https://tailscale.com/winter-update-week… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Winter Update Week 26 | |||
| https://tailscale.com/tailscaleup | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Tailscaleup | |||
| / | (empty) | empty | Add link text or aria-label |
| https://tailscale.com/use-cases/business… | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Business Vpn | |||
| https://tailscale.com/use-cases/business… | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Business Vpn | |||
| <button> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
/; /
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
Generic link text like 'click here' doesn't describe the destination.
https://tailscale.com/winter-update-week-26 ("Read more"); https://tailscale.com/tailscaleup ("Learn more"); https://tailscale.com/use-cases/business-vpn ("Learn more"); https://tailscale.com/use-cases/business-vpn ("Learn more")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Icon-only buttons need an aria-label so screen readers can announce them.
button.inline-flex (#253 on page)
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
DFavicon & BrandingAction3 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure9 landmarksREVIEW
Multiple navigations need aria-label to distinguish them for screen readers.
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.
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
BHeading Hierarchy18 headings, 1 skip(s)REVIEW
- H3 Company
- H3 Help & Support
- H3 Legal
- H3 Social
- H1 The best secure connectivity platform for the AI era
- H1 The best secure connectivity platform for the AI era duplicate H1
- H3 Business VPN skipped
- H3 Business VPN
- H2 20,000 businesses choose Tailscale
- H2 20,000 businesses choose Tailscale
- H2 Easy, secure, identity-based access to anything
- H2 Easy, secure, identity-based access to anything
- H3 Installation takes minutes
- H3 Switching is easy
- H3 Bridge hybrid environments
- H2 Developer approved, But don’t just take our word for it.
- H2 Developer approved, But don’t just take our word for it.
- H3 Secure your networking using identity with Tailscale
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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
B404 Error PageHTTP 404, custom pageREVIEW
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
CColor Contrast (Screenshot)Action20 text elements analyzed, 3 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 The best secure conn… | 5.83:1 | 3.0:1 | #000000 | #868787 | Pass |
| h1 The best secure conn… | 5.83:1 | 3.0:1 | #000000 | #868787 | Pass |
| h2 Easy, secure, identi… | 5.83:1 | 3.0:1 | #000000 | #868787 | Pass |
| h2 Easy, secure, identi… | 5.83:1 | 3.0:1 | #000000 | #868787 | Pass |
| h3 Business VPN | 5.83:1 | 3.0:1 | #000000 | #868787 | Pass |
| h3 Business VPN | 5.83:1 | 3.0:1 | #000000 | #868787 | Pass |
| h3 Installation takes m… | 5.83:1 | 3.0:1 | #000000 | #868787 | Pass |
| h3 Switching is easy | 5.83:1 | 3.0:1 | #000000 | #868787 | Pass |
| h3 Bridge hybrid enviro… | 5.83:1 | 3.0:1 | #000000 | #868787 | Pass |
| title Tailscale | Secure C… | 1.20:1 | 4.5:1 | #000000 | #1A1919 | Fail |
| a APERTURE IS NOW AVAI… | 1.20:1 | 4.5:1 | #000000 | #1A1919 | Fail |
| span Read more → | 1.20:1 | 4.5:1 | #000000 | #1A1919 | Fail |
| a Blog | 6.84:1 | 4.5:1 | #000000 | #939393 | Pass |
| a Docs | 6.84:1 | 4.5:1 | #000000 | #939393 | Pass |
| a Download | 6.49:1 | 4.5:1 | #000000 | #8F8F8E | Pass |
| a Contact sales | 6.49:1 | 4.5:1 | #000000 | #8F8F8E | Pass |
| button Platform | 6.49:1 | 4.5:1 | #000000 | #8F8F8E | Pass |
| p Meet Tailscale | 6.49:1 | 4.5:1 | #000000 | #8F8F8E | Pass |
| a How Tailscale Works | 6.49:1 | 4.5:1 | #000000 | #8F8F8E | Pass |
| a WireGuard® for Ente… | 6.49:1 | 4.5:1 | #000000 | #8F8F8E | 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.
BLighthouse Accessibility AuditsScore 87/100 — 4 failing, 25 passedREVIEW
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
header.bg-white > div.mx-auto > div.xlsmall:justify-between > button.inline-flex header.bg-white > div.mx-auto > div.xlsmall:justify-between > button.inline-flex |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.sticky > header.bg-white > div.mx-auto > a.inline-flex div.sticky > header.bg-white > div.mx-auto > a.inline-flex |
div.mx-auto > div.grid > div.col-span-1 > a.inline-flex div.mx-auto > div.grid > div.col-span-1 > a.inline-flex |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Business VPN div.mx-auto > button.flex > div.flex > span.font-semibold |
PRODUCT div.mt-64 > div.shadow-2 > div.flex > p.font-mdio |
Over 100 integrations.
div.mx-auto > div.shadow-2 > h2.title-md > span.text-gray-700 |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Business VPN div.mt-64 > div.shadow-2 > div.flex > h3.title-2xl |
These are opportunities to improve keyboard navigation in your application.