Skip to content
https://laist.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
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::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 4 <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.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) 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 (missing!) 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

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

B
Heading Hierarchy
19 headings
REVIEW
19 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Hey, LA listener!
  • H4 Patients in ICE custody
  • H5 CA lawmakers seek protections for patients
  • H4 Masked ICE agents
  • H5 Appeals court strikes down CA ban on masked agents
  • H4 OC's 'voting dog'
  • H5 Woman pleads guilty, faces jail time for stunt
  • H4 UC admission
  • H5 How more CA students to top UCs impacts taxpayers
  • H4 Wildlife crossing
  • H5 101 Freeway wildlife crossing to open this winter
  • H2 More news
  • H3 Want these headlines in your inbox?
  • H3 Local news needs you!
  • H3 Go Fact Yourself LIVE with Meaghan Rath and Hrishikesh Hirway
  • H3 CicLAvia—West LA
  • H3 Night at the Library: A Century of Light
  • H3 Wild Card with Rachel Martin LIVE
  • H3 Brains On Universe Presents…..Puberty! (The podcast)

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

B
Form Accessibility
2 of 17 controls have issues
REVIEW
2 of 17 controls have issues
Critical::
2 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">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100001">
Info::
15 control(s) properly labeled
17 controls
15 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#gsc-i-id1textbuscararia-label
Email_Addressemailnone
#monthly-anyh313whfrradioMonthlyfor/id
#one-time-anyh313whfrradioOne timefor/id
#10-anyh313whfrradionone
#15-anyh313whfrradionone
#30-anyh313whfrradionone
#custom-recurs-anyh313whfrradionone
amounttextnone
#120-anyh313whfrradionone
#180-anyh313whfrradionone
#360-anyh313whfrradionone
#custom-recurs-anyh313whfrradionone
amounttextnone
Email_Addressemailnone
#g-recaptcha-response-100000textarea(none)none
#g-recaptcha-response-100001textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100001">

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

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 404 - Page Not Found | LAist ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 25 passed
REVIEW
85

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
tbody > tr > td.gsc-search-button > button.gsc-search-button tbody > tr > td.gsc-search-button > button.gsc-search-button

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Patients in ICE custody CA lawmakers seek protections for patients 6 minutes ag… div.BriefListCarousel-container > ps-list-carousel.BriefListCarousel > div.BriefListCarousel-items-container > ul.BriefListCarousel-items
SAT, APR 25 Go Fact Yourself LIVE with Meaghan Rath and Hrishikesh Hirway On A… main.HomePage-main > ps-list-carousel.EventList-Carousel > div.EventList-Carousel-container > ul.EventList-Carousel-items

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Patients in ICE custody CA lawmakers seek protections for patients 6 minutes ago ul.BriefListCarousel-items > div.flickity-viewport > div.flickity-slider > li.BriefListCarousel-items-item
SAT, APR 25 Go Fact Yourself LIVE with Meaghan Rath and Hrishikesh Hirway On A… ul.EventList-Carousel-items > div.flickity-viewport > div.flickity-slider > li.EventList-Carousel-items-item

These are opportunities to improve the experience of reading tabular or list data using 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
LOGIN div.Page-header-hamburger-menu-wrapper > ps-login-module.LoginModule > div.LoginModule-login-button > button.ButtonAltB
LOGIN ps-login-module.LoginModule > div.LoginModule-login-button > button.ButtonAltB > a
DONATE div.Page-header-content > div.Page-header-content-inner > div.Page-header-top-bar > button.Page-header-donate-button
DONATE div.Page-header-content-inner > div.Page-header-top-bar > button.Page-header-donate-button > a.Link
LEARN MORE ps-video-carousel-slide.VideoModuleCarousel-video > div.VideoModuleCarousel-video-cta > button.EventPromo-Carousel-cta > a.Link
LEARN MORE ps-promo.EventPromo-Carousel > div.EventPromo-Carousel-contents > button.EventPromo-Carousel-cta > a.Link

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
LISTEN div.Page-header-content > div.Page-header-content-inner > div.Page-header-top-bar > button.Page-header-play-stream
Patients in ICE custody CA lawmakers seek protections for patients li.BriefListCarousel-items-item > ps-promo.BriefPromoCarousel > div.BriefPromoCarousel-content > a.Link
○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
●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.
●Links have a discernible name
●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
●ARIA IDs are unique
●Identical links have the same purpose.
○`[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
○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.
○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
Alt Text Quality
1 of 66 images have issues
PASS
1 of 66 images have issues
Warning::
1 image(s) with filename as alt text
Info::
27 image(s) with alt text over 125 characters
Info::
4 decorative image(s) correctly marked
Info::
34 image(s) with good alt text
66 images 34 good alt text 4 decorative 1 generic
IssueCount
filename1 image(s)
too long27 image(s)
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 More news21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hey, LA listener!21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Want these headlines…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Local news needs you…21.00:13.0:1
#000000
#FFFFFF
Pass
title Local and national n…21.00:14.5:1
#000000
#FFFFFF
Pass
div Sponsored message13.90:14.5:1
#000000
#FECC32
Pass
div Logged in as13.90:14.5:1
#000000
#FECC32
Pass
a Login13.90:14.5:1
#000000
#FECC33
Pass
button Logout21.00:14.5:1
#000000
#FFFFFF
Pass
a The Brief15.93:14.5:1
#000000
#FDD6E5
Pass
span News15.96:14.5:1
#000000
#FDD7DF
Pass
a Housing & Homelessne…16.04:14.5:1
#000000
#FED8D9
Pass
a Arts & Entertainment15.97:14.5:1
#000000
#FED8D2
Pass
a Food16.39:14.5:1
#000000
#FEDCD3
Pass
a Orange County News16.96:14.5:1
#000000
#FEE1D6
Pass
a Climate & Environmen…17.40:14.5:1
#000000
#FDE5DA
Pass
a Civics & Democracy17.99:14.5:1
#000000
#FDEADD
Pass
a Education18.56:14.5:1
#000000
#FCEFE0
Pass
a Transportation & Mob…19.07:14.5:1
#000000
#FCF3E3
Pass
a Explore LA19.42:14.5:1
#000000
#FBF6E5
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