Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 7 REVIEW 4 FIX

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

17 headings, 1 skip(s)

REVIEW

17 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 Together, We Chili’s
H2 What are We All About?
H2 What’s at the Heart of a ChiliHead?
H3 Love
H3 Belonging
H3 Enjoyment
H2 #ChilisLove Means Taking Good Care of the Ones We Love
H2 To Know Us is to Love Us!
H2 Our Giving Promise!
H2 Corporate Sites
H2 Career Sites
H2 DID SOMEONE SAY COOKIES?
H2 (empty)
H4 Essential skipped
H4 Performance
H4 Advertising
H3 Cookie List

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Link & Button Quality

Action

4 issue(s) across 33 links and 11 buttons

REVIEW

4 issue(s) across 33 links and 11 buttons

3 link(s) with generic text

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

Got: /benefits#learning ("Learn more"); /our-story#beliefs ("Learn more"); /benefits#perks ("Learn more")

14 link(s) open in new tab without warning

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

Got: https://www.chilis.com; https://www.brinker.com; https://www.brinkerjobs.com; https://twitter.com/chilis; https://www.linkedin.com/company/chili's; https://www.glassdoor.com/Overview/Working-at-Chili-s-Grill-and-Bar-EI_IE1433…; https://www.instagram.com/chilis; https://www.brinker.com/terms&conditions; https://www.brinker.com/privacy; https://www.brinker.com/fraud-alerts (+4 more)

1 button(s) with no accessible text

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

Got: button#search-btn

16 link(s) with descriptive text

33 links

0 empty

3 generic text

14 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/benefits#learning	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Benefits#Learning
/our-story#beliefs	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Our Story#Beliefs
/benefits#perks	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Benefits#Perks
https://www.chilis.com	chilis.com	new tab	Add '(opens in new tab)' to text
https://www.brinker.com	brinker.com	new tab	Add '(opens in new tab)' to text
https://www.brinkerjobs.com	Brinker Jobs	new tab	Add '(opens in new tab)' to text
https://twitter.com/chilis	Twitter logo	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/chili's	LinkedIn logo	new tab	Add '(opens in new tab)' to text
https://www.glassdoor.com/Overview/Worki…	Glassdoor logo	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/chilis	Instagram logo	new tab	Add '(opens in new tab)' to text
https://www.brinker.com/terms&conditions	Terms and Conditions	new tab	Add '(opens in new tab)' to text
https://www.brinker.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.brinker.com/fraud-alerts	Fraud Alerts	new tab	Add '(opens in new tab)' to text
https://brinker.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://brinker.com/terms-and-condition…	Terms and Conditions	new tab	Add '(opens in new tab)' to text
https://brinker.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/solutions/conse…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

26 links and buttons have descriptive text

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

/benefits#learning ("Learn more"); /our-story#beliefs ("Learn more"); /benefits#perks ("Learn 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://www.chilis.com; https://www.brinker.com; https://www.brinkerjobs.com; https://twitter.com/chilis; https://www.linkedin.com/company/chili's; https://www.glassdoor.com/Overview/Working-at-Chili-s-Grill-and-Bar-EI_IE1433…; https://www.instagram.com/chilis; https://www.brinker.com/terms&conditions; https://www.brinker.com/privacy; https://www.brinker.com/fraud-alerts (+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#search-btn

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

Iframe Accessibility

2/4 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/4 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (3 below threshold)

3 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <label> 10.0px ("Keyword"); <label> 10.0px ("Location"); <div> 10.0px ("Chili's serves communities across multip...").

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 Page not found - Chili’s Careers ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

5 icon(s) detected

REVIEW

5 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, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h1 Together, We Chili’s

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

32px · mid-page

h2 What are We All About?

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What’s at the Heart of a ChiliHead?

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 #ChilisLove Means Taking Good Care of th…

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 To Know Us is to Love Us!

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Corporate Sites

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Career Sites

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 DID SOMEONE SAY COOKIES?

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Love

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Belonging

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Enjoyment

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cookie List

1.46:1

#000000

#22235B

needs 3.0:1 (large text)

19px · bottom of viewport

span Search Jobs

3.06:1

#000000

#69583B

needs 4.5:1 (normal text)

16px · top of page (header area)

span Learn About Us

3.67:1

#000000

#756447

needs 4.5:1 (normal text)

16px · above the fold

span Close Menu

2.71:1

#000000

#6B4C35

needs 4.5:1 (normal text)

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

span Our Story

2.18:1

#000000

#564032

needs 4.5:1 (normal text)

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

span Together, we Chili’s! See how our bran…

2.02:1

#000000

#5A381F

needs 4.5:1 (normal text)

16px · above the fold

2 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 Together, We Chili�…	1.46:1	3.0:1	#000000	#22235B	Fail
h2 What are We All Abou…	1.46:1	3.0:1	#000000	#22235B	Fail
h2 What’s at the Hear…	1.46:1	3.0:1	#000000	#22235B	Fail
h2 #ChilisLove Means Ta…	1.46:1	3.0:1	#000000	#22235B	Fail
h2 To Know Us is to Lov…	1.46:1	3.0:1	#000000	#22235B	Fail
h2 Corporate Sites	1.46:1	3.0:1	#000000	#22235B	Fail
h2 Career Sites	1.46:1	3.0:1	#000000	#22235B	Fail
h2 DID SOMEONE SAY COOK…	1.46:1	3.0:1	#000000	#22235B	Fail
h3 Love	1.46:1	3.0:1	#000000	#22235B	Fail
h3 Belonging	1.46:1	3.0:1	#000000	#22235B	Fail
h3 Enjoyment	1.46:1	3.0:1	#000000	#22235B	Fail
h3 Cookie List	1.46:1	3.0:1	#000000	#22235B	Fail
title Home \| Chili’s Car…	10.86:1	4.5:1	#000000	#F8A4A7	Pass
title Home - Chili’s Car…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Search Jobs	3.06:1	4.5:1	#000000	#69583B	Fail
span Learn About Us	3.67:1	4.5:1	#000000	#756447	Fail
span Close Menu	2.71:1	4.5:1	#000000	#6B4C35	Fail
span Our Story	2.18:1	4.5:1	#000000	#564032	Fail
span Together, we Chili�…	2.02:1	4.5:1	#000000	#5A381F	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+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Alt Text Quality

All 27 images OK

PASS

All 27 images OK

17 decorative image(s) correctly marked

10 image(s) with good alt text

27 images 10 good alt text 17 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 9 controls labeled

PASS

All 9 controls labeled

9 control(s) properly labeled

9 controls

9 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#job	text	Keyword	for/id
#location	text	Location	for/id
#ot-group-id-BG53	checkbox	Performance	for/id
#ot-group-id-BG54	checkbox	Advertising	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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "vendor-search-handler" should use type="search" (currently type="text")

Field name "vendor-search-handler" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

9 form control(s) checked, no input-semantic issues

PASS

9 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

16 explicit tabindex attribute(s) checked, no anti-patterns

PASS

16 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Lighthouse Accessibility Audits

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

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
Join Our Team `section.one_column > div.container > p.cta > a`
Learn about our story `section.three_column_feature_card_teaser > div.container > p.text-center > a.txt-green`
To Know Us is to Love Us! `main#main > section.four_column_list_no_background_image > div.container > h2`
Learn more `ul.no-bullets > li.g-li1 > p > a.no-underline`
Learn more `ul.no-bullets > li.g-li2 > p > a.no-underline`
Learn more `ul.no-bullets > li.g-li3 > p > a.no-underline`
Search jobs `ul.no-bullets > li.g-li4 > p.cta > a`
View Video Transcript `div.col-md-7 > p > strong > a.txt-green`
CORPORATE SITES `div.container-fluid > div#footer-toprow > div#footer-corporate > h2.txt-uppercase`
CAREER SITES `div.container-fluid > div#footer-toprow > div#footer-career > h2.txt-uppercase`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main#main > section.video_only > div.video > iframe#player_16_742428834_1408101617 `main#main > section.video_only > div.video > iframe#player_16_742428834_1408101617`

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
header > div#secondary-nav > div.search > a `header > div#secondary-nav > div.search > a`

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

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

●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

●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

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

●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

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

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