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

Link & Button Quality

Action

19 issue(s) across 174 links and 77 buttons

FIX

19 issue(s) across 174 links and 77 buttons

2 link(s) with no accessible text

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

Got: https://www.eater.com/newsletters; https://www.eater.com/newsletters

4 link(s) with generic text

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

Got: /video ("More"); /add-to-cart ("More"); /video ("More"); /add-to-cart ("More")

14 link(s) open in new tab without warning

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

Got: https://apps.apple.com/app/apple-store/id6469005148?pt=541474&ct=Eater_Main_N…; https://www.youtube.com/user/eater1/videos; https://apps.apple.com/app/apple-store/id6469005148?pt=541474&ct=Eater_NavBar…; https://www.amazon.com/stores/Eater/author/B0CH1LK92L; https://www.amazon.com/stores/page/0E087226-9453-40C5-B327-7B9D66562F97?ingre…; https://www.amazon.com/stores/page/579AAC3B-DB9F-419C-AD6A-7D3EB2A47A11; https://shop.eater.com/; https://eaterwineclub.com/; https://punchdrink.com/; https://www.thrillist.com/ (+4 more)

13 button(s) with no accessible text

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

Got: button._1632iru4 (#330 on page); button (#2543 on page); button (#2572 on page); button (#2672 on page); button (#2704 on page); button (#2720 on page); button (#2747 on page); button (#2771 on page); button (#2802 on page); button (#2864 on page) (+3 more)

154 link(s) with descriptive text

174 links

2 empty

4 generic text

14 new tab

13 empty buttons

Element	Text	Issue	Suggested Fix
https://apps.apple.com/app/apple-store/i…	App IconGet ourApp	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/eater1/vide…	VideoWatch	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/app/apple-store/i…	App	new tab	Add '(opens in new tab)' to text
https://www.amazon.com/stores/Eater/auth…	BooksExternal Link	new tab	Add '(opens in new tab)' to text
https://www.amazon.com/stores/page/0E087…	TablewareExternal Link	new tab	Add '(opens in new tab)' to text
https://www.amazon.com/stores/page/579AA…	CookwareExternal Link	new tab	Add '(opens in new tab)' to text
https://shop.eater.com/	MerchExternal Link	new tab	Add '(opens in new tab)' to text
https://eaterwineclub.com/	Wine ClubExternal Link	new tab	Add '(opens in new tab)' to text
https://punchdrink.com/	PunchExternal Link	new tab	Add '(opens in new tab)' to text
https://www.thrillist.com/	ThrillistExternal Link	new tab	Add '(opens in new tab)' to text
https://www.eater.com/newsletters	(empty)	empty	Add link text or aria-label
/video	More	generic text	Replace with descriptive text
Before: More Suggested: Video
/add-to-cart	More	generic text	Replace with descriptive text
Before: More Suggested: Add To Cart
/video	More	generic text	Replace with descriptive text
Before: More Suggested: Video
/add-to-cart	More	generic text	Replace with descriptive text
Before: More Suggested: Add To Cart
https://apps.apple.com/us/app/eater/id64…	Get the App	new tab	Add '(opens in new tab)' to text
https://www.eater.com/newsletters	(empty)	empty	Add link text or aria-label
https://www.voxmedia.com/legal/cookie-po…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.voxmedia.com/legal/cookie-po…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	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
<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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

218 links and buttons have descriptive text

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

https://www.eater.com/newsletters; https://www.eater.com/newsletters

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

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

/video ("More"); /add-to-cart ("More"); /video ("More"); /add-to-cart ("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

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

https://apps.apple.com/app/apple-store/id6469005148?pt=541474&ct=Eater_Main_N…; https://www.youtube.com/user/eater1/videos; https://apps.apple.com/app/apple-store/id6469005148?pt=541474&ct=Eater_NavBar…; https://www.amazon.com/stores/Eater/author/B0CH1LK92L; https://www.amazon.com/stores/page/0E087226-9453-40C5-B327-7B9D66562F97?ingre…; https://www.amazon.com/stores/page/579AAC3B-DB9F-419C-AD6A-7D3EB2A47A11; https://shop.eater.com/; https://eaterwineclub.com/; https://punchdrink.com/; https://www.thrillist.com/ (+4 more)

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._1632iru4 (#330 on page); button (#2543 on page); button (#2572 on page); button (#2672 on page); button (#2704 on page); button (#2720 on page); button (#2747 on page); button (#2771 on page); button (#2802 on page); button (#2864 on page) (+3 more)

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

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 ✗

Heading Hierarchy

39 headings

REVIEW

39 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Video
H2 Add to Cart
H2 The Latest
H2 Video
H2 Add to Cart
H2 Eater Today
H2 Download the Eater App
H2 Eater Maps
H2 Most Popular
H2 Dining Out
H2 Privacy Notice
H3 Ways we may use your data:
H2 Privacy Center
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies 77 partners can use this purpose
H5 Ensure security, prevent and detect fraud, and fix errors 77 partners can use this special purpose
H4 Functional Cookies 104 partners can use this purpose
H5 Use limited data to select advertising 79 partners can use this purpose
H5 Use limited data to select content 19 partners can use this purpose
H5 Use profiles to select personalised content 21 partners can use this purpose
H5 Create profiles to personalise content 24 partners can use this purpose
H5 Deliver and present advertising and content 76 partners can use this special purpose
H5 Identify devices based on information transmitted automatically 59 partners can use this feature
H4 Performance Cookies 34 partners can use this purpose
H5 Link different devices 34 partners can use this feature
H4 Social Media & Embedded Content
H4 Targeting Cookies 48 partners can use this purpose
H5 Match and combine data from other data sources 48 partners can use this feature
H4 Measure content performance 36 partners can use this purpose
H4 Use profiles to select personalised advertising 60 partners can use this purpose
H5 Create profiles for personalised advertising 63 partners can use this purpose
H4 Understand audiences through statistics or combinations of data from different sources 63 partners can use this purpose
H5 Develop and improve services 77 partners can use this purpose
H5 Measure advertising performance 103 partners can use this purpose
H4 Store and/or access information on a device 89 partners can use this purpose
H4 Use precise geolocation data 34 partners can use this special feature
H4 Actively scan device characteristics for identification 15 partners can use this special feature
H4 Save and communicate privacy choices 67 partners can use this special purpose
H3 Cookie List

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / 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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

Action

7 icon(s) detected

REVIEW

7 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 15 pass AA only

span App

4.16:1

#000000

#D32D1F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Dining Out

4.16:1

#000000

#D32D1F

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Video	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Add to Cart	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 The Latest	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Video	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Add to Cart	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Eater Today	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Download the Eater A…	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Eater Maps	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Most Popular	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Dining Out	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Privacy Notice	4.16:1	3.0:1	#000000	#D32D1F	Pass
h2 Privacy Center	4.16:1	3.0:1	#000000	#D32D1F	Pass
h3 Ways we may use your…	4.16:1	3.0:1	#000000	#D32D1F	Pass
h3 Manage Consent Prefe…	4.16:1	3.0:1	#000000	#D32D1F	Pass
h3 Cookie List	4.16:1	3.0:1	#000000	#D32D1F	Pass
title Eater	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Get our	10.74:1	4.5:1	#000000	#EBA9A3	Pass
span App	4.16:1	4.5:1	#000000	#D32D1F	Fail
a Dining Out	4.16:1	4.5:1	#000000	#D32D1F	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.

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

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

A+

Alt Text Quality

All 122 images OK

PASS

All 122 images OK

122 image(s) with good alt text

122 images 122 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 26 controls have issues

PASS

1 of 26 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

25 control(s) properly labeled

26 controls

25 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#:R2ja3d56:	text	Search	for/id
#:Rra3d56:	select	Visit another Eater city site	for/id
#email	email	Email (required)	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-sub-group-id-IAB2V2_2	checkbox	Use limited data to select advertising	aria-label
#ot-sub-group-id-IAB2V2_11	checkbox	Use limited data to select content	aria-label
#ot-sub-group-id-IAB2V2_6	checkbox	Use profiles to select personalised content	aria-label
#ot-sub-group-id-IAB2V2_5	checkbox	Create profiles to personalise content	aria-label
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0005	checkbox	Social Media & Embedded Content	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-IAB2V2_8	checkbox	Measure content performance	for/id
#ot-group-id-IAB2V2_4	checkbox	Use profiles to select personalised advertising	for/id
#ot-sub-group-id-IAB2V2_3	checkbox	Create profiles for personalised advertising	aria-label
#ot-group-id-IAB2V2_9	checkbox	Understand audiences through statistics or combinations of data from different sources	for/id
#ot-sub-group-id-IAB2V2_10	checkbox	Develop and improve services	aria-label
#ot-sub-group-id-IAB2V2_7	checkbox	Measure advertising performance	aria-label
#ot-group-id-IAB2V2_1	checkbox	Store and/or access information on a device	for/id
#ot-group-id-ISF2V2_1	checkbox	Use precise geolocation data	for/id
#ot-group-id-ISF2V2_2	checkbox	Actively scan device characteristics for identification	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#g-recaptcha-response-100000	textarea	(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

Lighthouse Accessibility Audits

Score 93/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.

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
div.tzi1w98 > ul.wovzix0 > li > a.wovzix1 `div.tzi1w98 > ul.wovzix0 > li > a.wovzix1`

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
Archives `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`
Contact Us `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`
Send Us a Tip `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`
Community Guidelines `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`
Masthead `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`
About Eater `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`
Ethics Statement `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`
Press Room `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`
Newsletters `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`
Maps Methodology `div._1c7i3jt0 > ul._1c7i3jt1 > li._1c7i3jt2 > a._1c7i3jt3`

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

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

●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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

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

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

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