Skip to content
https://losangelesapparel.net

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
8
REVIEW
2
PASS
14
INFO
0
Checks
24
14 PASS 2 REVIEW 8 FIX
D
Iframe Accessibility
Action
9/15 iframe(s) missing title; 0 placeholder(s)
FIX
9/15 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://losangelesapparel.net/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/cu…")
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.
Warning::
<iframe> missing title attribute (src="https://losangelesapparel.net/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/cu…")
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.
Warning::
<iframe> missing title attribute (src="https://losangelesapparel.net/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/cu…")
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.
Warning::
<iframe> missing title attribute (src="https://losangelesapparel.net/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/cu…")
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.
Warning::
<iframe> missing title attribute (src="https://losangelesapparel.net/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/cu…")
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.
Warning::
<iframe> missing title attribute (src="https://losangelesapparel.net/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/cu…")
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.
Warning::
<iframe> missing title attribute (src="https://losangelesapparel.net/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/cu…")
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.
Warning::
<iframe> missing title attribute (src="")
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.
Warning::
<iframe> missing title attribute (src="https://tr.snapchat.com/cm/i?pid=cd332295-32bb-490b-825a-110b132c6ec3&u_scsid=7…")
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.
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found – Los Angeles Apparel ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
Theme color only
FIX
Theme color only
Info::
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.
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 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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Item added to your cart
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Best Sellers
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 HOODIES
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Just For You
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 CATEGORY HIGHLIGHTS
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 That's Los Angeles
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Help
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ordering
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About Us
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Social Links
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Subscribe to our emails
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Download Mobile App
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Country/region
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Our City Inspires Us
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Videos
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
19px · bottom of viewport
title Los Angeles Apparel
1.96:1
#000000
on
#3E3E3E
needs 4.5:1 (normal text)
16px · top of page (header area)
a My Wishlist
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Press Alt+1 for screen-reader mode, Alt+…
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Accessibility Screen-Reader Guide, Feedb…
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Bag
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Item added to your c…2.03:13.0:1
#000000
#404040
Fail
h2 Best Sellers2.03:13.0:1
#000000
#404040
Fail
h2 HOODIES2.03:13.0:1
#000000
#404040
Fail
h2 Just For You2.03:13.0:1
#000000
#404040
Fail
h2 CATEGORY HIGHLIGHTS2.03:13.0:1
#000000
#404040
Fail
h2 That's Los Angeles2.03:13.0:1
#000000
#404040
Fail
h2 Help2.03:13.0:1
#000000
#404040
Fail
h2 Ordering2.03:13.0:1
#000000
#404040
Fail
h2 About Us2.03:13.0:1
#000000
#404040
Fail
h2 Social Links2.03:13.0:1
#000000
#404040
Fail
h2 Subscribe to our ema…2.03:13.0:1
#000000
#404040
Fail
h2 Download Mobile App2.03:13.0:1
#000000
#404040
Fail
h2 Country/region2.03:13.0:1
#000000
#404040
Fail
h3 Our City Inspires Us2.03:13.0:1
#000000
#404040
Fail
h3 Videos2.03:13.0:1
#000000
#404040
Fail
title Los Angeles Apparel1.96:14.5:1
#000000
#3E3E3E
Fail
a My Wishlist1.93:14.5:1
#000000
#3D3D3D
Fail
span Press Alt+1 for scre…1.93:14.5:1
#000000
#3D3D3D
Fail
a Accessibility Screen…1.93:14.5:1
#000000
#3D3D3D
Fail
span Bag1.93:14.5:1
#000000
#3D3D3D
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.

B
Lighthouse Accessibility Audits
Score 87/100 — 3 failing, 28 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#ajax-cart > div.ajax-cart__header > div.ajax-cart__navigation > button.ajax-cart-header__close div#ajax-cart > div.ajax-cart__header > div.ajax-cart__navigation > button.ajax-cart-header__close

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
sticky-header.header-wrapper > header.header > h1.header__heading > a.header__heading-link sticky-header.header-wrapper > header.header > h1.header__heading > a.header__heading-link
div.flickity-viewport > div.flickity-slider > div.carousel__cell > a.cell div.flickity-viewport > div.flickity-slider > div.carousel__cell > a.cell
main#MainContent > section#shopify-section-template--20623032156339__image_banner > div#Banner-template--20623032156339__image_banner > a.banner__media main#MainContent > section#shopify-section-template--20623032156339__image_banner > div#Banner-template--20623032156339__image_banner > a.banner__media
main#MainContent > section#shopify-section-template--20623032156339__163667178124a23ae7 > div#Banner-template--20623032156339__163667178124a23ae7 > a.banner__media main#MainContent > section#shopify-section-template--20623032156339__163667178124a23ae7 > div#Banner-template--20623032156339__163667178124a23ae7 > a.banner__media
li.grid__item > div.multicolumn-card > div.multicolumn-card__image-wrapper--full-width > a li.grid__item > div.multicolumn-card > div.multicolumn-card__image-wrapper--full-width > a
li.grid__item > div.multicolumn-card > div.multicolumn-card__image-wrapper--full-width > a li.grid__item > div.multicolumn-card > div.multicolumn-card__image-wrapper--full-width > 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.

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

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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●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
●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
●ARIA IDs are unique
●All heading elements contain content.
●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
○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
○`[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
○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>`.
○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.
A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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+
Heading Hierarchy
38 headings
PASS
38 headings
Info::
Single H1 present
  • H1 .st0_logo{fill:none;stroke:#2D3237;stroke-miterlimit:10;} .st1_logo{fill:#2D3237;}
  • H2 Item added to your cart
  • H2 Best Sellers
  • H3 43021GDGarment Dye Cap Sleeve Baby Rib T-Shirt
  • H3 RHR318GDHeavy Rib Spaghetti Mini Dress
  • H3 8320GDGarment Dye Spaghetti Tank Camisole
  • H3 8300GDGarment Dye Yoga Legging
  • H3 HF09Heavy Fleece Hoodie (Piece Dye)
  • H3 HF05Heavy Fleece Wide Leg Sweatpants (Piece Dye)
  • H3 FF01Poly-Cotton Crew Neck T-Shirt
  • H3 43044Baby Rib 3/4 Sleeve Boatneck Top
  • H3 8391Spaghetti Bralette
  • H3 43013SETContrast Baby Rib Thong 7-Pack
  • H2 HOODIES
  • H2 Women's
  • H2 Men's
  • H2 Just For You
  • H3 6.5oz Garment Dye Crew Neck T-Shirt
  • H3 43044Baby Rib 3/4 Sleeve Boatneck Top
  • H3 HF09Heavy Fleece Hoodie (Garment Dye)
  • H3 Thigh High Sock
  • H3 43053Baby Rib Long Sleeve Raglan
  • H3 RNS112Micro Mesh Bra Bodysuit
  • H3 RNS91Micro Mesh Spaghetti Bralette
  • H3 HF16Heavy Fleece Cropped Zip-Up Hoodie (Garment Dye)
  • H3 8300GDGarment Dye Yoga Legging
  • H3 CC356Cheesecloth Fitted V-Neck T-Shirt
  • H2 CATEGORY HIGHLIGHTS
  • H3 Our City Inspires Us
  • H3 Videos
  • H2 That's Los Angeles
  • H2 Help
  • H2 Ordering
  • H2 About Us
  • H2 Social Links
  • H2 Subscribe to our emails
  • H2 Download Mobile App
  • H2 Country/region
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
2 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: 2 all-caps heading(s)
A+
Alt Text Quality
All 180 images OK
PASS
All 180 images OK
Info::
103 decorative image(s) correctly marked
Info::
77 image(s) with good alt text
180 images 77 good alt text 103 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 5 controls have issues
PASS
1 of 5 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 type="submit">
Info::
4 control(s) properly labeled
5 controls
4 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#Search-In-Modal-1searchSearchfor/id
#Search-In-ModalsearchSearchfor/id
#NewsletterForm--footeremailEmailfor/id
qsearchSearcharia-label
inputsubmit(none)none

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

<input type="submit">

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

A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A
Tabindex Anti-Patterns
0 positive, 2 -1-on-focusable
PASS
0 positive, 2 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input id="Mobile-Search-Bar-AB">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 18 visible text node(s) render at >= 12 CSS pixels
PASS
All 18 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback