Skip to content
https://ksl.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Heading Hierarchy
Action
133 headings, 26 skip(s)
FIX
133 headings, 26 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Utah Breaking News, Sports and Weather
  • H2 Elizabeth Smart opens up about new hobby: bodybuilding competitions
  • H2 Former kidnapping victim turned advocate Elizabeth Smart just opened up online about a new chapter in her life: bodybuilding competitions.
  • H4 Arianne Brown, KSL 18 skipped
  • H2 Hurricane secures iconic 'H' hill for public use
  • H4 Josh Furlong, KSL skipped
  • H2 The Utah Checkdown podcast: Spring camp recap + NFL draft weekend preview
  • H4 Emily Ashcraft, KSL 9 skipped
  • H2 Jury finds American Fork woman guilty of murdering son-in-law in conspiracy case
  • H3 Latest News & Features
  • H2 Have You Seen This? Frodo selling the ring to Pawn Stars is a spectacular AI mashup
  • H4 Emily Ashcraft, KSL  |  Posted April 22 - 3:42 p.m.  |  Save Story skipped
  • H5 One man decided to use AI create a mashup video where Frodo tries to sell the one ring to Pawn Stars' Rick Harrison, and he does it so well.
  • H3 SPONSORED
  • H2 Utah clinic offers lower cost heart scans without the wait or a doctor's order
  • H4 EkoCardia  |  Posted April 22 - 3:00 p.m.  |  Save Story skipped
  • H5 Built around accessibility, quality, and expert interpretation, EkoCardia provides echocardiograms in a modern outpatient setting with transparent pricing, prompt scheduling, and no referral required.
  • H2 Meet the granddaughter of Irene Corbett, Utah's only known Titanic passenger
  • H4 Ashley Moser, KSL  |  Posted April 22 - 2:30 p.m.  |  Save Story skipped
  • H5 More than a century after the Titanic sank, Irene Corbett's namesake shares her family's story, now featured inside the traveling Titanic exhibition in Utah.
  • H2 Ping-pong robot Ace makes history by beating top-level human players
  • H4 Will Dunham, Reuters  |  Updated April 22 - 2:00 p.m.  |  Save Story skipped
  • H5 An autonomous robot ping-pong player dubbed Ace has achieved a milestone for AI and robotics in Tokyo by competing against and sometimes defeating top-level human players at table tennis.
  • H2 Salt Lake man stabbed dog during fight with girlfriend, police say
  • H4 Pat Reavy, KSL  |  Posted April 22 - 1:30 p.m.  |  Save Story skipped
  • H5 A Salt Lake man was arrested Tuesday and accused of stabbing his dog multiple times after getting into an argument with his girlfriend.
  • H2 Pentagon makes flu shot optional for troops, rescinding requirement
  • H4 Kaanita Iyer, CNN  |  Updated April 22 - 12:45 p.m.  |  Save Story skipped
  • H5 Defense Secretary Pete Hegseth announced Tuesday that the military will no longer require the annual flu vaccine for troops.
  • H2 When's the best time to list a home for sale in the U.S.?
  • H4 Lisa Riley Roche, Deseret News  |  Posted April 22 - 12:00 p.m.  |  Save Story skipped
  • H5 Thinking of selling your home? You might want to get it on the market quickly.
  • H2 Trump administration nears deal to rescue Spirit Airlines, WSJ reports
  • H4 Reuters  |  Updated April 22 - 11:38 a.m.  |  Save Story skipped
  • H5 The Trump administration has neared a deal to rescue embattled low-cost carrier Spirit Airlines, ​the Wall Street Journal reported on Wednesday, citing people familiar with the matter.
  • H3 SPONSORED
  • H2 What to know before becoming a foster parent for refugee youth in Utah
  • H4 Catholic Community Services  |  Posted April 22 - 11:30 a.m.  |  Save Story skipped
  • H5 For those considering stepping in, understanding how the process works can help answer some of the most common concerns.
  • H2 Davis County crisis center hosting 5K to raise awareness of sexual violence
  • H4 Curtis Booker, KSL  |  Posted April 22 - 11:15 a.m.  |  Save Story skipped
  • H5 Safe Harbor Crisis Center will host its annual "Walk In Their Shoes" 5K on Friday in Kaysville to raise awareness of sexual violence.
  • H2 Earth Day is here — how the DWR says you can celebrate by helping wildlife
  • H4 Hayden Madson, Deseret News  |  Posted April 22 - 10:30 a.m.  |  Save Story skipped
  • H5 On Earth Day, many Utah groups will be gathering with a goal to make a difference in protecting Earth's natural resources.
  • H2 Hurricane secures iconic 'H' hill for public use
  • H4 Arianne Brown, KSL  |  Posted April 22 - 10:02 a.m.  |  Save Story skipped
  • H5 The city of Hurricane in southern Utah has recently entered into a deal to purchase the "H" from private landowners.
  • H2 Virginians approve Democratic map targeting 4 Republican congressional seats
  • H4 Joseph Ax, Reuters  |  Updated April 22 - 9:31 a.m.  |  Save Story skipped
  • H5 Virginia voters on Tuesday approved a new Democratic-drawn congressional map that could flip four Republican House seats in November's midterm elections, media ​projected.
  • H2 New display explains Great Salt Lake's water situation, one marble at a time
  • H4 Carter Williams, KSL  |  Posted April 22 - 9:05 a.m.  |  Save Story skipped
  • H5 A new exhibit at the Salt Lake County Government Center in Salt Lake City explains the Great Salt Lake's water situation by using marbles.
  • H2 Iran fires on 3 ships in the Strait of Hormuz as US maintains blockade and diplomacy stalls
  • H4 Jon Gambrell and David Rising, Associated Press  |  Posted April 22 - 8:30 a.m.  |  Save Story skipped
  • H5 Iran has fired on three ships in the Strait of Hormuz and seized two of them.
  • H2 The Hat Trick: Guenther, Cooley shine as Mammoth steal Game 2 on the road to even series
  • H4 Cole Bagley, KSL  |  Posted April 22 - 8:24 a.m.  |  Save Story skipped
  • H5 Despite a sluggish start to Tuesday night's game in Vegas, the Utah Mammoth stole Game 2 as they utilized their wicked speed to burn the Knights defensively.
  • H2 Tough housing market: Some homeowners opt to remodel rather than buy
  • H4 Daniel Woodruff, KSL  |  Posted April 22 - 8:05 a.m.  |  Save Story skipped
  • H5 A Redfin study found that 43% of Americans chose to remodel their home in the last year, with another 33% saying they plan to do that sometime in the next year. Why?
  • H3 SPONSORED
  • H2 Organ donation saves lives at Intermountain Primary Children's Hospital: Caregiver shares her donor story
  • H4 Intermountain Health  |  Posted April 22 - 8:00 a.m.  |  Save Story skipped
  • H5 April is National Donate Life Month, a time to raise awareness about organ, eye and tissue donation, and to encourage organ donation registration.
  • H2 Juan Diego softball pitcher severely injured after line drive knocks out teeth
  • H4 Dan Rascon, KSL  |  Posted April 22 - 7:41 a.m.  |  Save Story skipped
  • H5 A painful and frightening injury has sidelined a key player on the Juan Diego High School girls softball team.
  • H2 Southern Poverty Law Center charged with fraud over use of paid informants
  • H4 Jana Winter, Julia Harte and Andrew Goudsward, Reuters  |  Updated April 22 - 7:18 a.m.  |  Save Story skipped
  • H5 The Trump administration obtained a criminal indictment on Tuesday charging the Southern Poverty Law Center, a civil rights group that tracks political ​extremists, with fraud.
  • H2 Deaths of several scientists in recent months sparks federal investigation
  • H4 Natasha Chen, Alex Stambaugh, Chris Boyette, CNN  |  Updated April 22 - 6:51 a.m.  |  Save Story skipped
  • H5 In recent months, the deaths of several acclaimed scientists connected to sensitive US nuclear and aerospace research have fueled speculation.
  • H2 Miss Inspiration pageant helps women with intellectual disabilities shine
  • H4 Mike Anderson, KSL  |  Posted April 22 - 6:15 a.m.  |  Save Story skipped
  • H5 Fifteen women with developmental and intellectual disabilities were given the chance to shine Tuesday night in the biannual Miss Inspiration pageant in Orem.
  • H2 Mammoth earn first playoff win in franchise history with 3-2 result over Vegas
  • H4 Jaxon Wynder, KSL  |  Posted April 21 - 11:37 p.m.  |  Save Story skipped
  • H5 Logan Cooley's third period goal propelled the Mammoth to a game two win over the Golden Knights as Dylan Guenther and Kailer Yamamoto each record two points in the win.
  • H3 Markets
  • H3 STAY IN THE KNOW
  • H3 Sports »
  • H2 The Utah Checkdown podcast: Spring camp recap + NFL draft weekend preview
  • H3 Features »
  • H2 Have You Seen This? Frodo selling the ring to Pawn Stars is a spectacular AI mashup
  • H3 Outdoors »
  • H2 Earth Day is here — how the DWR says you can celebrate by helping wildlife
  • H3 World »
  • H2 Meet the granddaughter of Irene Corbett, Utah's only known Titanic passenger
  • H3 U.S. »
  • H2 Meet the granddaughter of Irene Corbett, Utah's only known Titanic passenger
  • H3 Utah »
  • H2 Elizabeth Smart opens up about new hobby: bodybuilding competitions
  • H3 Voces de Utah »
  • H2 'Once in a lifetime' opportunity: Soccer star Messi in Utah for Inter Miami-Real Salt Lake game
  • H3 Business »
  • H2 US set to move to reclassify marijuana as early as Wednesday, Axios reports
  • H3 Politics »
  • H2 Rep. David Scott, a Georgia Democrat seeking his 13th term in Congress, dies at age 80
  • H2 We Care About Your Privacy
  • H3 We and our partners process data to provide:
  • H2 About Your Privacy
  • H3 Manage Consent Preferences
  • H4 Targeting Cookies
  • H4 Performance Cookies
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Store and/or access information on a device 813 partners can use this purpose
  • H4 Personalised advertising and content, advertising and content measurement, audience research and services development 962 partners can use this purpose
  • H5 Use limited data to select advertising 759 partners can use this purpose
  • H5 Create profiles for personalised advertising 619 partners can use this purpose
  • H5 Use profiles to select personalised advertising 621 partners can use this purpose
  • H5 Create profiles to personalise content 263 partners can use this purpose
  • H5 Use profiles to select personalised content 237 partners can use this purpose
  • H5 Measure advertising performance 879 partners can use this purpose
  • H5 Measure content performance 405 partners can use this purpose
  • H5 Understand audiences through statistics or combinations of data from different sources 560 partners can use this purpose
  • H5 Develop and improve services 661 partners can use this purpose
  • H5 Use limited data to select content 178 partners can use this purpose
  • H4 Use precise geolocation data 291 partners can use this special feature
  • H4 Actively scan device characteristics for identification 159 partners can use this special feature
  • H4 Ensure security, prevent and detect fraud, and fix errors 628 partners can use this special purpose
  • H4 Deliver and present advertising and content 621 partners can use this special purpose
  • H4 Match and combine data from other data sources 444 partners can use this feature
  • H4 Link different devices 372 partners can use this feature
  • H4 Identify devices based on information transmitted automatically 578 partners can use this feature
  • H4 Save and communicate privacy choices 478 partners can use this special purpose
  • H3 Cookie List
  • H2 Why are you reporting this ad?
  • H2 Additional Information

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

D
Form Accessibility
Action
4 of 30 controls have issues
FIX
4 of 30 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="image">; <input type="text" name="s">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="email" id="email">; <textarea name="user_feedback" id="adl-user-feedback">
Info::
26 control(s) properly labeled
30 controls
26 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-IAB2V2_1checkboxStore and/or access information on a devicefor/id
#ot-group-id-V2STACK42checkboxPersonalised advertising and content, advertising and content measurement, audience research and services developmentfor/id
#ot-sub-group-id-IAB2V2_2checkboxUse limited data to select advertisingaria-label
#ot-sub-group-id-IAB2V2_3checkboxCreate profiles for personalised advertisingaria-label
#ot-sub-group-id-IAB2V2_4checkboxUse profiles to select personalised advertisingaria-label
#ot-sub-group-id-IAB2V2_5checkboxCreate profiles to personalise contentaria-label
#ot-sub-group-id-IAB2V2_6checkboxUse profiles to select personalised contentaria-label
#ot-sub-group-id-IAB2V2_7checkboxMeasure advertising performancearia-label
#ot-sub-group-id-IAB2V2_8checkboxMeasure content performancearia-label
#ot-sub-group-id-IAB2V2_9checkboxUnderstand audiences through statistics or combinations of data from different sourcesaria-label
#ot-sub-group-id-IAB2V2_10checkboxDevelop and improve servicesaria-label
#ot-sub-group-id-IAB2V2_11checkboxUse limited data to select contentaria-label
#ot-group-id-ISF2V2_1checkboxUse precise geolocation datafor/id
#ot-group-id-ISF2V2_2checkboxActively scan device characteristics for identificationfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
categoryradionone
categoryradionone
categoryradionone
categoryradionone
#emailtext(Enter your email)placeholder only
#adl-user-feedbacktextarea(What does the ad say, who is the advertiser, what does the ad look like?)placeholder only
inputimage(none)none
stext(none)none

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

<input type="image">; <input type="text" name="s">

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="email" id="email">; <textarea name="user_feedback" id="adl-user-feedback">

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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-o08zpu
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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: #0b162f
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
Info::
Hamburger menu detected (responsive design)
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)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "main menu" 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

B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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 Present
Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: KSL News
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name KSL News 192×192 icon 512×512 icon Start URL Display Mode
Name KSL News Icons 2 icon(s)
B
Lighthouse Accessibility Audits
Score 84/100 — 6 failing, 25 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.

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
Sign In div.ksl-header-menu__inner > div.ksl-header-account > div.ksl-header-account__logged-out > a.ksl-header-account__login-button
MARKETPLACE div.ksl-header-menu__inner > div.ksl-header-mobile-links > div.ksl-header-nav-group > div.ksl-header-nav-group__head
Sign Me Up div.newsSignup > div.firstColumn > form.newsSignupForm > button.button
Create your own KSL.com news feed! body#body > div.InformationBubble__PointerBox-o92yog-0 > div.InformationBubble__BoxContent-o92yog-2 > p.Typography__variantProp-sc-5cwz35-0

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms of Use div.newsSignup > div.firstColumn > div.emailSignupMessage > a
Privacy Notice div.newsSignup > div.firstColumn > div.emailSignupMessage > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Arianne Brown, KSL 18 div.top_picks > div.pick_story > div.pick_story_meta > h4.short
Josh Furlong, KSL div.top_picks > div.pick_story > div.pick_story_meta > h4.short
Matt Gephardt and Sloan Schrage, KSL 86 div.top_picks > div.pick_story > div.pick_story_meta > h4.short
 April 22 - 3:42 p.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 3:00 p.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 2:30 p.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 2:00 p.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 1:30 p.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 12:45 p.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 12:00 p.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 11:38 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
 April 22 - 11:30 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 11:15 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 10:30 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 10:02 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 9:31 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 9:05 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 8:30 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 8:24 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
 April 22 - 8:05 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 8:00 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
 April 22 - 7:41 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 7:18 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 22 - 6:51 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
 April 22 - 6:15 a.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4
April 21 - 11:37 p.m.  |  Save Story div.firefox_fix > div.queue_story > div.headline > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.quotebox > form > div#stockInput > input div.quotebox > form > div#stockInput > input

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
18 div.pick_story > div.pick_story_meta > h4.short > a.comment-count
86 div.pick_story > div.pick_story_meta > h4.short > a.comment-count

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.

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
51° div.ksl-header__outer > div.ksl-header__inner > span > button.ksl-header-weather-toggle
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
`<input type="image">` elements have `[alt]` text
`[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
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.
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
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
`<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.
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
All 54 images OK
PASS
All 54 images OK
Info::
54 image(s) with good alt text
54 images 54 good alt text
All images have appropriate alt text.
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
h1 Utah Breaking News, …19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Elizabeth Smart open…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Former kidnapping vi…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 The Utah Checkdown p…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Have You Seen This? …19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Earth Day is here …19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Meet the granddaught…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Meet the granddaught…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Elizabeth Smart open…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 'Once in a lifetime'…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 US set to move to re…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Rep. David Scott, a …19.43:13.0:1
#000000
#F6F6F6
Pass
h2 We Care About Your P…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 About Your Privacy19.43:13.0:1
#000000
#F6F6F6
Pass
h2 Why are you reportin…10.53:13.0:1
#3A3A3A
#F6F6F6
Pass
h2 Additional Informati…10.53:13.0:1
#3A3A3A
#F6F6F6
Pass
h3 Latest News & Featur…19.43:13.0:1
#000000
#F6F6F6
Pass
h3 SPONSORED19.43:13.0:1
#000000
#F6F6F6
Pass
h3 SPONSORED19.43:13.0:1
#000000
#F6F6F6
Pass
h3 SPONSORED19.43:13.0:1
#000000
#F6F6F6
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