Skip to content
https://smh.com.au

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Heading Hierarchy
Action
536 headings, 101 skip(s)
FIX
536 headings, 101 skip(s)
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
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 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 The Sydney Morning Herald
  • H2 The Sydney Morning Herald
  • H4 Premium skipped
  • H4 More
  • H3 Good Food - What’s for Dinner
  • H3 The Morning Edition podcast
  • H3 Mini Crossword
  • H5 Live skipped
  • H5 Middle East at war
  • H3 Vance’s trip to Pakistan for peace talks ‘on hold’; Iran yet to decide on attending
  • H3 Latest live posts
  • H3 Two Israeli soldiers punished after destroying Jesus statue in Lebanon
  • H3 Witkoff, Kushner arrive at White House
  • H3 US military boards Iran-linked oil tanker in Indian Ocean
  • H3 Vance, Rubio still meeting with Trump at White House, says US official
  • H5 Exclusive skipped
  • H5 AUKUS
  • H3 Australia’s depending on AUKUS Virginia-class subs. The US says they’re not its priority
  • H5 Opinion skipped
  • H5 Opinion
  • H3 Iran wants to make peace with the US this week – if Trump’s ego doesn’t get in the way
  • H5 Clinton Fernandes skipped
  • H5 Nick Greiner
  • H3 Nick Greiner’s parting advice to bring the Libs back from extinction
  • H5 City life skipped
  • H3 Inside the fight to turn this hard-won Sydney land into housing
  • H5 Public transport skipped
  • H3 Revealed: The growing cost of delays to opening final stage of Sydney’s M1 metro line
  • H5 Income tax skipped
  • H3 States warned on spending binge as they all collected record tax takes
  • H5 Opinion skipped
  • H5 Australian economy
  • H3 Lovin’ democracy? You’re probably doing all right, then
  • H5 Ross Gittins skipped
  • H5 Analysis
  • H5 Start-ups
  • H3 A $50 billion NDIS is proving too tempting for Australia’s rich-listers
  • H5 Colin Kruger skipped
  • H5 Federal budget
  • H3 Labor to tackle two of budget’s biggest headaches – aged care and NDIS – in one go
  • H5 Education skipped
  • H3 The secret to the NAPLAN writing test that students aren’t told about
  • H5 Opinion skipped
  • H5 HSC
  • H3 HSC advanced maths exodus adds up. But it points to another problem
  • H5 Bronwyn Reid O'Connor skipped
  • H5 Property market
  • H3 The type of home where prices are falling most right now
  • H5 Tax deductions skipped
  • H3 How drivers could get bigger tax deductions for car expenses within months
  • H5 Wallabies skipped
  • H3 The Wallabies will have a stacked back line in 2027. This is why Jorgensen is already excited
  • H5 Opinion skipped
  • H5 Travel tips
  • H3 The nine cities that gave me a terrible first impression
  • H5 Ben Groundwater skipped
  • H5 Got a Minute?
  • H3 Everything’s gone south since our company was acquired. Now what?
  • H5 Taste test skipped
  • H3 A major chain cheapie takes top spot in the not-so-great supermarket Anzac biscuit taste test
  • H5 ★★½ skipped
  • H5 Review
  • H3 Baby Reindeer wasn’t an easy watch, but Richard Gadd’s new show is punishing
  • H5 Spectrum skipped
  • H3 Ben Lerner’s gorgeously crafted novel explores the human world of wrong turns
  • H2 Just in
  • H3 Thinking of selling mum’s silverware? It’s all in the timing
  • H5 Opinion skipped
  • H3 I’m 67 and working part-time. Should I start drawing on my super?
  • H5 Opinion skipped
  • H3 Iran wants to make peace with the US this week – if Trump’s ego doesn’t get in the way
  • H3 The Wallabies will have a stacked back line in 2027. This is why Jorgensen is already excited
  • H2 Editor's Picks
  • H5 Updated skipped
  • H5 Police
  • H3 ‘I haven’t done anything wrong’: Accused Treasury official denies corrupt motive behind data breach
  • H5 Analysis skipped
  • H5 Science
  • H3 Experts linked this popular teen activity with cancer. Then came the backlash
  • H5 Angus Dalton skipped
  • H5 Opinion
  • H5 Sex & relationships
  • H3 The manosphere is obsessed with Pilates. It’s about far more than fitness
  • H5 Jenna Guillaume skipped
  • H2 shorts
  • H5 Series skipped
  • H3 Healthy, wealthy and retired
  • H3 Brought to you by
  • H3 The best midlife investment you can make has nothing to do with money
  • H3 How do you know when you’re ready to retire?
  • H3 Five years ago today I beat breast cancer. This insurance saved me
  • H3 Six surprising habits only the happiest retirees get right
  • H2 MIDDLE EAST IN CRISIS
  • H3 Trump expects ‘great deal’ from Iran talks as ceasefire ticks down
  • H5 Opinion skipped
  • H3 Trump is an absolute disaster for the oil and gas industry
  • H5 Ambrose Evans-Pritchard skipped
  • H5 Opinion
  • H3 Trump’s madcap folly emboldening this ‘axis of upheaval’
  • H5 Peter Hartcher skipped
  • H3 Trump has become the star of Iran’s Lego movies
  • H5 Exclusive skipped
  • H3 Australians turn on ‘unreliable, erratic’ Trump as Iran war drags on
  • H2 Sydney
  • H5 Defamation skipped
  • H3 ‘Nuts’: Explosive texts in Rebel Wilson defamation case
  • H5 Development skipped
  • H3 High-density housing is coming to this Sydney suburb – but not its most exclusive street
  • H5 Investigation skipped
  • H5 Healthcare
  • H3 After her sister died, Jessica went for a check-up. Soon, she too was dead
  • H5 Courts skipped
  • H3 Principal, teachers accused of assaulting multiple school boys
  • H5 City life skipped
  • H3 Vote on 20 ways we could improve Sydney
  • H2 From our partners
  • H5 domain skipped
  • H3 What you get for $2 million in a $4 million suburb
  • H2 Politics
  • H5 Analysis skipped
  • H5 Middle East at war
  • H3 Fix the budget with more tax on gas? The world’s changed since Pocock’s viral video
  • H5 Mike Foley skipped
  • H5 Defence
  • H3 ‘Star Wars is happening now’: $7b splurge on drone-killing tech
  • H5 Exclusive skipped
  • H5 Victorian election
  • H3 Poised to pounce on a key byelection, One Nation’s campaign committee collapsed
  • H5 Exclusive skipped
  • H5 Byelection
  • H3 One Nation just whingeing, Canavan says as Coalition swaps preferences
  • H2 Business
  • H5 Watch skipped
  • H5 Aviation
  • H3 Thousands of nervous flyers come to him for help. This is what he tells them
  • H5 Analysis skipped
  • H5 Gadgets
  • H3 What can we expect from Apple’s next boss?
  • H5 Tim Biggs skipped
  • H5 Iron ore
  • H3 Fortescue launches ad blitz against billion-dollar diesel tax ‘handouts’
  • H5 Aviation skipped
  • H3 Qantas, Virgin launch domestic ticket deals to fill cash coffers in Iran crisis
  • H2 World
  • H5 Analysis skipped
  • H5 UK politics
  • H3 A comedian could not have done a better job than Starmer’s earnest pitch to parliament
  • H5 David Crowe skipped
  • H5 Drugs
  • H3 These salmon got high on cocaine. That wasn’t the craziest part
  • H5 Updated skipped
  • H5 US politics
  • H3 Trump loses third cabinet member, FBI boss sues over ‘problem drinker’ story
  • H5 Mass shooting skipped
  • H3 ‘Horrific act’: Tourist killed as gunman opens fire at ​Mexico ​pyramids
  • H2 Opinion
  • H3 The massive ‘care gaps’ exposing Australia’s aged care crisis
  • H5 Rachel Lane skipped
  • H3 I want to leave all my money to my kids; the government has different ideas
  • H5 Jenna Price skipped
  • H3 Special treatment for Ben Roberts-Smith needs a better explanation
  • H5 The Herald's View skipped
  • H3 The day Prince died ended an era. Ten years on, the loss still lingers
  • H5 George Palathingal skipped
  • H2 Explore
  • H4 Premium skipped
  • H4 Got a news tip?
  • H2 Property
  • H5 Title Deeds skipped
  • H3 ‘Love living there’: Why ex-Woolies boss Brad Banducci decided not to move
  • H5 Auctions skipped
  • H3 ‘Spectacular’: Local family pays $8.95m on northern beaches
  • H5 Construction skipped
  • H3 What the reality TV reno shows don’t tell you
  • H5 Exclusive skipped
  • H5 Title Deeds
  • H3 Freight boss sells $11m home in elite Sydney suburb
  • H5 Auctions skipped
  • H3 ‘We fell in love with it’: Unrenovated inner west home sells for $2.4 million
  • H2 Good Food
  • H5 MasterChef Recap skipped
  • H3 The front-runners, the dark horses and the one who will rub you up the wrong way on MasterChef
  • H5 Review skipped
  • H5 Newtown
  • H3 ‘Bedrock of Australia Street’: Why this Newtown spot remains a firm favourite
  • H5 Exclusive skipped
  • H5 Just open
  • H3 First look at legendary Leichhardt restaurant Grappa’s upmarket spin-off
  • H5 Good Food events skipped
  • H3 Is takeaway the future of dining? The stats suggest yes, but the industry is adapting
  • H2 Lifestyle
  • H5 Sex & relationships skipped
  • H3 Signs you may be a ‘placeholder partner’ in your relationship
  • H5 Fitness skipped
  • H3 Too tired to exercise? These tips will get your energy up
  • H5 Sunday Life skipped
  • H3 The breakfast swap a dietitian prescribes this fitness influencer for better energy payoff
  • H5 Sunday Life skipped
  • H3 Kathy Lette wanted a trip to make her feel young again. Here’s where she went
  • H5 Exclusive skipped
  • H5 Prostate cancer
  • H3 It’s the deadliest cancer for Australian men. This test could be life-saving for many, and their daughters
  • H2 Culture
  • H5 Exit interview skipped
  • H5 Reality TV
  • H3 Laura Byrne worried about one thing covering MAFS. It became her favourite part
  • H5 Cinema skipped
  • H3 Daniel MacPherson: ‘I had a broken nose, fractured pelvis and still kept fighting’
  • H5 Vale skipped
  • H3 Melrose Place and Starship Troopers star dies suddenly
  • H5 Review skipped
  • H3 What to stream this week: Elle Fanning’s gutsy sex work dramedy, plus five more new picks
  • H5 Literature skipped
  • H3 How AI is trying to rival a creative mind when it comes to writing novels
  • H2 Traveller
  • H5 Opinion skipped
  • H5 Travel tips
  • H3 The nine cities that gave me a terrible first impression
  • H5 ★★★½ skipped
  • H5 Hotel reviews
  • H3 After 26 years, Australians still flock to this sprawling Pacific island resort
  • H5 Queensland skipped
  • H3 The unexpectedly cool Queensland town you’ve probably never heard of
  • H5 Europe skipped
  • H3 A town’s unique fountain made us change our honeymoon route
  • H2 Drivedrive
  • H3 Why a damaged car could be the cheapest way into the EV market
  • H3 The tech-laden hybrid SUV that proves sometimes less is more
  • H3 Australia and China keep gifting cars to other countries – here's why
  • H2 From Our Partners
  • H5 stan skipped
  • H3 Starring Elizabeth Banks and Matthew Macfadyen, The Miniature Wife is streaming now, only on Stan.
  • H5 stan skipped
  • H3 Stan has your exclusive backstage pass to all the drama with MAFS: After The Dinner Party. Streaming now, exclusively on Stan.
  • H2 Sport
  • H5 Wallabies skipped
  • H3 The Wallabies will have a stacked back line in 2027. This is why Jorgensen is already excited
  • H5 NRL 2026 skipped
  • H3 ‘No one knows the club like me’: Dean Young embraces tough task at Dragons
  • H5 NRL 2026 skipped
  • H3 The Kokoda lessons Daly Cherry-Evans will never forget
  • H5 NRL 2026 skipped
  • H3 Young talent time: Kade Reed to debut, Kyle Flanagan dropped
  • H5 Australian rugby skipped
  • H3 Lions help RA post record $70m profit as Wallabies get good news on star duo
  • H5 Updated skipped
  • H5 Around the clubs
  • H3 ‘Sky’s the limit’: Rabbitohs stars back versatile teammate to play Origin
  • H5 Club rugby skipped
  • H3 Former league star Phil Blake sues club over sacking as coach
  • H2 Have Your Say
  • H3 Dragons take aim at ‘personal agendas’ but Flanagan got a good run
  • H5 Chris Barrett skipped
  • H2 More in Sport
  • H5 Soccer skipped
  • H3 City star Haaland relishes the moment as Arsenal slide continues
  • H5 Updated skipped
  • H5 AFL
  • H3 Further drug test details emerge as Ollie Hollands sends loving message to Elijah
  • H5 Updated skipped
  • H5 NRL
  • H3 Dean Young takes over as interim head coach after Dragons part ways with Flanagan
  • H5 NRL skipped
  • H3 Daley backs Blues depth after Haas ruled out of Origin series opener
  • H5 Analysis skipped
  • H5 NRL
  • H3 The Sunday breakfast that sealed Flanagan’s fate at the Dragons
  • H5 Updated skipped
  • H5 AFL
  • H3 Carlton say Elijah Hollands has been admitted to hospital
  • H5 Exclusive skipped
  • H5 AFL
  • H3 ‘There was a bit of chatter’: Pie aware of Hollands talk on field
  • H5 Opinion skipped
  • H5 NRL
  • H3 Why the Dragons will overlook the most obvious replacement for Shane Flanagan
  • H2 Featured video
  • H5 AFL skipped
  • H3 AFL demands answers on Hollands saga
  • H2 Racing
  • H5 Horse racing skipped
  • H3 Tips and race-by-race guide for Canterbury on Wednesday
  • H5 Horse racing skipped
  • H3 Charlton content to bide his time with ‘immature’ gelding
  • H5 Horse racing skipped
  • H3 Waller’s Sydney autumn domination ends with double delight
  • H2 Most Viewed today
  • H3 Young talent time: Kade Reed to debut, Kyle Flanagan dropped
  • H3 US-Iran war as it happened: Trump says he won’t be ‘rushed into making a bad deal’; Vance to lead US delegation in Pakistan for peace talks with Iran as ceasefire deadline nears
  • H3 High-density housing is coming to this Sydney suburb – but not its most exclusive street
  • H3 The world’s 10 most beautiful libraries every book-lover should visit
  • H3 Former league star Phil Blake sues club over sacking as coach
  • H5 Opinion skipped
  • H3 My flight to Europe is cancelled. I’m nervous about accepting the replacement
  • H3 After her sister died, Jessica went for a check-up. Four months later, she was dead
  • H3 Special treatment for Ben Roberts-Smith needs a better explanation
  • H3 ‘Never waste a crisis’: Ex-Shell executive says it’s time for Australia to tax windfall profits on energy
  • H2 The Sydney Morning Herald
  • H3 Our Sites
  • H3 Classifieds
  • H3 The Sydney Morning Herald
  • H3 Products & Services
  • H1 We value your privacy. With your consent we use data to do the following: duplicate H1
  • H1 Manage your data duplicate H1
  • H2 Store and/or access information on a device
  • H2 Use limited data to select advertising
  • H2 Create profiles for personalised advertising
  • H2 Use profiles to select personalised advertising
  • H2 Create profiles to personalise content
  • H2 Use profiles to select personalised content
  • H2 Measure advertising performance
  • H2 Measure content performance
  • H2 Understand audiences through statistics or combinations of data from different sources
  • H2 Develop and improve services
  • H2 Use limited data to select content
  • H2 Ensure security, prevent and detect fraud, and fix errors
  • H2 Deliver and present advertising and content
  • H2 Save and communicate privacy choices
  • H2 Match and combine data from other data sources
  • H2 Link different devices
  • H2 Identify devices based on information transmitted automatically
  • H2 Use precise geolocation data
  • H2 Storage, duration, and usage details
  • H1 Confirm our vendors duplicate H1
  • H2 Exponential Interactive, Inc d/b/a VDX.tv
  • H2 Index Exchange Inc.
  • H2 Quantcast
  • H2 BeeswaxIO Corporation
  • H2 Sovrn, Inc.
  • H2 Adkernel LLC
  • H2 Adikteev
  • H2 RTB House S.A.
  • H2 The UK Trade Desk Ltd
  • H2 Nexxen Inc.
  • H2 Epsilon
  • H2 Yahoo EMEA Limited
  • H2 ADventori SAS
  • H2 Triple Lift, Inc.
  • H2 Xandr, Inc.
  • H2 Nexxen Group LLC
  • H2 NEURAL.ONE
  • H2 ADITION (Virtual Minds GmbH)
  • H2 Active Agent (Virtual Minds GmbH)
  • H2 Equativ
  • H2 Adform A/S
  • H2 Magnite, Inc.
  • H2 RATEGAIN ADARA INC
  • H2 Sift Media, Inc
  • H2 Lumen Research Limited
  • H2 OpenX
  • H2 Yieldlab (Virtual Minds GmbH)
  • H2 Simplifi Holdings LLC
  • H2 PubMatic, Inc
  • H2 Comscore B.V.
  • H2 Flashtalking
  • H2 Sharethrough, Inc
  • H2 PulsePoint, Inc.
  • H2 Smaato, Inc.
  • H2 Crimtan Holdings Limited
  • H2 Criteo SA
  • H2 SCOPE3 SAS
  • H2 LiveRamp
  • H2 WPP Media
  • H2 Sonobi, Inc
  • H2 LoopMe Limited
  • H2 Dynata LLC
  • H2 Ask Locala
  • H2 Azira
  • H2 DoubleVerify Inc.
  • H2 BIDSWITCH GmbH
  • H2 IPONWEB GmbH
  • H2 NextRoll, Inc.
  • H2 Media.net Advertising FZ-LLC
  • H2 LiveIntent Inc.
  • H2 Basis Global Technologies, Inc.
  • H2 Seedtag Advertising S.L
  • H2 SMADEX, S.L.U.
  • H2 Bombora Inc.
  • H2 Outbrain UK.
  • H2 Yieldmo, Inc.
  • H2 A Million Ads
  • H2 Remerge GmbH
  • H2 Affle Iberia SL
  • H2 Magnite CTV, Inc.
  • H2 Delta Projects AB
  • H2 Zemanta Inc.
  • H2 AcuityAds Inc.
  • H2 Rockerbox, Inc
  • H2 StackAdapt Inc.
  • H2 OneTag Limited
  • H2 Smartology Limited
  • H2 Improve Digital
  • H2 Adobe Advertising Cloud
  • H2 Bannerflow AB
  • H2 TabMo SAS
  • H2 Integral Ad Science (incorporating ADmantX)
  • H2 Wizaly
  • H2 Weborama
  • H2 Readpeak Oy
  • H2 Jivox Corporation
  • H2 Sojern, Inc.
  • H2 Polar Mobile Group Inc.
  • H2 On Device Research Limited
  • H2 Exactag GmbH
  • H2 Celtra Inc.
  • H2 ADTIMING TECHNOLOGY PTE. LTD
  • H2 Gemius SA
  • H2 InMobi Pte Ltd
  • H2 The Kantar Group Limited
  • H2 Samba TV UK Limited
  • H2 Nielsen Media Research Ltd.
  • H2 RevX
  • H2 Pixalate, Inc.
  • H2 Triapodi Ltd. d/b/a Digital Turbine
  • H2 AudienceProject A/S
  • H2 Eulerian Technologies
  • H2 Seenthis AB
  • H2 travel audience GmbH
  • H2 HUMAN
  • H2 Streamwise srl
  • H2 Innovid LLC
  • H2 Zeta Global Corp.
  • H2 Madington
  • H2 Opinary (Affinity Global GmbH)
  • H2 GumGum, Inc.
  • H2 Cint USA, Inc.
  • H2 Jampp LTD
  • H2 Realtime Technologies GmbH
  • H2 DeepIntent, Inc.
  • H2 Happydemics
  • H2 Otto GmbH & Co. KGaA
  • H2 Adobe Audience Manager, Adobe Experience Platform
  • H2 CHEQ AI TECHNOLOGIES
  • H2 Localsensor B.V.
  • H2 Adnami Aps
  • H2 Blue
  • H2 Relay42 Netherlands B.V.
  • H2 Mobsuccess
  • H2 Liftoff Monetize and Vungle Exchange
  • H2 The MediaGrid Inc.
  • H2 Go.pl sp. z o.o.
  • H2 HyperTV, Inc.
  • H2 Appier PTE Ltd
  • H2 6Sense Insights, Inc.
  • H2 Google Advertising Products
  • H2 GfK GmbH
  • H2 Clinch Labs LTD
  • H2 Amazon Ads
  • H2 LinkedIn Ireland Unlimited Company
  • H2 Moloco, Inc.
  • H2 Nielsen International SA
  • H2 Mintegral International Limited
  • H2 PRECISO SRL
  • H2 Pelmorex Corp.
  • H2 TikTok Ad Network
  • H2 Extreme Reach, Inc
  • H2 Somplo Ltd
  • H2 Adelaide Metrics Inc
  • H2 Baidu (Hong Kong) Limited
  • H2 Arpeely Ltd.
  • H2 Adventure Media SARL
  • H2 Microsoft Advertising
  • H2 Opera Software Ireland Limited
  • H2 xpln.ai SAS
  • H2 ABCS INSIGHTS
  • H2 Affle Inc
  • H2 Admaster Private Limited
  • H2 Bidease Inc
  • H2 Intango Ltd
  • H2 Artsai
  • H2 Meta
  • H2 C3 Metrics
  • H2 Roku Advertising Services
  • H2 eBay
  • H2 Evidon
  • H2 GroovinAds
  • H2 Sizmek
  • H2 Equativ
  • H2 SMN Corporation
  • H2 TrustArc
  • H2 CyberAgent
  • H2 MicroAd
  • H2 AdMaxim
  • H2 Magnite
  • H2 Yango
  • H2 Singular Labs Inc.
  • H2 Neustar
  • H2 Netquest
  • H2 Cloudflare
  • H2 Salesforce DMP
  • H2 Bridgewell
  • H2 AppLovin Corp.
  • H2 AdTheorent, Inc.
  • H2 Rackspace
  • H2 Placed
  • H2 Aarki
  • H2 NinthDecimal
  • H2 TreSensa
  • H2 Bigabid
  • H2 Optimize LCC D.B.A Genius Monkey
  • H2 gskinner
  • H2 Yahoo! Japan
  • H2 Chalk Digital
  • H2 jsdelivr
  • H2 HockeyCurve
  • H2 Upwave
  • H2 IQM
  • H2 fluct
  • H2 Zucks
  • H2 UNICORN
  • H2 AdFalcon
  • H2 Supership
  • H2 Marketing Science Consulting Group, Inc.
  • H2 Kobler
  • H2 Adstra
  • H2 Persona.ly
  • H2 Oracle Data Cloud
  • H2 Throtle
  • H2 ironSource Mobile
  • H2 MediaPal
  • H2 Tuky Data
  • H2 CONTXTFUL
  • H2 MarketCast LLC
  • H2 LeadsRx
  • H2 clean.io
  • H2 Unity Ads
  • H2 Loblaw Media
  • H2 Ad Lightning
  • H2 Lacuna
  • H2 Coupang
  • H2 Playable Factory
  • H2 Prism Partner
  • H2 TemuDSP
  • H2 DISQO
  • H2 Mercado Livre
  • H1 (empty)

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

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

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

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

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
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.
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::
7 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 7 <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
Alt Text Quality
4 of 109 images have issues
REVIEW
4 of 109 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
3 image(s) with generic alt text
Info::
6 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
97 image(s) with good alt text
109 images 97 good alt text 2 decorative 3 generic 1 missing
IssueCount
missing1 image(s)
generic3 image(s)
too long6 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Sydney Morning H…3.66:13.0:1
#000000
#666666
Pass
h1 We value your privac…3.66:13.0:1
#000000
#666666
Pass
h1 Manage your data3.66:13.0:1
#000000
#666666
Pass
h1 Confirm our vendors3.66:13.0:1
#000000
#666666
Pass
h2 The Sydney Morning H…3.66:13.0:1
#000000
#666666
Pass
h2 Editor's Picks3.66:13.0:1
#000000
#666666
Pass
h2 shorts3.66:13.0:1
#000000
#666666
Pass
h2 From our partners3.66:13.0:1
#000000
#666666
Pass
h2 Explore3.66:13.0:1
#000000
#666666
Pass
h2 From Our Partners3.66:13.0:1
#000000
#666666
Pass
h2 Have Your Say3.66:13.0:1
#000000
#666666
Pass
h2 More in Sport3.66:13.0:1
#000000
#666666
Pass
h2 Featured video3.66:13.0:1
#000000
#666666
Pass
h2 Most Viewed today3.66:13.0:1
#000000
#666666
Pass
h2 The Sydney Morning H…3.66:13.0:1
#000000
#666666
Pass
h2 Store and/or access …3.66:13.0:1
#000000
#666666
Pass
h2 Use limited data to …3.66:13.0:1
#000000
#666666
Pass
h2 Create profiles for …3.66:13.0:1
#000000
#666666
Pass
h2 Use profiles to sele…3.66:13.0:1
#000000
#666666
Pass
h2 Create profiles to p…3.66:13.0:1
#000000
#666666
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 25 passed
REVIEW
83

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
Money contributor div.z3g3Y > div.vwQJl > div > p.LhCcW
Columnist div.z3g3Y > div.vwQJl > div > p.LhCcW
Editorial div.z3g3Y > div.vwQJl > div > p.LhCcW
Senior music writer div.z3g3Y > div.vwQJl > div > p.LhCcW
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

These are opportunities to improve the legibility of your content.

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
a > div.pc0-m > picture > img.ZAk8w
a > div.pc0-m > picture > img.ZAk8w
a > div.pc0-m > picture > img.ZAk8w

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.YzFy- > div#homepage-header-subscribe-button-piano-id > div.tp-container-inner > iframe#offer_9fadc4fc427b415c63ed-0 div.YzFy- > div#homepage-header-subscribe-button-piano-id > div.tp-container-inner > iframe#offer_9fadc4fc427b415c63ed-0

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
div.Gg84- > div.qWp8L > figure.-RwuQ > a
div.dgB04 > div.qWp8L > figure.-RwuQ > a
div.dgB04 > div.qWp8L > figure.-RwuQ > a

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.

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
Live div.qWp8L > div.z3g3Y > div.EKPfZ > h5.Lxtfy
Exclusive div.nNhKL > div.qWp8L > div.EKPfZ > h5._77RNt
Opinion div.nNhKL > div.qWp8L > div.EKPfZ > h5._77RNt
Clinton Fernandes div.z3g3Y > div.vwQJl > div > h5.VM6Jl
City life div.C0fem > div.qWp8L > div.EKPfZ > h5.bxWRo
Public transport div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Income tax div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Opinion div.nNhKL > div.qWp8L > div.EKPfZ > h5._77RNt
Ross Gittins div.z3g3Y > div.vwQJl > div > h5.VM6Jl
Colin Kruger div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl
Education div.nNhKL > div.qWp8L > div.EKPfZ > h5.bxWRo
Opinion div.C0fem > div.qWp8L > div.EKPfZ > h5._77RNt
Bronwyn Reid O'Connor div.z3g3Y > div.vwQJl > div > h5.VM6Jl
Tax deductions div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Wallabies div.nNhKL > div.qWp8L > div.EKPfZ > h5.bxWRo
Opinion div.nNhKL > div.qWp8L > div.EKPfZ > h5._77RNt
Ben Groundwater div.z3g3Y > div.vwQJl > div > h5.VM6Jl
Taste test div.nNhKL > div.qWp8L > div.EKPfZ > h5.bxWRo
★★½ div.-tzWc > div.qWp8L > div.EKPfZ > h5._77RNt
Spectrum div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Opinion div > div.bcQQs > div.AcFMr > h5._6nsXK
Opinion div > div.bcQQs > div.AcFMr > h5._6nsXK
Updated div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Analysis div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Angus Dalton div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl
Jenna Guillaume div.z3g3Y > div.vwQJl > div > h5.VM6Jl
Series div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Opinion div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Ambrose Evans-Pritchard div.z3g3Y > div.vwQJl > div > h5.VM6Jl
Peter Hartcher div.z3g3Y > div.vwQJl > div > h5.VM6Jl
Exclusive div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Defamation div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Development div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Investigation div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Courts div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
City life div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Domain div.qWp8L > div.z3g3Y > div.EKPfZ > h5.Kc1uy
Analysis div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Mike Foley div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl
Exclusive div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Exclusive div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Watch div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Analysis div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Tim Biggs div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl
Aviation div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Analysis div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
David Crowe div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl
Updated div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Mass shooting div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Rachel Lane div.z3g3Y > div.vwQJl > div > h5.VM6Jl
Jenna Price div.z3g3Y > div.vwQJl > div > h5.VM6Jl
The Herald's View div.z3g3Y > div.vwQJl > div > h5.VM6Jl
George Palathingal div.z3g3Y > div.vwQJl > div > h5.VM6Jl
PREMIUM div > section.vov3Q > div._1ooGP > h4._4wR92
Title Deeds div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Auctions div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Construction div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Exclusive div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Auctions div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
MasterChef Recap div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Review div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Exclusive div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Good Food events div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Sex & relationships div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Fitness div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Sunday Life div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Sunday Life div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Exclusive div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Exit interview div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Cinema div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Vale div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Review div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Literature div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Opinion div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
★★★½ div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Queensland div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Europe div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Stan div.qWp8L > div.z3g3Y > div.EKPfZ > h5.Kc1uy
Stan div.qWp8L > div.z3g3Y > div.EKPfZ > h5.Kc1uy
Wallabies div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
NRL 2026 div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
NRL 2026 div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
NRL 2026 div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Australian rugby div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Updated div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt
Club rugby div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Chris Barrett div.z3g3Y > div.vwQJl > div > h5.VM6Jl
SOCCER div.qWp8L > div.z3g3Y > div.FPWpc > h5.WXkF7
Updated div.qWp8L > div.z3g3Y > div.FPWpc > h5.HlHTW
Updated div.qWp8L > div.z3g3Y > div.FPWpc > h5.HlHTW
NRL div.qWp8L > div.z3g3Y > div.FPWpc > h5.WXkF7
Analysis div.qWp8L > div.z3g3Y > div.FPWpc > h5.HlHTW
Updated div.qWp8L > div.z3g3Y > div.FPWpc > h5.HlHTW
Exclusive div.qWp8L > div.z3g3Y > div.FPWpc > h5.HlHTW
Opinion div.qWp8L > div.z3g3Y > div.FPWpc > h5.HlHTW
AFL div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Horse racing div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Horse racing div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Horse racing div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo
Opinion div.qWp8L > div.z3g3Y > div.FPWpc > h5.HlHTW

These are opportunities to improve keyboard navigation in your application.

○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
●`[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.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●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
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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
Landmark Structure
37 landmarks
PASS
37 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
7 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A
Form Accessibility
1 of 284 controls have issues
PASS
1 of 284 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
283 control(s) properly labeled
284 controls
283 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#site-searchsearchSearch Sitefor/id
inputcheckboxConsent (123 vendors)none
inputcheckboxConsent (75 vendors)none
#fc-preference-slider-purpose-2checkboxLegitimate interest (41 vendors)none
inputcheckboxConsent (106 vendors)none
inputcheckboxConsent (106 vendors)none
inputcheckboxConsent (31 vendors)none
inputcheckboxConsent (29 vendors)none
inputcheckboxConsent (76 vendors)none
#fc-preference-slider-purpose-7checkboxLegitimate interest (59 vendors)none
inputcheckboxConsent (30 vendors)none
#fc-preference-slider-purpose-8checkboxLegitimate interest (21 vendors)none
inputcheckboxConsent (57 vendors)none
#fc-preference-slider-purpose-9checkboxLegitimate interest (31 vendors)none
inputcheckboxConsent (64 vendors)none
#fc-preference-slider-purpose-10checkboxLegitimate interest (51 vendors)none
inputcheckboxConsent (14 vendors)none
#fc-preference-slider-purpose-11checkboxLegitimate interest (5 vendors)none
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-11checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-14checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-15checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-21checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-23checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-28checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-32checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-36checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-50checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-52checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-69checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-76checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-85checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-93checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-98checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-104checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-124checkboxLegitimate interestnone
#fc-preference-slider-gvl-vendor-126checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-142checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-156checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-163checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-173checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-192checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-202checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-209checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-231checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-232checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-238checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-246checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-253checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-264checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-278checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-284checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-290checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-294checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-297checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-394checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-431checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-452checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-486checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-527checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-528checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-541checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-559checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-612checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-667checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-690checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-699checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-728checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-740checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-755checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-767checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-804checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-807checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-812checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-867checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-986checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-1005checkboxLegitimate interestnone
#fc-preference-slider-gvl-vendor-1019checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-1067checkboxLegitimate interestnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-1071checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-1135checkboxLegitimate interestnone
#fc-preference-slider-gvl-vendor-1142checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
#fc-preference-slider-gvl-vendor-1391checkboxLegitimate interestnone
#fc-preference-slider-gvl-vendor-1412checkboxLegitimate interestnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputcheckboxConsentnone
inputsubmit(none)none

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

<input type="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback