Accessibility

F

Heading Hierarchy

Action

241 headings, 26 skip(s)

FIX

241 headings, 26 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

1 hidden heading(s) (aria-hidden)

H2 Authorities seize counterfeit NFL merchandise in Strip District
H3 2 Min Read | 2 hours Ago
H2 Hempfield man sentenced for bringing injured parakeet into Greensburg bar
H3 2 Min Read | 3 hours Ago
H2 Cause of fatal West Deer fire remains undeterminedVideo
H3 1 Min Read | 5 hours Ago
H3 local
H1 Pittsburgh transforms as NFL Draft festivities begin ahead of expected influx of fansVideo
H2 ‘I think that Pittsburgh is one of the most beautiful cities that I’ve ever seen’
H4 7 Min Read | 8 mins Ago skipped
H2 Sports Columnists
H3 Tim Benz
H4 View latest articles
H3 Joe Starkey
H4 View latest articles
H3 Mark Madden
H4 View latest articles
H5 local
H3 Authorities seize counterfeit NFL merchandise in Strip District
H4 Pennsylvania Attorney General Dave Sunday warned 2026 NFL Draft attendees to be wary
H6 2 Min Read | 2 hours Ago skipped
H5 local
H3 AI-driven sports technology from Carnegie Mellon students draws interest from Mark Cuban
H4 (empty)
H6 4 Min Read | 1 hour Ago skipped
H5 local
H3 PennWest merger undershot estimated tuition revenue by $53M, enrollment by 4,800 studentsVideo
H4 Spokesman says merger of Cal, Clarion, Edinboro couldn’t reverse decade-long enrollment declines
H6 6 Min Read | 4 hours Ago skipped
H2 Got a News Tip?
H3 Send us your tip Email Us
H3 Call Us
H2 Get TribLIVE News
H2 Sports Columnists
H3 Tim Benz
H4 View latest articles
H3 Joe Starkey
H4 View latest articles
H3 Mark Madden
H4 View latest articles
H2 Sports
H3 Chris Adamski’s Steelers mock draft: Give me playmaking WR first, worry about O-line later
H6 4 Min Read | 7 mins Ago skipped
H3 With NFL’s eyes on North Shore, Steelers football staff will be plotting team’s future on the South Side
H6 4 Min Read | 3 hours Ago skipped
H3 ‘Once-in-a-lifetime opportunity’: Top NFL Draft prospects ready to take center stage in Pittsburgh
H6 5 Min Read | 3 hours Ago skipped
H3 Penguins recall goaltender Sergei Murashov from Wilkes-Barre/Scranton
H6 1 Min Read | 1 hour Ago skipped
H3 Penguins forward Justin Brazeau expected to rejoin lineup for Game 3
H6 3 Min Read | 4 hours Ago skipped
H3 Mark Madden: Why are the Steelers letting Aaron Rodgers drag them around again?
H6 3 Min Read | 3 hours Ago skipped
H2 Top Stories
H4 Valley News Dispatch skipped
H3 Video shows Springdale Police arresting local critic during council meetingVideo
H5 4 Min Read | 49 mins Ago skipped
H4 Pennsylvania
H3 Fetterman looks to expand SNAP benefits to include hot rotisserie chicken
H5 2 Min Read | 1 hour Ago skipped
H4 Local
H3 First-time visitors land in Pittsburgh for NFL Draft and reunions
H5 3 Min Read | 1 hour Ago skipped
H4 World
H3 Pentagon says Navy Secretary John Phelan is leaving, the latest departure of a top defense leader
H5 2 Min Read | 1 hour Ago skipped
H2 Got a News Tip?
H3 Send us your tip Email Us
H3 Call Us
H2 Get TribLIVE News
H2 Sports Columnists
H3 Tim Benz
H4 View latest articles
H3 Joe Starkey
H4 View latest articles
H3 Mark Madden
H4 View latest articles
H2 Sports
H3 Chris Adamski’s Steelers mock draft: Give me playmaking WR first, worry about O-line later
H6 4 Min Read | 7 mins Ago skipped
H3 With NFL’s eyes on North Shore, Steelers football staff will be plotting team’s future on the South Side
H6 4 Min Read | 3 hours Ago skipped
H3 ‘Once-in-a-lifetime opportunity’: Top NFL Draft prospects ready to take center stage in Pittsburgh
H6 5 Min Read | 3 hours Ago skipped
H3 Penguins recall goaltender Sergei Murashov from Wilkes-Barre/Scranton
H6 1 Min Read | 1 hour Ago skipped
H3 Penguins forward Justin Brazeau expected to rejoin lineup for Game 3
H6 3 Min Read | 4 hours Ago skipped
H3 Mark Madden: Why are the Steelers letting Aaron Rodgers drag them around again?
H6 3 Min Read | 3 hours Ago skipped
H2 Editor's Picks
H5 sports skipped
H3 Photos: Inside the NFL Experience on the North Shore
H5 local skipped
H3 Trib Total Media announces members of Pittsburgh Community Advisory Panel
H5 local skipped
H3 Volunteer opportunities can make every day ‘Earth Day’
H5 local skipped
H3 A guide to NFL Draft week’s many bizarre and inspired events in Pittsburgh
H5 lifestyles skipped
H3 Researchers have spent decades breeding better potatoes for chips, and their work isn’t done
H2 Events
H2 Pittsburgh
H3 Authorities seize counterfeit NFL merchandise in Strip District
H3 Pittsburgh transforms as NFL Draft festivities begin ahead of expected influx of fansVideo
H3 Lawrenceville gas station killing prompts lawsuit by father of victim
H3 Former Steeler Jerome Bettis, NFL commissioner view CMU’s inventions to power sports
H3 Goodell, Rooney, McCarthy help open new Hazelwood Green community athletic field ahead of NFL Draft
H3 AI-driven sports technology from Carnegie Mellon students draws interest from Mark Cuban
H2 Westmoreland
H3 Hempfield man sentenced for bringing injured parakeet into Greensburg bar
H3 30 volunteers install raised beds for community garden in Jeannette
H3 What’s happening this summer at Westmoreland County Parks
H3 Federal rescue package in works for Spirit Airlines
H3 North Huntingdon donates old police car to Catholic Diocese police department
H3 Trump raises prospect of federal support or merger as Spirit Airlines struggles with costs and debt
H2 Valley News Dispatch
H3 Cause of fatal West Deer fire remains undeterminedVideo
H3 Leechburg baseball association to combine past and present at 75th annual opening day
H3 Video shows Springdale Police arresting local critic during council meetingVideo
H3 Second Vandergrift fire department back in service after insurance lapse
H3 New Kensington-Arnold School District pauses elementary building realignment plans
H3 Tarentum sewer line project expected to ease runoff near Ormond Street
H2 Allegheny
H3 Pittsburgh transforms as NFL Draft festivities begin ahead of expected influx of fansVideo
H3 Bridgeville woman accused of stealing $18K from Char Valley choral boosters account
H3 Nurture House, a new preschool in McCandless, keeps play the focus of learning
H3 Horseback riding program for children with disabilities seeks volunteers
H3 Trib Total Media announces members of Pittsburgh Community Advisory Panel
H3 Two29 Gallery in Braddock will open with a celebration of Pittsburgh’s ‘aerosol art’Video
H2 Regional
H3 PennWest merger undershot estimated tuition revenue by $53M, enrollment by 4,800 studentsVideo
H3 Volunteer opportunities can make every day ‘Earth Day’
H3 Grandmother, family friend charged in Renesmay Eutsey death investigation, Fayette DA says
H3 Pittsburgh locals split on NFL Draft, but agree it will be a spectacle
H3 Turnpike starts engineering work for updated Breezewood, I-70 interchangeVideo
H3 Breeze Airways delays restart of Pittsburgh-Los Angeles direct flights
H2 NFL Draft
H3 Chris Adamski’s Steelers mock draft: Give me playmaking WR first, worry about O-line later
H3 Pittsburgh transforms as NFL Draft festivities begin ahead of expected influx of fansVideo
H3 AI-driven sports technology from Carnegie Mellon students draws interest from Mark Cuban
H3 Authorities seize counterfeit NFL merchandise in Strip District
H3 Photos: Inside the NFL Experience on the North Shore
H3 First-time visitors land in Pittsburgh for NFL Draft and reunions
H2 U.S./World
H3 Pentagon says Navy Secretary John Phelan is leaving, the latest departure of a top defense leader
H3 U.S. health officials nix publication of a study on covid vaccine effectiveness
H3 Fetterman looks to expand SNAP benefits to include hot rotisserie chicken
H3 Photos: Inside the NFL Experience on the North Shore
H3 Federal appeals court blocks California law requiring federal agents to wear identification
H3 Chemical leak at a West Virginia plant kills 2 people and sends 30 others to hospitals, officials say
H2 Opinion
H3 Editorial: Can Pittsburgh afford compassionate catering?
H3 Bruce Cooper: Planet Earth, we are a crew
H3 Randi McCray: Democracy isn’t eroding. It’s evolving. The question is: Toward what?
H3 Editorial: 911 dispatchers are unseen first responders
H3 Joshua Rothman: Vaccine confusion sets up U.S. for a resurgence of hepatitis B in babies
H3 Brent Landau: Pa. Constitution is 250 years old — and as relevant as ever
H2 Partner News
H3 What’s happening this summer at Westmoreland County Parks
H3 Community Bank celebrates 125th anniversary with ‘Generations of Trust’ campaign
H3 Hidden Gems: Local Businesses Driven by Passion
H3 Do you have to pay taxes when you inherit a house in Pittsburgh?
H3 Protecting your home this spring: Why choosing the right roofing partner matters
H3 Penn Commercial Business/Technical School to host College & Career Fair on April 10
H2 Entertainment
H3 Freeport Area graduate to open for Jason Aldean at Pittsburgh concert
H3 Dave Mason, co-founder of Traffic known for ‘We Just Disagree’ and ‘Feelin’ Alright,’ dies at 79Video
H3 Two29 Gallery in Braddock will open with a celebration of Pittsburgh’s ‘aerosol art’Video
H3 Corrosion of Conformity’s Pepper Keenan talks about new double album ahead of Pittsburgh showVideo
H3 2026 Pittsburgh area concert calendar
H3 ‘True Colors’ of Phipps Conservatory shine through at Spring Flower ShowVideo
H2 Lifestyles
H3 New seafood restaurant coming to Pittsburgh’s Cultural District
H3 Exploring barefoot trails on 2 continents as a way to connect with nature this Earth Day
H3 Researchers have spent decades breeding better potatoes for chips, and their work isn’t done
H3 Primanti’s for beginners: Do’s, don’ts, tips and tricks for eating Pittsburgh’s legendary sandwichVideo
H3 Where to eat on the South Side during the 2026 NFL Draft
H3 Consumers are lost at sea as seafood sustainability grows more complex
H2 Rob Owen
H3 TV Q&A: What’s the deal with the vSeeBox?Video
H3 TV Talk: Duchovny revisits government secrets – real ones, this time – in ‘Secrets Declassified’Video
H3 TV Talk: Where and how to watch Draft coverage this week
H3 TV Talk: ‘The Pitt’ to film in Pittsburgh again in November
H3 TV Talk: Netflix’s ‘Beef’ back with more intimate conflict
H3 TV Q&A: Why are weather readings for Pittsburgh taken at the airport?
H2 Games
H3 Sudoku
H3 Crosswords
H2 WATCH NOW
H3 (empty)
H2 Company
H2 Get the Trib
H2 Sections
H2 Terms of Use
H2 Download TribLive
H2 We Care About Your Privacy
H3 We and our partners process data to provide:
H2 About Your Privacy
H2 About Your Privacy hidden
H3 Your Privacy
H3 Strictly Necessary Cookies
H3 Targeting Cookies
H3 Functional Cookies
H3 Performance Cookies
H3 Store and/or access information on a device 813 partners can use this purpose
H3 Personalised advertising and content, advertising and content measurement, audience research and services development 966 partners can use this purpose
H3 Use precise geolocation data 291 partners can use this special feature
H3 Actively scan device characteristics for identification 159 partners can use this special feature
H3 Ensure security, prevent and detect fraud, and fix errors 628 partners can use this special purpose
H3 Deliver and present advertising and content 621 partners can use this special purpose
H3 Save and communicate privacy choices 478 partners can use this special purpose
H3 Match and combine data from other data sources 444 partners can use this feature
H3 Link different devices 372 partners can use this feature
H3 Identify devices based on information transmitted automatically 578 partners can use this feature
H4 Your Privacy
H4 Strictly Necessary Cookies
H4 Targeting Cookies
H4 Functional Cookies
H4 Performance 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 966 partners can use this purpose
H5 Use limited data to select advertising 762 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 883 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 Save and communicate privacy choices 478 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
H3 Cookie List

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

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

404 Error Page

Action

HTTP 500, custom page

FIX

HTTP 500, custom page

Unexpected status code: HTTP 500

Expected HTTP 404 but received 500. This may confuse search engine crawlers.

Got: HTTP 500

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 500 ✗Page Title WordPress › Error ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #b32025

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 2 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Link & Button Quality

1 issue(s) across 332 links and 81 buttons

REVIEW

1 issue(s) across 332 links and 81 buttons

18 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://e.triblive.com/; https://triblive.com/sports/nfl-draft/; https://www.facebook.com/triblive; https://instagram.com/triblive/; https://twitter.com/TribLIVE; https://www.linkedin.com/showcase/triblive; https://mediakit.triblive.com/about/who-we-are/; https://mediakit.triblive.com/advertising-services; https://subscribe.triblive.com/; https://tribtotalmedia.com/subscriber-services/ (+8 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.form-control (#198 on page)

314 link(s) with descriptive text

332 links

0 empty

0 generic text

18 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://e.triblive.com/	E-TRIB	new tab	Add '(opens in new tab)' to text
https://triblive.com/sports/nfl-draft/	HSSN Promo	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/triblive	Facebook	new tab	Add '(opens in new tab)' to text
https://instagram.com/triblive/	Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com/TribLIVE	Twitter X	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/showcase/tribli…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://mediakit.triblive.com/about/who-…	About Us	new tab	Add '(opens in new tab)' to text
https://mediakit.triblive.com/advertisin…	Advertise	new tab	Add '(opens in new tab)' to text
https://subscribe.triblive.com/	Subscribe	new tab	Add '(opens in new tab)' to text
https://tribtotalmedia.com/subscriber-se…	Subscriber Services	new tab	Add '(opens in new tab)' to text
https://tribtotalmedia.com/jobs/	Work at TribLIVE	new tab	Add '(opens in new tab)' to text
https://tribtotalmedia.com/subscriber-se…	Feedback	new tab	Add '(opens in new tab)' to text
https://mediakit.triblive.com/blog/	Blog	new tab	Add '(opens in new tab)' to text
https://e.triblive.com/	eTrib	new tab	Add '(opens in new tab)' to text
https://tribtotalmedia.com/tribune-revie…	Store Locations	new tab	Add '(opens in new tab)' to text
/termsofservice/#Privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://cookiepedia.co.uk/giving-consent…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/solutions/conse…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

394 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://e.triblive.com/; https://triblive.com/sports/nfl-draft/; https://www.facebook.com/triblive; https://instagram.com/triblive/; https://twitter.com/TribLIVE; https://www.linkedin.com/showcase/triblive; https://mediakit.triblive.com/about/who-we-are/; https://mediakit.triblive.com/advertising-services; https://subscribe.triblive.com/; https://tribtotalmedia.com/subscriber-services/ (+8 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.form-control (#198 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

B

Lighthouse Accessibility Audits

Score 86/100 — 4 failing, 27 passed

REVIEW

86

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
2 MIN READ `div.row > div.col-9 > h3 > span.home-hero-3-read-length`
2 HOURS AGO `div.row > div.col-9 > h3 > span.home-hero-3-time-ago`
2 MIN READ `div.row > div.col-9 > h3 > span.home-hero-3-read-length`
3 HOURS AGO `div.row > div.col-9 > h3 > span.home-hero-3-time-ago`
1 MIN READ `div.row > div.col-9 > h3 > span.home-hero-3-read-length`
5 HOURS AGO `div.row > div.col-9 > h3 > span.home-hero-3-time-ago`
LOCAL `div#home-hero > a > div.home-hero-text > h3`
7 MIN READ `a > div.home-hero-text > h4 > span.home-hero-read-length`
8 MINS AGO `a > div.home-hero-text > h4 > span.home-hero-time-ago`
LOCAL `li.home-latest-item > a > div.home-latest-item-text > h5`
2 MIN READ `a > div.home-latest-item-text > h6 > span.home-latest-read-length`
2 HOURS AGO `a > div.home-latest-item-text > h6 > span.home-latest-time-ago`
LOCAL `li.home-latest-item > a > div.home-latest-item-text > h5`
4 MIN READ `a > div.home-latest-item-text > h6 > span.home-latest-read-length`
1 HOUR AGO `a > div.home-latest-item-text > h6 > span.home-latest-time-ago`
LOCAL `li.home-latest-item > a > div.home-latest-item-text > h5`
6 MIN READ `a > div.home-latest-item-text > h6 > span.home-latest-read-length`
4 HOURS AGO `a > div.home-latest-item-text > h6 > span.home-latest-time-ago`
VALLEY NEWS DISPATCH `li.home-top-stories-item > a > div.home-top-stories-item-text > h4`
4 MIN READ `a > div.home-top-stories-item-text > h5 > span.home-top-stories-read-length`
49 MINS AGO `a > div.home-top-stories-item-text > h5 > span.home-top-stories-time-ago`
PENNSYLVANIA `li.home-top-stories-item > a > div.home-top-stories-item-text > h4`
2 MIN READ `a > div.home-top-stories-item-text > h5 > span.home-top-stories-read-length`
1 HOUR AGO `a > div.home-top-stories-item-text > h5 > span.home-top-stories-time-ago`
LOCAL `li.home-top-stories-item > a > div.home-top-stories-item-text > h4`
3 MIN READ `a > div.home-top-stories-item-text > h5 > span.home-top-stories-read-length`
1 HOUR AGO `a > div.home-top-stories-item-text > h5 > span.home-top-stories-time-ago`
WORLD `li.home-top-stories-item > a > div.home-top-stories-item-text > h4`
2 MIN READ `a > div.home-top-stories-item-text > h5 > span.home-top-stories-read-length`
1 HOUR AGO `a > div.home-top-stories-item-text > h5 > span.home-top-stories-time-ago`
View latest articles `div.row > div.col-9 > h4 > a`
View latest articles `div.row > div.col-9 > h4 > a`
View latest articles `div.row > div.col-9 > h4 > a`
4 MIN READ `a > div.global-article-list-item-text > h6 > span.global-article-list-read-length`
7 MINS AGO `a > div.global-article-list-item-text > h6 > span.global-article-list-time-ago`
4 MIN READ `a > div.global-article-list-item-text > h6 > span.global-article-list-read-length`
3 HOURS AGO `a > div.global-article-list-item-text > h6 > span.global-article-list-time-ago`
5 MIN READ `a > div.global-article-list-item-text > h6 > span.global-article-list-read-length`
3 HOURS AGO `a > div.global-article-list-item-text > h6 > span.global-article-list-time-ago`
1 MIN READ `a > div.global-article-list-item-text > h6 > span.global-article-list-read-length`
1 HOUR AGO `a > div.global-article-list-item-text > h6 > span.global-article-list-time-ago`
3 MIN READ `a > div.global-article-list-item-text > h6 > span.global-article-list-read-length`
4 HOURS AGO `a > div.global-article-list-item-text > h6 > span.global-article-list-time-ago`
3 MIN READ `a > div.global-article-list-item-text > h6 > span.global-article-list-read-length`
3 HOURS AGO `a > div.global-article-list-item-text > h6 > span.global-article-list-time-ago`

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
7 MIN READ \| 8 MINS AGO `div#home-hero > a > div.home-hero-text > h4`
2 MIN READ \| 2 HOURS AGO `li.home-latest-item > a > div.home-latest-item-text > h6`
4 MIN READ \| 1 HOUR AGO `li.home-latest-item > a > div.home-latest-item-text > h6`
6 MIN READ \| 4 HOURS AGO `li.home-latest-item > a > div.home-latest-item-text > h6`
VALLEY NEWS DISPATCH `li.home-top-stories-item > a > div.home-top-stories-item-text > h4`
4 MIN READ \| 49 MINS AGO `li.home-top-stories-item > a > div.home-top-stories-item-text > h5`
2 MIN READ \| 1 HOUR AGO `li.home-top-stories-item > a > div.home-top-stories-item-text > h5`
3 MIN READ \| 1 HOUR AGO `li.home-top-stories-item > a > div.home-top-stories-item-text > h5`
2 MIN READ \| 1 HOUR AGO `li.home-top-stories-item > a > div.home-top-stories-item-text > h5`
4 MIN READ \| 7 MINS AGO `li.global-article-list-item > a > div.global-article-list-item-text > h6`
4 MIN READ \| 3 HOURS AGO `li.global-article-list-item > a > div.global-article-list-item-text > h6`
5 MIN READ \| 3 HOURS AGO `li.global-article-list-item > a > div.global-article-list-item-text > h6`
1 MIN READ \| 1 HOUR AGO `li.global-article-list-item > a > div.global-article-list-item-text > h6`
3 MIN READ \| 4 HOURS AGO `li.global-article-list-item > a > div.global-article-list-item-text > h6`
3 MIN READ \| 3 HOURS AGO `li.global-article-list-item > a > div.global-article-list-item-text > h6`
SPORTS `li.home-editors-picks-item > a > div.home-editors-picks-item-text > h5`
LOCAL `li.home-editors-picks-item > a > div.home-editors-picks-item-text > h5`
LOCAL `li.home-editors-picks-item > a > div.home-editors-picks-item-text > h5`
LOCAL `li.home-editors-picks-item > a > div.home-editors-picks-item-text > h5`
LIFESTYLES `li.home-editors-picks-item > a > div.home-editors-picks-item-text > h5`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > img#06db9294 `body.home > img#06db9294`

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
PITTSBURGH `div.container > div.row > div.col-9 > a`
View all > `div.container > div.row > div.col-3 > a`
WESTMORELAND `div.container > div.row > div.col-9 > a`
View all > `div.container > div.row > div.col-3 > a`
VALLEY NEWS DISPATCH `div.container > div.row > div.col-9 > a`
View all > `div.container > div.row > div.col-3 > a`

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

●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 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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●All heading elements contain content.

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○Uses ARIA roles only on compatible elements

○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 75 images OK

PASS

All 75 images OK

3 image(s) with alt text over 125 characters

9 decorative image(s) correctly marked

63 image(s) with good alt text

75 images 63 good alt text 9 decorative

Issue	Count
too long	3 image(s)

A

Form Accessibility

1 of 23 controls have issues

PASS

1 of 23 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="search">

22 control(s) properly labeled

23 controls

22 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-IAB2V2_1	checkbox	Store and/or access information on a device	for/id
#ot-group-id-V2STACK42	checkbox	Personalised advertising and content, advertising and content measurement, audience research and services development	for/id
#ot-sub-group-id-IAB2V2_2	checkbox	Use limited data to select advertising	aria-label
#ot-sub-group-id-IAB2V2_3	checkbox	Create profiles for personalised advertising	aria-label
#ot-sub-group-id-IAB2V2_4	checkbox	Use profiles to select personalised advertising	aria-label
#ot-sub-group-id-IAB2V2_5	checkbox	Create profiles to personalise content	aria-label
#ot-sub-group-id-IAB2V2_6	checkbox	Use profiles to select personalised content	aria-label
#ot-sub-group-id-IAB2V2_7	checkbox	Measure advertising performance	aria-label
#ot-sub-group-id-IAB2V2_8	checkbox	Measure content performance	aria-label
#ot-sub-group-id-IAB2V2_9	checkbox	Understand audiences through statistics or combinations of data from different sources	aria-label
#ot-sub-group-id-IAB2V2_10	checkbox	Develop and improve services	aria-label
#ot-sub-group-id-IAB2V2_11	checkbox	Use limited data to select content	aria-label
#ot-group-id-ISF2V2_1	checkbox	Use precise geolocation data	for/id
#ot-group-id-ISF2V2_2	checkbox	Actively scan device characteristics for identification	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#chkbox-id	checkbox	checkbox label	for/id
search	text	(Search the TRIB)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

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

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)

Element	Ratio	Required	FG	BG	Result
h1 Pittsburgh transform…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Authorities seize co…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Hempfield man senten…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Cause of fatal West …	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 ‘I think that Pitt…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Sports Columnists	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Sports Columnists	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Sports Columnists	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Events	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 WATCH NOW	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Company	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Get the Trib	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Sections	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Terms of Use	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Download TribLive	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 We Care About Your P…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 About Your Privacy	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 About Your Privacy	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 local	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Tim Benz	5.24:1	3.0:1	#000000	#7F7F7F	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.