Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FHeading HierarchyAction293 headings, 95 skip(s)FIX
- H1 The Age
- H2 The Age
- H4 Premium skipped
- H4 More
- H3 Screening Room newsletter
- H3 Life in the ’Burbs
- H3 Mini Crossword
- H5 Exclusive skipped
- H5 Child safety
- H3 Victoria’s new child safety regulator runs into FIFO controversy
- H5 Exclusive skipped
- H5 Victorian election
- H3 One Nation entrenched as third force as Victorians adopt ‘drain the swamp’ mentality
- H5 Income tax skipped
- H3 States warned on spending binge after record tax windfall
- H5 Live skipped
- H5 Middle East at war
- H3 US to extend ceasefire with Iran; JD Vance’s peace-talks trip ‘on hold’
- H3 Latest live posts
- H3 Ceasefire extension ‘a ploy to buy time’, says Iranian advisor
- H3 US mulls financial support for UAE
- H3 US extending ceasefire with Iran at Pakistan’s request
- H5 Exclusive skipped
- H5 AUKUS
- H3 Australia’s depending on AUKUS Virginia-class subs. US says they’re not its priority
- H5 Opinion skipped
- H5 Opinion
- H3 Why Trump may yet seize defeat from the jaws of victory in peace talks
- H5 Clinton Fernandes skipped
- H5 Money Talks
- H5 AFL 2026
- H3 Hot or not: The best and worst recruits of the 2026 AFL season so far
- H5 Taste test skipped
- H3 The surprise winner of our Anzac biscuit taste test
- H5 Editorial skipped
- H5 Editorial
- H3 For the sake of a young man, someone must be held to account
- H5 The Age's View skipped
- H5 Federal budget
- H3 Labor to tackle two of budget’s biggest headaches – aged care and NDIS – at once
- H5 Analysis skipped
- H5 Start-ups
- H3 Australia’s rich-listers can’t resist the $50 billion NDIS
- H5 Colin Kruger skipped
- H5 Tax deductions
- H3 Bigger tax claims for car expenses could be months away
- H5 Property market skipped
- H3 The new property downturn only applies to one type of home
- H5 Watch skipped
- H5 Aviation
- H3 Thousands of nervous flyers come to him for help. This is what he tells them
- H5 Crime skipped
- H3 Premier lashes YouTuber who entered Dezi’s final hideout
- H5 Opinion skipped
- H5 Travel tips
- H3 The nine cities that gave me a terrible first impression
- H5 Ben Groundwater skipped
- H5 MasterChef Recap
- H3 Front-runners, dark horses and the one who will rub you up the wrong way on MasterChef
- H5 Got a Minute? skipped
- H3 Everything’s gone south since our company was acquired. Now what?
- H2 Just in
- H5 Live skipped
- H3 US-Iran war live updates: Trump says US will extend ceasefire, blockade to continue; Israeli soldiers punished for destroying Jesus statue
- H5 Updated skipped
- H3 ASX set to fall as Wall Street seesaws; US-Iran ceasefire extended; Trump’s Fed nominee grilled
- H3 Hot or not: The best and worst recruits of the 2026 AFL season so far
- H5 Exclusive skipped
- H3 Victoria’s new child safety regulator runs into FIFO controversy
- H2 Editor's Picks
- H5 Victoria skipped
- H3 It’s a beloved historic structure, but not even David Attenborough can save Flinders Pier
- H5 Letters skipped
- H5 Letters
- H3 Time is right for bold steps from Labor
- H5 Opinion skipped
- 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 Victoria
- H5 Exclusive skipped
- H5 Victorian election
- H3 Hanson dismisses accusations after One Nation members’ mass exodus from campaign
- H5 Local council skipped
- H3 Restaurants, clubs furious over 2km strip that became a $5 million council cash cow
- H5 Analysis skipped
- H5 Science
- H3 An Australian study linked vaping to cancer. Then came the international backlash
- H5 Angus Dalton skipped
- H5 Defamation
- H3 ‘Nuts’: Explosive texts in Rebel Wilson defamation case
- H5 Education skipped
- H3 The secret to the NAPLAN writing test that students aren’t told about
- H2 From our partners
- H5 domain skipped
- H3 What you get for $2 million in a $4 million suburb
- H2 WAR IN THE MIDDLE EAST
- H3 Trump expects ‘great deal’ from Iran talks as ceasefire ticks down
- H3 Arrest Netanyahu? European moves spark fresh tensions with Israel
- H5 Opinion skipped
- H3 Trump’s madcap folly leaves door open for a dangerous new authoritarian era
- H5 Peter Hartcher skipped
- H3 Iran has made Lego into a weapon to fight Trump
- H5 Exclusive skipped
- H3 Australians turn on ‘unreliable, erratic’ Trump as Iran war drags on
- H2 Politics
- H5 Defence skipped
- H3 ‘Star Wars in Australia’: This anti-drone laser system can hit targets the size of a 10¢ piece
- H5 Analysis skipped
- H5 Middle East at war
- H3 Fix the budget with more tax on gas? The world has changed since Pocock’s viral video
- H5 Mike Foley skipped
- H5 Exclusive
- H5 Political leadership
- H3 The bush seat that’s turned into an anti-Hanson battleground
- H5 Exclusive skipped
- H5 Byelection
- H3 Canavan says One Nation is just whingeing as conservatives swap preferences
- H2 Business
- H5 Analysis skipped
- H5 Gadgets
- H3 What can we expect from Apple’s next boss?
- H5 Tim Biggs skipped
- H5 Updated
- H5 World markets
- H3 ASX set to fall as Wall Street seesaws; US-Iran ceasefire extended; Trump’s Fed nominee grilled
- H5 Opinion skipped
- H5 Supermarkets
- H3 Are we being cheated on prices? ACCC and supermarkets slug it out in court
- H5 Elizabeth Knight skipped
- H5 Aviation
- H3 Qantas, Virgin launch domestic ticket deals to fill cash coffers in Iran crisis
- H2 World
- H5 Drugs skipped
- 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
- H5 Updated skipped
- H5 Japan
- H3 Major 7.7-magnitude quake hits off Japan, tsunami warning downgraded
- H2 Opinion
- H3 The cause of Elijah Hollands’ mental health episode is not the main issue
- H5 Jake Niall skipped
- H3 I was cancelled from a feminist rally. I’ve got a strong hunch as to why
- H5 Catharine Lumby skipped
- H3 Trump is an absolute disaster for the oil and gas industry
- H5 Ambrose Evans-Pritchard skipped
- H3 Love her or hate her, Melbourne needs outspoken icons like Bec Judd
- H5 Stephen Brook 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 Updated skipped
- H5 Auctions
- H3 Melbourne vendors make $1.7m selling ‘a really lovely renovation’
- H5 Construction skipped
- H3 What the reality TV renovation shows don’t tell you
- H5 Auctions skipped
- H3 ‘One of the most tightly held parts’: Expat pays $1.7m for Melbourne home
- H5 Victoria residential property skipped
- H3 Four tree-change towns that are close to Melbourne but much cheaper
- H2 Good Food
- H5 Taste test skipped
- H3 A major chain cheapie takes top spot in the supermarket Anzac biscuit taste test
- 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 Just open skipped
- H3 Tea drinkers get their just desserts at this coffee-free Japanese cafe
- H5 Review skipped
- H5 Melbourne
- H3 We join the queue to review Ginza Kagari – a spot that flies its ramen in from Tokyo
- H2 Lifestyle
- H5 Mother's Day skipped
- H3 These influential Australian mums have done your May 10 shopping for you
- H5 Sex & relationships skipped
- H3 Signs you may be a ‘placeholder partner’ in your relationship
- H5 Fitness skipped
- H3 If you’re too tired to exercise, these expert tips will get your energy up
- H5 Sunday Life skipped
- H3 ‘I was never a playboy’: Why Matteo Bocelli never traded on his famous name for love
- H5 Exclusive skipped
- H5 Sunday Life
- H3 Lisa Kudrow created one of her best characters in 1989. Now, she says it’s time for her to retire
- H2 Culture
- H5 Exit interview skipped
- H5 Reality TV
- H3 Laura Byrne worried about one thing covering MAFS. It turned out to be her favourite part
- H5 Review skipped
- H3 Feuds, conflict and how the royal family uses fashion as a weapon
- H5 Cinema skipped
- H3 Daniel MacPherson on ‘saying yes to things I probably shouldn’t have’
- H5 Vale skipped
- H3 Melrose Place and Starship Troopers star dies suddenly aged 57
- H5 ★★★★ skipped
- H5 Review
- H3 Mick Molloy’s new show is nuts – and just what we need on free-to-air TV
- 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 Money Talks skipped
- H5 AFL 2026
- H3 Hot or not: The best and worst recruits of the 2026 AFL season so far
- H5 Opinion skipped
- H5 AFL 2026
- H3 The cause of Elijah Hollands’ mental health episode is not the main issue
- H5 Jake Niall skipped
- H5 Updated
- H5 AFL 2026
- H3 Further drug test details emerge as Ollie Hollands sends loving message to Elijah
- H5 Analysis skipped
- H5 AFL 2026
- H3 At quarter-time of season 2026, this is what your club needs to fix
- H5 Jon Pierik skipped
- H5 AFL 2026
- H3 Looking forward to more: Nick Daicos happy to reprise the role of his famous father
- H5 Analysis skipped
- H5 Formula 1
- H3 Formula 1 fans, and drivers, wanted changes to the new cars. They’re coming
- H5 Tom Cary skipped
- H5 Australian rugby
- H3 Lions help RA post record $70m profit as Wallabies get good news on star duo
- H2 Have Your Say
- H3 Elijah Hollands fell through the cracks in plain sight. His case raises many questions
- H2 More in Sport
- H5 AFL skipped
- H3 Butters umpire abuse charge thrown out in bizarre scenes and ‘miscarriage of justice’
- H5 Rugby Union skipped
- H3 Lions help RA post record $70m profit as Wallabies get good news on star duo
- H5 Exclusive skipped
- H5 AFL
- H3 ‘There was a bit of chatter’: Magpie aware of Hollands talk on field
- H5 Opinion skipped
- H5 AFL
- H3 The simple change that could have helped the Blues help Hollands
- H5 Soccer skipped
- H3 City star Haaland relishes the moment as Arsenal slide continues
- H5 AFL skipped
- H3 Three players offered bans for Hawks-Suns clash; Chinese link to Tasmania stadium build bid
- H5 Athletics skipped
- H3 (Very) Fast Eddie: Another Aussie 100m runner stuns with wind-assisted 9.84s
- H5 Netball skipped
- H3 The wonder shot that left this superstar’s opponent in shock
- H2 Featured video
- H5 AFL skipped
- H3 Bartel describes tribunal process as 'absolute shambles'
- H2 Most Viewed today
- H3 Further drug test details emerge as Ollie Hollands sends loving message to Elijah
- H3 How a 2km stretch of Chapel Street became the golden mile of council fees
- H3 Former Carlton recruit charged with cattle-stealing after owner chased allegedly stolen herd
- 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 At quarter-time of season 2026, this is what your club needs to fix
- H3 Hitler complaint, rapist meeting boycott: Nepean campaign exposes One Nation dysfunction
- H5 Opinion skipped
- H3 My flight to Europe is cancelled. I’m nervous about accepting the replacement
- H3 GetUp throwing $600,000 at Trump-themed byelection campaign to defeat Hanson
- H3 Term 2 teachers’ strikes to close Victorian schools through May and June
- H2 The Age
- H3 Our Sites
- H3 Classifieds
- H3 The Age
- H3 Products & Services
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
DFavicon & BrandingAction3 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BAlt Text Quality3 of 106 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 1 image(s) |
| generic | 2 image(s) |
| too long | 8 image(s) |
Images without alt text are invisible to screen readers.
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
BLink & Button Quality1 issue(s) across 536 links and 22 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://tvguide.theage.com.au | TV guide | new tab | Add '(opens in new tab)' to text |
| https://www.drive.com.au | Drive | new tab | Add '(opens in new tab)' to text |
| https://www.theage.com.au/national/victo… | Homes in Princes Hill. | new tab | Add '(opens in new tab)' to text |
| https://www.theage.com.au/national/victo… | Life in the ’Burbs | new tab | Add '(opens in new tab)' to text |
| https://www.theage.com.au/puzzles/crossw… | Play our new Mini Crossword. | new tab | Add '(opens in new tab)' to text |
| https://www.theage.com.au/puzzles/crossw… | Mini Crossword | new tab | Add '(opens in new tab)' to text |
| http://www.bom.gov.au/vic/forecasts/melb… | MelbourneWeather forecast | new tab | Add '(opens in new tab)' to text |
| https://www.australianunity.com.au/ | Australian Unity | new tab | Add '(opens in new tab)' to text |
| https://www.domain.com.au/news/what-you-… | What you get for $2 million in… | new tab | Add '(opens in new tab)' to text |
| https://www.domain.com.au/news/what-you-… | What you get for $2 million in… | new tab | Add '(opens in new tab)' to text |
| /confidential-news-tips | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Confidential News Tips | |||
| https://www.domain.com.au | Domain | new tab | Add '(opens in new tab)' to text |
| https://www.drive.com.au | Drivedrive | new tab | Add '(opens in new tab)' to text |
| https://www.drive.com.au/caradvice/econo… | Why a damaged car could be the… | new tab | Add '(opens in new tab)' to text |
| https://www.drive.com.au/caradvice/econo… | Why a damaged car could be the… | new tab | Add '(opens in new tab)' to text |
| https://www.drive.com.au/reviews/2026-mg… | The tech-laden hybrid SUV that… | new tab | Add '(opens in new tab)' to text |
| https://www.drive.com.au/reviews/2026-mg… | The tech-laden hybrid SUV that… | new tab | Add '(opens in new tab)' to text |
| https://www.drive.com.au/caradvice/austr… | Australia and China keep gifti… | new tab | Add '(opens in new tab)' to text |
| https://www.drive.com.au/caradvice/austr… | Australia and China keep gifti… | new tab | Add '(opens in new tab)' to text |
| https://www.stan.com.au/watch/the-miniat… | Starring Elizabeth Banks and M… | new tab | Add '(opens in new tab)' to text |
| https://www.stan.com.au/watch/the-miniat… | Starring Elizabeth Banks and M… | new tab | Add '(opens in new tab)' to text |
| https://www.stan.com.au/watch/mafs-after… | Stan has your exclusive backst… | new tab | Add '(opens in new tab)' to text |
| https://www.stan.com.au/watch/mafs-after… | Stan has your exclusive backst… | new tab | Add '(opens in new tab)' to text |
| https://twitter.com/theage | new tab | Add '(opens in new tab)' to text | |
| https://www.facebook.com/theageAustralia | new tab | Add '(opens in new tab)' to text | |
| https://www.instagram.com/theageaustrali… | new tab | Add '(opens in new tab)' to text | |
| /rssheadlines | RSS | new tab | Add '(opens in new tab)' to text |
Generic link text like 'click here' doesn't describe the destination.
/confidential-news-tips ("Learn more")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
https://tvguide.theage.com.au; https://www.drive.com.au; https://www.theage.com.au/national/victoria/life-in-the-burbs-interactive-map…; https://www.theage.com.au/national/victoria/life-in-the-burbs-interactive-map…; https://www.theage.com.au/puzzles/crosswords?promote_channel=CTA_HI_ENG&utm_s…; https://www.theage.com.au/puzzles/crosswords?promote_channel=CTA_HI_ENG&utm_s…; http://www.bom.gov.au/vic/forecasts/melbourne.shtml; https://www.australianunity.com.au/; https://www.domain.com.au/news/what-you-get-for-2-million-in-a-4-million-subu…; https://www.domain.com.au/news/what-you-get-for-2-million-in-a-4-million-subu… (+16 more)
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
CColor Contrast (Screenshot)Action20 text elements analyzed, 3 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
2 contrast failures on background images/gradients
These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 The Age | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 The Age | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Editor's Picks | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 shorts | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 From our partners | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Explore | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 From Our Partners | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Have Your Say | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 More in Sport | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Featured video | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Most Viewed today | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 The Age | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Ceasefire extension … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 US mulls financial s… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 US extending ceasefi… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Latest & Breaking Ne… | 1.79:1 | 4.5:1 | #000000 | #2D3850 | Fail |
| div Latest & Breaking Ne… | 1.79:1 | 4.5:1 | #000000 | #2D3850 | Fail |
| p We’re sorry, this … | 1.18:1 | 4.5:1 | #000000 | #0A1633 | Fail |
| button Dismiss | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Skip to sections nav… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
BLighthouse Accessibility AuditsScore 82/100 — 5 failing, 23 passedREVIEW
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Chief football writer, The Age div.z3g3Y > div.vwQJl > div > p.LhCcW |
Professor of media, author div.z3g3Y > div.vwQJl > div > p.LhCcW |
Special correspondent, The Age div.z3g3Y > div.vwQJl > div > p.LhCcW |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
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.
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_e599af4ae1d98bf6e460-0 div.YzFy- > div#homepage-header-subscribe-button-piano-id > div.tp-container-inner > iframe#offer_e599af4ae1d98bf6e460-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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Exclusive div.nNhKL > div.qWp8L > div.EKPfZ > h5._77RNt |
Exclusive div.nNhKL > div.qWp8L > div.EKPfZ > h5._77RNt |
Income tax div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Live div.qWp8L > div.z3g3Y > div.EKPfZ > h5.Lxtfy |
Exclusive div.nNhKL > div.qWp8L > div.EKPfZ > h5._77RNt |
Opinion div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Clinton Fernandes div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Taste test div.nNhKL > div.qWp8L > div.EKPfZ > h5.bxWRo |
Editorial div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
The Age's View div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Analysis div.-tzWc > div.qWp8L > div.EKPfZ > h5._77RNt |
Colin Kruger div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl |
Property market div.nNhKL > div.qWp8L > div.EKPfZ > h5.bxWRo |
Watch div.nNhKL > div.qWp8L > div.EKPfZ > h5._77RNt |
Crime div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Opinion div.nNhKL > div.qWp8L > div.EKPfZ > h5._77RNt |
Ben Groundwater div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Got a Minute? div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Live div > div.bcQQs > div.AcFMr > h5.Lxtfy |
Updated div > div.bcQQs > div.AcFMr > h5._6nsXK |
Exclusive div > div.bcQQs > div.AcFMr > h5._6nsXK |
Victoria div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Letters div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Opinion div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Jenna Guillaume div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Series div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Exclusive div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Local council div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Analysis div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Angus Dalton div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl |
Education div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Domain div.qWp8L > div.z3g3Y > div.EKPfZ > h5.Kc1uy |
Opinion div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Peter Hartcher div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Exclusive div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Defence div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
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 |
Analysis div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Tim Biggs div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl |
Opinion div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Elizabeth Knight div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Drugs div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Updated div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Mass shooting div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Updated div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Jake Niall div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Catharine Lumby div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Ambrose Evans-Pritchard div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Stephen Brook 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 |
Updated div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Construction div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Auctions div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Victoria residential property div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Taste test div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
MasterChef Recap div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Just open div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Review div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Mother's Day 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 |
Exclusive div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Exit interview div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Review div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Cinema div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
Vale div.qWp8L > div.z3g3Y > div.EKPfZ > h5.bxWRo |
★★★★ div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
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 |
Money Talks div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Opinion div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Jake Niall div.z3g3Y > div.vwQJl > div > h5.VM6Jl |
Analysis div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Jon Pierik div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl |
Analysis div.qWp8L > div.z3g3Y > div.EKPfZ > h5._77RNt |
Tom Cary div.qWp8L > div.z3g3Y > div.vwQJl > h5.VM6Jl |
AFL div.qWp8L > div.z3g3Y > div.FPWpc > h5.WXkF7 |
RUGBY UNION div.qWp8L > div.z3g3Y > div.FPWpc > h5.WXkF7 |
Exclusive div.qWp8L > div.z3g3Y > div.FPWpc > h5.HlHTW |
Opinion div.qWp8L > div.z3g3Y > div.FPWpc > h5.HlHTW |
SOCCER div.qWp8L > div.z3g3Y > div.FPWpc > h5.WXkF7 |
AFL div.qWp8L > div.z3g3Y > div.FPWpc > h5.WXkF7 |
ATHLETICS div.qWp8L > div.z3g3Y > div.FPWpc > h5.WXkF7 |
NETBALL div.qWp8L > div.z3g3Y > div.FPWpc > h5.WXkF7 |
AFL 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.
ALandmark Structure36 landmarksPASS
Multiple navigations need aria-label to distinguish them for screen readers.
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
AForm Accessibility1 of 2 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #site-search | search | Search Site | for/id |
| input | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit">
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