Skip to content
https://lacity.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
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 403 ✗Page Title Access Denied ✓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
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
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
6 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA 1 pass AA only
h1 Home
1.30:1
#000000
on
#212121
needs 3.0:1 (large text)
32px · bottom of viewport
h2 City of Los Angeles
1.30:1
#000000
on
#212121
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Quick Links
1.30:1
#000000
on
#212121
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connect With Us
1.30:1
#000000
on
#212121
needs 3.0:1 (large text)
24px · bottom of viewport
title Home | City of Los Angeles
1.41:1
#000000
on
#0F2940
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Home1.30:13.0:1
#000000
#212121
Fail
h2 City of Los Angeles1.30:13.0:1
#000000
#212121
Fail
h2 Quick Links1.30:13.0:1
#000000
#212121
Fail
h2 Connect With Us1.30:13.0:1
#000000
#212121
Fail
title Home | City of Los A…1.41:14.5:1
#000000
#0F2940
Fail
a Skip to main content5.09:14.5:1
#000000
#6F7F8C
Pass
p The Official Website…21.00:14.5:1
#000000
#FFFFFF
Pass
span Global Bar21.00:14.5:1
#000000
#FFFFFF
Pass
a City Services21.00:14.5:1
#000000
#FFFFFF
Pass
a City Directory21.00:14.5:1
#000000
#FFFFFF
Pass
span Search21.00:14.5:1
#000000
#FFFFFF
Pass
a RESIDENTS21.00:14.5:1
#000000
#FFFFFF
Pass
a BUSINESS21.00:14.5:1
#000000
#FFFFFF
Pass
a VISITORS21.00:14.5:1
#000000
#FFFFFF
Pass
a JOBS21.00:14.5:1
#000000
#FFFFFF
Pass
a GOVERNMENT21.00:14.5:1
#000000
#FFFFFF
Pass
span TRANSLATE21.00:14.5:1
#000000
#FFFFFF
Pass
span ACCESSIBILITY21.00:14.5:1
#000000
#FFFFFF
Pass
a SEARCH21.00:14.5:1
#000000
#FFFFFF
Pass
a RESIDENTS21.00:14.5:1
#000000
#FFFFFF
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 23 passed
REVIEW
84

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 2 3 4 5 6 7 8 9 div.view-content > div.slick > div#slick-c16266b9fd9 > ul.slick-dots
1 2 3 div.paragraph > div.slick > div#slick-37b77a661d4 > ul.slick-dots

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Search div.clearfix > p > a.px-3 > span.fa-solid

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Open this option div.clearfix > main#content > section.section > a#main-content

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of 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
Search div.content > div.clearfix > p > a.px-3

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
●`[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
●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
●Links have a discernible name
●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
●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
○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.
○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.
○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
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
4 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN ASIDE 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
5 headings
PASS
5 headings
Info::
Single H1 present
  • H1 Home
  • H2 News
  • H2 City of Los Angeles
  • H2 Quick Links
  • H2 Connect With Us
A+
Alt Text Quality
All 13 images OK
PASS
All 13 images OK
Info::
13 image(s) with good alt text
13 images 13 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 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 type="submit" id="edit-submit">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#edit-keyssearchSearchfor/id
#edit-submitsubmit(none)none

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

<input type="submit" id="edit-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+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/g/files/wph2451/files/css/css_iMBE_XQWVNdQbqEANtek1Rn2-m2w9jEQgAnvmYDl9Hw.css?delta=4&language=en&theme=lacity&include=eJyNUNFuwyAM_CESPgkZcFJWg5EN7djXj6VrNnUve7F85_PpdFB2pC3pxXrmpk2gGji5jUuDOypnXDZBfDnpL7wTe6BF26BUduMJPoYlhnigp7fzIJL4j_r1XjiiCVeMqbE4CIElJi723NZNZgAs0UwCbeBcueCMtL56LUvG0v8pc4Gp56IPeZRegVZ4g3dDEFIb38EnGtybi0kD31CGna7z1VQQ2KfpRZ_PP8zaS-2eZlkYjVIKV-tB0WivKEeH5-a-ikEXcYNOzejQhvmhviW8qz3mmjl2wk9_erFx
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/g/files/wph2451/files/css/css_iMBE_XQWVNdQbqEANtek1Rn2-m2w9jEQgAnvmYDl9Hw.css?delta=4&language=en&theme=lacity&include=eJyNUNFuwyAM_CESPgkZcFJWg5EN7djXj6VrNnUve7F85_PpdFB2pC3pxXrmpk2gGji5jUuDOypnXDZBfDnpL7wTe6BF26BUduMJPoYlhnigp7fzIJL4j_r1XjiiCVeMqbE4CIElJi723NZNZgAs0UwCbeBcueCMtL56LUvG0v8pc4Gp56IPeZRegVZ4g3dDEFIb38EnGtybi0kD31CGna7z1VQQ2KfpRZ_PP8zaS-2eZlkYjVIKV-tB0WivKEeH5-a-ikEXcYNOzejQhvmhviW8qz3mmjl2wk9_erFx ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback