Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

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

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 ✗

Landmark Structure

Action

8 landmarks

REVIEW

8 landmarks

No <main> landmark found

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

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

Search landmark present

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

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

Form Accessibility

Action

3 of 3 controls have issues

REVIEW

3 of 3 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">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="find_desc" id="search_description">; <input type="search" id="search_location">

3 controls

0 labeled

2 placeholder only

1 unlabeled

Control	Type	Label	Method
#search_description	search	(things to do, nail salons, plumbers)	placeholder only
#search_location	search	(address, neighborhood, city, state or zip)	placeholder only
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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

Action

4 issue(s) across 105 links and 21 buttons

REVIEW

4 issue(s) across 105 links and 21 buttons

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: ("More"); ("More"); /search ("More")

7 image-only link(s) without alt text

1 button(s) with no accessible text

95 link(s) with descriptive text

105 links

0 empty

3 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
	More	generic text	Replace with descriptive text
Before: More Suggested: Home page
	More	generic text	Replace with descriptive text
Before: More Suggested: Home page
/search?find_desc=Restaurants&find_loc=S…	Restaurants	img no alt	Add alt attribute to the image
/search?find_desc=Shopping&find_loc=San+…	Shopping	img no alt	Add alt attribute to the image
/search?find_desc=Nightlife&find_loc=San…	Nightlife	img no alt	Add alt attribute to the image
/search?find_desc=Active+Life&find_loc=S…	Active Life	img no alt	Add alt attribute to the image
/search?find_desc=Beauty+%26+Spas&find_l…	Beauty & Spas	img no alt	Add alt attribute to the image
/search?find_desc=Automotive&find_loc=Sa…	Automotive	img no alt	Add alt attribute to the image
/search?find_desc=Home+Services&find_loc…	Home Services	img no alt	Add alt attribute to the image
/search	More	generic text	Replace with descriptive text
Before: More Suggested: Search
<input>	(empty)	empty	Add button text or aria-label

115 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

("More"); ("More"); /search ("More")

Why this matters

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

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

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 15 fail WCAG AA

REVIEW

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

5 pass 15 fail WCAG AA 3 pass AA only

title Restaurants, Dentists, Bars, Beauty Salo…

1.15:1

#000000

#30040D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Yelp

1.11:1

#000000

#141010

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Yelp for Business

1.10:1

#000000

#0E0F11

needs 4.5:1 (normal text)

16px · top of page (header area)

p Write a Review

1.11:1

#000000

#0E1114

needs 4.5:1 (normal text)

16px · top of page (header area)

p Start a Project

1.15:1

#000000

#131519

needs 4.5:1 (normal text)

16px · above the fold

span Log In

1.16:1

#000000

#13161A

needs 4.5:1 (normal text)

16px · above the fold

span Sign Up

1.17:1

#000000

#141719

needs 4.5:1 (normal text)

16px · above the fold

span Restaurants

1.17:1

#000000

#16171B

needs 4.5:1 (normal text)

16px · above the fold

span Home & Garden

1.21:1

#000000

#171B1C

needs 4.5:1 (normal text)

16px · above the fold

span Auto Services

1.32:1

#000000

#222223

needs 4.5:1 (normal text)

16px · above the fold

span Health & Beauty

1.23:1

#000000

#181D1F

needs 4.5:1 (normal text)

16px · above the fold

span Travel & Activities

1.25:1

#000000

#191E1F

needs 4.5:1 (normal text)

16px · above the fold

span More

1.32:1

#000000

#222221

needs 4.5:1 (normal text)

16px · above the fold

span More

1.16:1

#000000

#12161A

needs 4.5:1 (normal text)

16px · mid-page

span Tax services

2.91:1

#000000

#505769

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Beat the tax clock	4.70:1	3.0:1	#000000	#79767D	Pass
h2 Recent Activity	4.12:1	3.0:1	#000000	#686F75	Pass
h2 Categories	5.04:1	3.0:1	#000000	#7F7B7F	Pass
title Restaurants, Dentist…	1.15:1	4.5:1	#000000	#30040D	Fail
a Yelp	1.11:1	4.5:1	#000000	#141010	Fail
span Yelp for Business	1.10:1	4.5:1	#000000	#0E0F11	Fail
p Write a Review	1.11:1	4.5:1	#000000	#0E1114	Fail
p Start a Project	1.15:1	4.5:1	#000000	#131519	Fail
span Log In	1.16:1	4.5:1	#000000	#13161A	Fail
span Sign Up	1.17:1	4.5:1	#000000	#141719	Fail
span Restaurants	1.17:1	4.5:1	#000000	#16171B	Fail
span Home & Garden	1.21:1	4.5:1	#000000	#171B1C	Fail
span Auto Services	1.32:1	4.5:1	#000000	#222223	Fail
span Health & Beauty	1.23:1	4.5:1	#000000	#181D1F	Fail
span Travel & Activities	1.25:1	4.5:1	#000000	#191E1F	Fail
span More	1.32:1	4.5:1	#000000	#222221	Fail
span More	1.16:1	4.5:1	#000000	#12161A	Fail
span Tax services	2.91:1	4.5:1	#000000	#505769	Fail
a South Tampa CPA Serv…	5.31:1	4.5:1	#000000	#788094	Pass
p Photo from the busin…	5.17:1	4.5:1	#000000	#757E95	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.

A+

Heading Hierarchy

3 headings

PASS

3 headings

Single H1 present

H1 Beat the tax clock
H2 Recent Activity
H2 Categories

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

8 decorative image(s) correctly marked

2 image(s) with good alt text

10 images 2 good alt text 8 decorative

All images have appropriate alt text.

Lighthouse Accessibility Audits

Score 92/100 — 3 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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.y-css-1w1a6wv > div.y-css-1ilqd8r > div.y-css-984oc > img#_R_kqqql2iu_ `div.y-css-1w1a6wv > div.y-css-1ilqd8r > div.y-css-984oc > img#_R_kqqql2iu_`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
À propos `li.y-css-1jjy2nq > span.y-css-1djd53t > div.y-css-1wba61o > a.y-css-mh3hcb`
Blog `li.y-css-1jjy2nq > span.y-css-1djd53t > div.y-css-1wba61o > a.y-css-mh3hcb`
Aide `li.y-css-1jjy2nq > span.y-css-1djd53t > div.y-css-1wba61o > a.y-css-mh3hcb`
Conditions `li.y-css-1jjy2nq > span.y-css-1djd53t > div.y-css-1wba61o > a.y-css-mh3hcb`
Politique de confidentialité `li.y-css-1jjy2nq > span.y-css-1djd53t > div.y-css-1wba61o > a.y-css-mh3hcb`
Manage Cookies `li.y-css-1jjy2nq > span.y-css-1djd53t > div.y-css-1wba61o > a.y-css-mh3hcb`
Yelp pour les professionnels `li.y-css-1jjy2nq > span.y-css-1djd53t > div.y-css-1wba61o > a.y-css-mh3hcb`
Marketing & Advertising Agencies `li.y-css-1jjy2nq > span.y-css-1djd53t > div.y-css-1wba61o > a.y-css-mh3hcb`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Santa Lyna 9 Petit déjeuner & brunch `div.y-css-11p0fx8 > section.y-css-mhg9c5 > div.y-css-tn7lw0 > a.y-css-1h2mj76`
Ouvert `div > div.y-css-mhg9c5 > div.y-css-275p19 > a.link__09f24___SI7S`

○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

●Input buttons have discernible text.

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

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

●Background and foreground colors have a sufficient contrast ratio

●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

●No element has a `[tabindex]` value greater than 0

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

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

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