Skip to content
https://sltrib.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 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
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 footer

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
Heading Hierarchy
Action
60 headings, 1 skip(s)
FIX
60 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 One of Park City Mountain’s last free parking areas is going away next season
  • H3 She was a false prophet’s wife. Now she’s reclaiming her life after years of control and abuse.
  • H3 Trump admin helps Utah steer clear of worse air quality status — but not because the air got better
  • H3 He was a snowboarding outsider who brought the sport to a ski resort near you — and to the Olympics
  • H3 Gordon Monson: A Vegas player tells Utah’s Logan Cooley, ‘I’m gonna ... kill you.’ But it’s the Golden Knight who might get hurt.
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 News
  • H3 ‘It’s never been this bad’: How Utahns are coping with the topsy-turvy economy
  • H3 She was a false prophet’s wife. Now she’s reclaiming her life after years of control and abuse.
  • H3 Incumbent GOP Salt Lake County Council member loses at convention, ending hopes for reelection
  • H2 Sports
  • H3 Real Salt Lake se prepara para Lionel Messi, agregando 1,000 asientos adicionales.
  • H3 Gordon Monson: A Vegas player tells Utah’s Logan Cooley, ‘I’m gonna ... kill you.’ But it’s the Golden Knight who might get hurt.
  • H3 Soccer star Lionel Messi is coming to Utah this week. Some fans are using it to pay off their honeymoon.
  • H2 THE LATEST
  • H2 Thank You to our Supporters:
  • H2 POLITICS
  • H3 Buzz of the Week: Vehicle camping in SLC: What’s the right approach?
  • H3 Ben McAdams leads fundraising race for Utah’s new, blue congressional district by nearly $1M
  • H3 ‘I was disturbed’: Two young Democrats respond to Nate Blouin’s crude posts
  • H3 Sign up for the Daily Buzz Newsletter
  • H2 Opinion
  • H3 Letter: Utah’s dual language immersion programs are being undermined
  • H3 Letter: Communities nationwide are fighting ICE warehouses. We should fight, too.
  • H3 Voices: Utah can’t wait 20 years for clean energy. If you care about winters in Utah, it’s time to speak up.
  • H3 Get the Inside Voices Newsletter
  • H2 Sponsored Stories
  • H3 How this award-winning photographer reveals the beauty of the microscopic world
  • H3 Planning your financial future together
  • H3 I do… plan to change my tax filing status
  • H3 Receive Top Stories Email Notifications
  • H2 Religion
  • H3 Open house is set for LDS temple that emerged during a dustup over treasured murals
  • H3 Supreme Court’s rejection of a final major case shuts the door on LDS tithing lawsuits — or does it?
  • H3 LDS Church announces new names for its Young Women groups
  • H2 Culture
  • H3 For this Utahn searching for ‘Love on the Spectrum,’ life is about making your own fairy tale
  • H3 Alan Osmond, oldest of the singing siblings and co-founder of Stadium of Fire, dies
  • H3 A new bar brings the Himalayas to the foot of Big Cottonwood Canyon
  • H2 Support Utah’s source for local news
  • H2 Bagley
  • H3 'Bagley Cartoon: Pope and Dope'
  • H3 'Bagley Cartoon: Word Made Litigious'
  • H3 'Bagley Cartoon: Legacy'
  • H3 'This week from Bagley: Commencement speakers, Vance and the pope, Trump’s dire strait, measles in Utah, MAGA blasphemy'
  • H3 'Bagley Cartoon: Fair and Balanced'
  • H3 'Bagley Cartoon: Red State Blues'
  • H3 'Bagley Cartoon: Pope and Dope'
  • H3 'Bagley Cartoon: Word Made Litigious'
  • H3 'Bagley Cartoon: Legacy'
  • H3 'This week from Bagley: Commencement speakers, Vance and the pope, Trump’s dire strait, measles in Utah, MAGA blasphemy'
  • H3 'Bagley Cartoon: Fair and Balanced'
  • H3 'Bagley Cartoon: Red State Blues'
  • H3 'Bagley Cartoon: Pope and Dope'
  • H5 CONNECT skipped
  • H5 SUBSCRIPTIONS
  • H5 ABOUT US
  • H5 MORE

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

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

F
Alt Text Quality
Action
4 of 77 images have issues
FIX
4 of 77 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
9 image(s) with alt text over 125 characters
Info::
64 image(s) with good alt text
77 images 64 good alt text 4 missing
IssueCount
missing4 image(s)
too long9 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name 192×192 icon 512×512 icon Start URL Display Mode standalone
Display Mode standalone
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.
Got: #ffffff
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
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
4 of 12 controls have issues
REVIEW
4 of 12 controls have issues
Critical::
4 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">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-1">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-2">; <input type="checkbox" name="queryly_toggle" id="queryly_toggle">
Info::
8 control(s) properly labeled
12 controls
8 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#osano-cm-dialog-toggle--category_STORAGEcheckboxnone
#osano-cm-dialog-toggle--category_MARKETINGcheckboxnone
#osano-cm-dialog-toggle--category_PERSONALIZATIONcheckboxnone
#osano-cm-dialog-toggle--category_ANALYTICScheckboxnone
#email-POLITICSemailEmail Addressfor/id
#email-OpinionemailEmail Addressfor/id
#email-Sponsored StoriesemailEmail Addressfor/id
#queryly_querysearchSearcharia-label
#g-recaptcha-responsetextarea(none)none
#g-recaptcha-response-2textarea(none)none
#queryly_togglecheckbox(none)none
#g-recaptcha-response-1textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-1">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-2">; <input type="checkbox" name="queryly_toggle" id="queryly_toggle">

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
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page Not Found - The Salt Lake Tribune Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 25 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
Save div.osano-cm-window > div#c10afaf3-9280-472e-8e03-d83a1944c7e8 > div.osano-cm-dialog__buttons > button.osano-cm-save
Accept All div.osano-cm-window > div#c10afaf3-9280-472e-8e03-d83a1944c7e8 > div.osano-cm-dialog__buttons > button.osano-cm-accept-all
Reject Non-Essential div.osano-cm-window > div#c10afaf3-9280-472e-8e03-d83a1944c7e8 > div.osano-cm-dialog__buttons > button.osano-cm-denyAll
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of … div.trib-newsletter > div.trib-newsletter__content > form.trib-newsletter__form > p.recaptcha-attribution
Privacy Policy div.trib-newsletter__content > form.trib-newsletter__form > p.recaptcha-attribution > a
Terms of Service div.trib-newsletter__content > form.trib-newsletter__form > p.recaptcha-attribution > a
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of … div.trib-newsletter > div.trib-newsletter__content > form.trib-newsletter__form > p.recaptcha-attribution
Privacy Policy div.trib-newsletter__content > form.trib-newsletter__form > p.recaptcha-attribution > a
Terms of Service div.trib-newsletter__content > form.trib-newsletter__form > p.recaptcha-attribution > a
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of … div.trib-newsletter > div.trib-newsletter__content > form.trib-newsletter__form > p.recaptcha-attribution
Privacy Policy div.trib-newsletter__content > form.trib-newsletter__form > p.recaptcha-attribution > a
Terms of Service div.trib-newsletter__content > form.trib-newsletter__form > p.recaptcha-attribution > a

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
body > iframe body > iframe

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
twitter-logo div > div.bagley-item > div.bagley-share > a.soc-med-item

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

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
Storage Preferences div#c10afaf3-9280-472e-8e03-d83a1944c7e8 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link
Third Parties div#c10afaf3-9280-472e-8e03-d83a1944c7e8 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link

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
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
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
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.
`[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
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.
Elements with visible text labels have matching accessible names.
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+
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 News19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Sports19.77:13.0:1
#000000
#F8F8F8
Pass
h2 THE LATEST19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Thank You to our Sup…17.64:13.0:1
#121212
#F8F8F8
Pass
h2 POLITICS19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Opinion19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Sponsored Stories19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Religion19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Culture19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Support Utah’s sou…19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Bagley19.77:13.0:1
#000000
#F8F8F8
Pass
h3 One of Park City Mou…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 She was a false prop…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Trump admin helps Ut…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 He was a snowboardin…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Gordon Monson: A Veg…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 ‘It’s never been…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 She was a false prop…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Incumbent GOP Salt L…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Real Salt Lake se pr…19.77:13.0:1
#000000
#F8F8F8
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