Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

2 landmarks

FIX

2 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

No banner (header) landmark

No contentinfo (footer) landmark

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

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

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

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

Alt Text Quality

Action

19 of 20 images have issues

FIX

19 of 20 images have issues

19 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

17 image-in-link without alt text

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

1 image(s) with good alt text

20 images 1 good alt text 19 missing

Issue	Count
missing	19 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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-hfxwx4

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://eatbu.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://eatbu.com/manifest.json

Manifest contains invalid JSON.

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.

Got: #ffffff

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

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 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Link & Button Quality

1 issue(s) across 28 links and 0 buttons

REVIEW

1 issue(s) across 28 links and 0 buttons

1 link(s) with no accessible text

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

Got: #

3 link(s) open in new tab without warning

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

Got: https://support.dish.co/l/en/article/spke9vkrj4-faqs-dish-website; https://www.dish.co/terms-of-use/; https://www.dish.co/privacy-policy/

24 link(s) with descriptive text

28 links

1 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	English	img no alt	Add alt attribute to the image
?lang=cs	Čeština	img no alt	Add alt attribute to the image
?lang=de	Deutsch	img no alt	Add alt attribute to the image
?lang=en	English	img no alt	Add alt attribute to the image
?lang=es	Español	img no alt	Add alt attribute to the image
?lang=fr	Français	img no alt	Add alt attribute to the image
?lang=hr	Hrvatski	img no alt	Add alt attribute to the image
?lang=it	Italiano	img no alt	Add alt attribute to the image
?lang=hu	Magyar	img no alt	Add alt attribute to the image
?lang=nl	Nederlands	img no alt	Add alt attribute to the image
?lang=pl	Polski	img no alt	Add alt attribute to the image
?lang=pt	Português	img no alt	Add alt attribute to the image
?lang=ro	Română	img no alt	Add alt attribute to the image
?lang=ru	Русский	img no alt	Add alt attribute to the image
?lang=sk	Slovensky	img no alt	Add alt attribute to the image
?lang=tr	Türkçe	img no alt	Add alt attribute to the image
?lang=uk	Українська	img no alt	Add alt attribute to the image
https://support.dish.co/l/en/article/spk…	FAQ	new tab	Add '(opens in new tab)' to text
https://www.dish.co/terms-of-use/	Terms of Use	new tab	Add '(opens in new tab)' to text
https://www.dish.co/privacy-policy/	Data Privacy	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label

24 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://support.dish.co/l/en/article/spke9vkrj4-faqs-dish-website; https://www.dish.co/terms-of-use/; https://www.dish.co/privacy-policy/

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

14 icon(s) detected

REVIEW

14 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

a Čeština

1.77:1

#000000

#313939

needs 4.5:1 (normal text)

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

a Deutsch

1.60:1

#000000

#293233

needs 4.5:1 (normal text)

16px · top of page (header area)

a English

1.40:1

#000000

#1C2929

needs 4.5:1 (normal text)

16px · above the fold

a Español

1.64:1

#000000

#2B3433

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Français

1.24:1

#000000

#121F20

needs 4.5:1 (normal text)

16px · above the fold

a Hrvatski

1.37:1

#000000

#1C2728

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Italiano

1.77:1

#000000

#293A3E

needs 4.5:1 (normal text)

16px · above the fold

a Magyar

1.38:1

#000000

#1B2828

needs 4.5:1 (normal text)

16px · above the fold

a Nederlands

2.31:1

#000000

#50473F

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Polski

1.15:1

#000000

#0C1718

needs 4.5:1 (normal text)

16px · above the fold

a Português

1.36:1

#000000

#1F2623

needs 4.5:1 (normal text)

16px · above the fold

a Română

2.24:1

#000000

#404848

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

a Русский

1.24:1

#000000

#111F1E

needs 4.5:1 (normal text)

16px · mid-page

a Slovensky

1.81:1

#000000

#343A39

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

a Türkçe

3.65:1

#000000

#6D6463

needs 4.5:1 (normal text)

16px · mid-page

a Українська

2.18:1

#000000

#4A443A

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

span Your website for hospitality

1.89:1

#000000

#3D3C32

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

span Whether your establishment is a restaura…

2.55:1

#000000

#524E4B

needs 4.5:1 (normal text)

16px · mid-page

8 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
title DISH WEBSITE	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span English	8.97:1	4.5:1	#000000	#A7AAA9	Pass
a Čeština	1.77:1	4.5:1	#000000	#313939	Fail
a Deutsch	1.60:1	4.5:1	#000000	#293233	Fail
a English	1.40:1	4.5:1	#000000	#1C2929	Fail
a Español	1.64:1	4.5:1	#000000	#2B3433	Fail
a Français	1.24:1	4.5:1	#000000	#121F20	Fail
a Hrvatski	1.37:1	4.5:1	#000000	#1C2728	Fail
a Italiano	1.77:1	4.5:1	#000000	#293A3E	Fail
a Magyar	1.38:1	4.5:1	#000000	#1B2828	Fail
a Nederlands	2.31:1	4.5:1	#000000	#50473F	Fail
a Polski	1.15:1	4.5:1	#000000	#0C1718	Fail
a Português	1.36:1	4.5:1	#000000	#1F2623	Fail
a Română	2.24:1	4.5:1	#000000	#404848	Fail
a Русский	1.24:1	4.5:1	#000000	#111F1E	Fail
a Slovensky	1.81:1	4.5:1	#000000	#343A39	Fail
a Türkçe	3.65:1	4.5:1	#000000	#6D6463	Fail
a Українська	2.18:1	4.5:1	#000000	#4A443A	Fail
span Your website for hos…	1.89:1	4.5:1	#000000	#3D3C32	Fail
span Whether your establi…	2.55:1	4.5:1	#000000	#524E4B	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.

Lighthouse Accessibility Audits

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

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
REGISTER NOW `div.mod-home-tagline > div.jumbotron > div.buttons-wrap > a.btn`
Accept All `div.sc-dtInlm > div.sc-cWSHoV > div.sc-kOPcWz > button.sc-gsFSXq`
Deny `div.sc-dtInlm > div.sc-cWSHoV > div.sc-kOPcWz > button.sc-gsFSXq`

These are opportunities to improve the legibility of your content.

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
li.dropdown > a.dropdown-toggle > strong.img-holder > img `li.dropdown > a.dropdown-toggle > strong.img-holder > img`

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#navbar > ul.nav > li.dropdown > a.dropdown-toggle`

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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.

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

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

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

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Your website for hospitality

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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