Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Alt Text Quality

Action

24 of 242 images have issues

FIX

24 of 242 images have issues

24 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

24 image-in-link without alt text

An image inside a link with no alt creates an empty link.

1 image(s) with alt text over 125 characters

217 image(s) with good alt text

242 images 217 good alt text 24 missing

Issue	Count
missing	24 image(s)
too long	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

No 192x192 icon

A 192px icon is required for PWA installation.

PWA Install Criteria Not Installable

Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗

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.

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 ✗

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

No <nav> landmark 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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Link & Button Quality

Action

13 issue(s) across 153 links and 6 buttons

REVIEW

13 issue(s) across 153 links and 6 buttons

13 link(s) with no accessible text

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

Got: https://ifttt.com/join?source=how-it-works-animation; https://ifttt.com/connect/spotify/youtube; https://ifttt.com/connect/android_messages/gmail; https://ifttt.com/connect/if_notifications/location; https://ifttt.com/connect/maker_webhooks/phone_call; https://ifttt.com/connect/google_calendar/slack; https://ifttt.com/connect/clickup/google_sheets; https://ifttt.com/connect/discord/twitter; https://ifttt.com/connect/feed/wordpress; https://ifttt.com/connect/hue/location (+3 more)

10 link(s) open in new tab without warning

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

Got: https://itunes.apple.com/app/apple-store/id660944635?pt=1752682&ct=homepage-mobile&mt=8; https://play.google.com/store/apps/details?id=com.ifttt.ifttt&utm_source=homepage-mobile&utm_medium=web; https://itunes.apple.com/app/apple-store/id660944635?pt=1752682&ct=/&mt=8; https://play.google.com/store/apps/details?id=com.ifttt.ifttt&utm_source=/&utm_medium=web; https://www.facebook.com/ifttt; https://www.linkedin.com/company/ifttt/; https://www.instagram.com/todayatifttt/; https://www.youtube.com/@IFTTT; https://twitter.com/IFTTT; https://www.tiktok.com/@workswithifttt

130 link(s) with descriptive text

153 links

13 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://ifttt.com/join?source=how-it-wor…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/spotify/youtub…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/android_messag…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/if_notificatio…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/maker_webhooks…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/google_calenda…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/clickup/google…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/discord/twitte…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/feed/wordpress	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/hue/location	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/if_notificatio…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/do_button/myq_…	(empty)	empty	Add link text or aria-label
https://ifttt.com/connect/lifx/weather	(empty)	empty	Add link text or aria-label
https://itunes.apple.com/app/apple-store…	The Apple App Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	The Google Play Store	new tab	Add '(opens in new tab)' to text
https://itunes.apple.com/app/apple-store…	The Apple App Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	The Google Play Store	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/ifttt	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/ifttt/	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/todayatifttt/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@IFTTT	YouTube	new tab	Add '(opens in new tab)' to text
https://twitter.com/IFTTT	Twitter	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@workswithifttt	TikTok	new tab	Add '(opens in new tab)' to text

136 links and buttons have descriptive text

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

https://ifttt.com/join?source=how-it-works-animation; https://ifttt.com/connect/spotify/youtube; https://ifttt.com/connect/android_messages/gmail; https://ifttt.com/connect/if_notifications/location; https://ifttt.com/connect/maker_webhooks/phone_call; https://ifttt.com/connect/google_calendar/slack; https://ifttt.com/connect/clickup/google_sheets; https://ifttt.com/connect/discord/twitter; https://ifttt.com/connect/feed/wordpress; https://ifttt.com/connect/hue/location (+3 more)

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://itunes.apple.com/app/apple-store/id660944635?pt=1752682&ct=homepage-mobile&mt=8; https://play.google.com/store/apps/details?id=com.ifttt.ifttt&utm_source=homepage-mobile&utm_medium=web; https://itunes.apple.com/app/apple-store/id660944635?pt=1752682&ct=/&mt=8; https://play.google.com/store/apps/details?id=com.ifttt.ifttt&utm_source=/&utm_medium=web; https://www.facebook.com/ifttt; https://www.linkedin.com/company/ifttt/; https://www.instagram.com/todayatifttt/; https://www.youtube.com/@IFTTT; https://twitter.com/IFTTT; https://www.tiktok.com/@workswithifttt

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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

13 pass 7 fail WCAG AA

h1 Automate.

1.00:1

#FFFFFF

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Save time.

1.00:1

#FFFFFF

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Get more done.

1.00:1

#FFFFFF

needs 3.0:1 (large text)

32px · bottom of viewport

title IFTTT - Automate business & home

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

span Recent

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

span Recommendations

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

span Finance

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Automate.	1.00:1	3.0:1	#FFFFFF	#FFFFFF	Fail
h1 Save time.	1.00:1	3.0:1	#FFFFFF	#FFFFFF	Fail
h1 Get more done.	1.00:1	3.0:1	#FFFFFF	#FFFFFF	Fail
h2 How does IFTTT work?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Connect an automatio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Work smarter with 10…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Automate your everyd…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Save time and boost …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Set your home on aut…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Transform your workf…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The leading no-code …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Make your Applets mo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Smarter workflows, m…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Our most popular int…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Top productivity int…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Our top smart home i…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title IFTTT - Automate bus…	1.32:1	4.5:1	#000000	#222222	Fail
span Recent	1.32:1	4.5:1	#000000	#222222	Fail
span Recommendations	1.32:1	4.5:1	#000000	#222222	Fail
span Finance	1.32:1	4.5:1	#000000	#222222	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.

A+

Heading Hierarchy

27 headings

PASS

27 headings

Single H1 present

H1 Automate. Save time.Get more done.
H2 How does IFTTT work?
H2 Connect an automation in a minute or less
H2 Work smarter with 1000+ services
H2 Automate your everyday
H3 Our most popular integrations
H4 Easy DIY building
H4 Your integrations, your way
H4 Do more with multiple actions
H4 Up-level with AI
H2 Save time and boost productivity
H3 Top productivity integrations
H4 Sync tasks and calendars
H4 Track billable hours
H4 Streamline work communication
H4 Use AI to jumpstart projects
H2 Set your home on autopilot
H3 Our top smart home integrations
H4 Location-based control
H4 Voice assistants
H4 Energy-saving automations
H4 Smart home security automation
H2 Transform your workflows with AI
H2 The leading no-code automation app on mobile
H2 Make your Applets more powerful
H2 Top brands trust IFTTT IFTTT
H2 Smarter workflows, measurable results

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#universal-search-input	search	Search	aria-label

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title IFTTT ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 26 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
Save new Spotify Discover Weekly songs to an archive `a.applet-card-body > div.content > div.title > span`
Spotify `a.applet-card-body > div.content > div.owner > span.author`
124K `a.applet-card-body > div.meta > span.installs > span.number`
Google `a.applet-card-body > div.content > div.owner > span.author`
132K `a.applet-card-body > div.meta > span.installs > span.number`
div.content > div.owner > span > span.by `div.content > div.owner > span > span.by`
div.content > div.owner > span > span.author `div.content > div.owner > span > span.author`
a.applet-card-body > div.meta > span.installs > span.number `a.applet-card-body > div.meta > span.installs > span.number`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name `div.explore-services-module__container > div.explore-services-module__grid > a.explore-services-module__tile > span.explore-services-module__name`
div.user-testimonial-card-wrapper > div.user-testimonial-card > div.user-testimonial-card__quote > p.user-testimonial-card__quote-text `div.user-testimonial-card-wrapper > div.user-testimonial-card > div.user-testimonial-card__quote > p.user-testimonial-card__quote-text`
div.user-testimonial-card > div.user-testimonial-card__person > div.user-testimonial-card__profile > p.user-testimonial-card__profile-name `div.user-testimonial-card > div.user-testimonial-card__person > div.user-testimonial-card__profile > p.user-testimonial-card__profile-name`

These are opportunities to improve the legibility of your content.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.bg--white > section.how-it-works > div.how-it-works-container > a.how-it-works-animation `main.bg--white > section.how-it-works > div.how-it-works-container > a.how-it-works-animation`

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.

○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

●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

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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●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

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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