Skip to content
https://lg.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
13 landmarks
FIX
13 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No contentinfo (footer) landmark
Warning::
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
BANNER header MAIN (missing!) CONTENTINFO (missing!)

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

D
Alt Text Quality
Action
6 of 268 images have issues
FIX
6 of 268 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
76 image(s) with alt text over 125 characters
Info::
35 decorative image(s) correctly marked
Info::
151 image(s) with good alt text
268 images 151 good alt text 35 decorative 6 missing
IssueCount
missing6 image(s)
too long76 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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input>
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="textfield" id=":r0:">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#:r0:text(Search LG)placeholder only
inputinput(none)none

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

<input>

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.

<input type="text" name="textfield" id=":r0:">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title LG Electronics & Home Appliances | Shop Now | LG USA ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
13 icon(s) detected
REVIEW
13 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 87/100 — 5 failing, 30 passed
REVIEW
87

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
$200 Off Soundbar div.optimizely-product-recs-template__card-header > div.optimizely-product-recs-template__promo-tags > div.optimizely-product-recs-template__promo-tag > span

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
div.MuiGrid-root > div.MuiBox-root > p > a#terms
div.MuiBox-root > ul.MuiList-root > li.MuiListItem-root > a.MuiTypography-root div.MuiBox-root > ul.MuiList-root > li.MuiListItem-root > a.MuiTypography-root

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta
head > meta head > meta

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
/LGUSSupport div.MuiBox-root > ul.MuiList-root > li.MuiListItem-root > a.MuiTypography-root
@lgussupport div.MuiBox-root > ul.MuiList-root > li.MuiListItem-root > a.MuiTypography-root

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
0 div.MuiBox-root > div.MuiBox-root > div > button#nav-toggle-1
○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
●Form elements have associated labels
●`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
●`<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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●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
○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.
○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.
○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.
A+
Heading Hierarchy
41 headings
PASS
41 headings
Info::
Single H1 present
  • H2 Performance You Can See.Quality You Can Trust.
  • H2 Save up to 35% on select appliances and up to $2,300 on utility bills
  • H2 Greatness at its thinnest: This is Wallpaper TV
  • H2 Save 30-53% on top home appliances
  • H2 Power your setup with savings on select Monitors
  • H2 Performance You Can See.Quality You Can Trust.
  • H2 Save up to 35% on select appliances and up to $2,300 on utility bills
  • H2 Greatness at its thinnest: This is Wallpaper TV
  • H2 Save 30-53% on top home appliances
  • H2 Power your setup with savings on select Monitors
  • H2 Performance You Can See.Quality You Can Trust.
  • H1 Shop top appliances and electronics
  • H2 Discover LG Deals
  • H2 Top Deals
  • H2 Kitchen
  • H2 Laundry
  • H2 TV & Audio
  • H2 Laptops & Monitors
  • H2 Vacuum & A/C
  • H2 Shop with an LG Expert: FREE advice + deals on appliances + tech
  • H2 Recommended for you
  • H2 Home appliances you can count on
  • H2 LG Reliability
  • H2 Kitchen
  • H2 Laundry
  • H2 Energy Innovation
  • H2 Other Appliances
  • H2 What LG Customers Say
  • H2 Take your home entertainment to new heights
  • H2 TVs
  • H2 Audio
  • H2 Lifestyle Screens
  • H2 webOS
  • H2 What LG Customers Say
  • H2 Work hard, play more with our top monitors and laptops
  • H2 Monitors
  • H2 Laptops
  • H2 What LG Customers Say
  • H2 Explore the benefits of shopping LG.com
  • H2 Life's Good with LG
  • H2 For LG Owners
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Top Deals14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Kitchen14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Laundry14.72:13.0:1
#000000
#DAD8D1
Pass
h2 TV & Audio14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Laptops & Monitors14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Vacuum & A/C14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Recommended for you14.72:13.0:1
#000000
#DAD8D1
Pass
h2 LG Reliability14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Kitchen14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Laundry14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Energy Innovation14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Other Appliances14.72:13.0:1
#000000
#DAD8D1
Pass
h2 What LG Customers Sa…14.72:13.0:1
#000000
#DAD8D1
Pass
h2 TVs14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Audio14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Lifestyle Screens14.72:13.0:1
#000000
#DAD8D1
Pass
h2 webOS14.72:13.0:1
#000000
#DAD8D1
Pass
h2 What LG Customers Sa…14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Monitors14.72:13.0:1
#000000
#DAD8D1
Pass
h2 Laptops14.72:13.0:1
#000000
#DAD8D1
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.

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

Send Feedback