Accessibility

F

Heading Hierarchy

Action

98 headings, 40 skip(s)

FIX

98 headings, 40 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

H3 Regional
H2 The most important things happening in the communities you care about — straight to your inbox.Free hyperlocal news, events and conversation for 30,000 U.S. communities.
H3 Read the latest stories from Patch's team of local journalists
H6 Joliet, IL|2m skipped
H2 He Won't Stop Burglarizing Joliet Businesses, Dan's Candies, Banana Joe's His Latest Victims: Prosecutors
H6 Edison-Metuchen, NJ|2m skipped
H2 Edison Youth Sports Funding Ordinance Tabled Over Residency Rule, Missing Formula
H6 Lacey, NJ|33m skipped
H2 Fire Risk High 1 Year After Jones Road Wildfire Blazed Through 15K Acres
H6 Plainfield, IL|38m skipped
H2 Expansive Wallin Woods Development Approved Again: Here's Why
H3 Put Your Event on the Map
H6 Huntington, NY|50m skipped
H2 He Watched His Brother Get Adopted, Now Vance Is Still Waiting: Huntington Adoptable Pet Of The Week
H6 Elmhurst, IL|48m skipped
H2 Elmhurst May Face Budget Challenge With State's 'Slap In Face'
H6 Worcester, MA|55m skipped
H2 Man Stabbed Behind Worcester City Hall, Police Investigating
H6 Crystal Lake-Cary, IL|58m skipped
H2 New Menchie’s Frozen Yogurt At Water’s Edge Could Get Expanded Signage Approval
H3 Sell It Where You Live
H6 Joliet, IL|44m skipped
H2 'Yeah I Hit Him,' Foster Mom On Joliet's Manhattan Road Must Remain Jailed After Orange Incident: Prosecutors
H6 Darien, CT|1h skipped
H2 Darien To Explore Sister City Relationship In Ukraine
H6 Windsor Locks-East Windsor, CT|56m skipped
H2 Windsor Locks Dad Remembered After Tragic Drowning In Florida
H6 Banning-Beaumont, CA|1h skipped
H2 Pass Area Dogs Killed In Mountain Lion Attack: Sightings, What To Know
H3 Post a Classified in Minutes
H6 Woodbridge, NJ|40m skipped
H2 Man Accused Of Killing Rutgers Student In Wrong-Way Crash Offered Plea Deal; He's Also Wanted By ICE
H6 Haverford-Havertown, PA|1h skipped
H2 Child Services Saw Signs Of Abuse A Day Before Delco Parents Killed Toddler: Court Docs
H6 Darien, IL|1h skipped
H2 Darien Cameras 'Disgusting' Overreach: Speaker At Meeting
H6 Marblehead, MA|1h skipped
H2 Marblehead Pushes Tiered, Phased Prop 2 1/2 Tax Override To Save Staff, Services
H3 Put Your Business in the Spotlight
H6 West Orange, NJ|1h skipped
H2 West Orange Advocates Push For Local Law Limiting Cooperation With ICE
H6 Pittsburgh, PA|1h skipped
H2 Pittsburgh PizzaFest 2026: Get Details Here
H6 Great Neck, NY|2h skipped
H2 ALDI To Open New Great Neck Store Ahead Of Schedule
H6 Darien, IL|2h skipped
H2 Darien Store Caught In Crossfire Of Donation Debate
H3 Grow Local Awareness Fast
H6 Hillsborough, NJ|2h skipped
H2 Hillsborough Director Says Film-Ready Status Will Bring Boost To Area
H6 West Orange, NJ|3h skipped
H2 Proposed Tax Hike In West Orange Town Budget Sparks Criticism, Questions
H6 Milford, CT|3h skipped
H2 Milford Schools' Consolidation Plan Could Cost Over $1.4 Billion
H6 Novato, CA|2h skipped
H2 Teen Driver In Fatal Marin Co. DUI: Police Announced Charges
H3 Promote Your Event Today
H6 Rohnert Park-Cotati, CA|2h skipped
H2 Charges For Teen Rohnert Park Driver In Fatal DUI
H6 Bel Air, MD|3h skipped
H2 5th MD Location Of Private School Opens In Harford County
H6 Framingham, MA|3h skipped
H2 Amid Public Pressure, Nestlé Exec Renegs On Framingham State Speech
H6 Troy, MI|3h skipped
H2 Troy Gym Owner Appointed To Michigan Board Of Physical Therapy
H3 Put Your Event on the Map
H6 Levittown, PA|3h skipped
H2 Fox Freed From Peanut Butter Jar On Face In Middletown Twp.
H6 Eagan, MN|4h skipped
H2 Minnesota Twins Fan Wants One-Of-A-Kind Bobblehead Collection To Honor Her Late Brother
H6 Berlin, CT|4h skipped
H2 Berlin OKs $4M For Water Line, Tank Repairs
H6 Upper West Side, NY|4h skipped
H2 NJ Rescue Horse Heroically Stops Robbery In NYC
H3 Sell It Where You Live
H6 Temecula, CA|1h skipped
H2 Temecula Gas Leak Prompts Evacuations Tuesday Morning Near Vail Ranch Center
H6 Plainfield, IL|4h skipped
H2 Data Center Moratorium Imposed In Plainfield After Unanimous Village Board Vote
H6 Lacey, NJ|4h skipped
H2 Field Renamed In Honor Of Lacey Girls Softball Founder
H6 Darien, IL|4h skipped
H2 Darien Issues 375 Permits In Wake Of Storms
H3 Post a Classified in Minutes
H6 West Chester, PA|5h skipped
H2 West Chester Student Killed By Car Saved 3 Lives, Helped Heal 100 Others As Organ Donor
H6 Winnetka-Glencoe, IL|3h skipped
H2 Mother-Son Duo Host Book Drive To Expand Access For Students In Chicago
H6 Marlborough, MA|5h skipped
H2 Marlborough Animal Advocate Joins Effort To Protect Endangered Owls In Aruba
H6 Annapolis, MD|3h skipped
H2 Arrest Made After Fight Sees Several People Pepper-Sprayed: Police
H3 Put Your Business in the Spotlight
H3 Find out what’s happening in yourcommunity on the Patch app
H3 Communities Across Our Network | Everything Local
H3 Corporate Info
H3 Partnerships
H3 Support

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

No dark mode signals detected

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

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

C

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 2 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

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 10 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 Regional	14.49:1	3.0:1	#000000	#BEE0B2	Pass
h3 Read the latest stor…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Put Your Event on th…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Sell It Where You Li…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Post a Classified in…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Put Your Business in…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Grow Local Awareness…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Promote Your Event T…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Put Your Event on th…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Sell It Where You Li…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Post a Classified in…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Put Your Business in…	3.36:1	3.0:1	#049F55	#FCFCFC	Pass
h3 Find out what’s ha…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 community on the Pat…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Communities Across O…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Corporate Info	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Partnerships	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Support	20.47:1	3.0:1	#000000	#FCFCFC	Pass
title Patch - Everything L…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	18.72:1	4.5:1	#000000	#E6F4FD	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.

A

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

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

Why this matters

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

Learn more ▾

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

Source: WAI-ARIA Authoring Practices

A+

Alt Text Quality

All 137 images OK

PASS

All 137 images OK

137 image(s) with good alt text

137 images 137 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Method
community	text	none
community	search	none
community	search	none
email	email	none

A

Link & Button Quality

229 links, 5 buttons — all OK

PASS

229 links, 5 buttons — all OK

6 link(s) open in new tab without warning

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

Got: https://www.linkedin.com/company/patch-com; /us/across-america/platform; https://facebook.com/Patch; https://twitter.com/PatchTweet; https://www.linkedin.com/company/patch-com; https://www.instagram.com/patch

223 link(s) with descriptive text

229 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.linkedin.com/company/patch-c…	Careers	new tab	Add '(opens in new tab)' to text
/us/across-america/platform	Advertise on Patch	new tab	Add '(opens in new tab)' to text
https://facebook.com/Patch	Patch On Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/PatchTweet	Follow Patch On Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/patch-c…	Follow Patch On LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/patch	Follow Patch On Instagram	new tab	Add '(opens in new tab)' to text

228 links and buttons have descriptive text

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

https://www.linkedin.com/company/patch-com; /us/across-america/platform; https://facebook.com/Patch; https://twitter.com/PatchTweet; https://www.linkedin.com/company/patch-com; https://www.instagram.com/patch

Why this matters

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

Learn more ▾

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

Source: MDN target / OWASP

A

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A

Favicon & Branding

6 icon(s) detected

PASS

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Patch

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Patch ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Patch Display Mode standalone Theme Color #004C05 Background Color #FFFFFF Icons 2 icon(s)

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 25 passed

PASS

95

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
Put Your Event on the Map `section.block > div > a > h3`
Sell It Where You Live `section.block > div > a > h3`
Post a Classified in Minutes `section.block > div > a > h3`
Put Your Business in the Spotlight `section.block > div > a > h3`
Grow Local Awareness Fast `section.block > div > a > h3`
Promote Your Event Today `section.block > div > a > h3`
Put Your Event on the Map `section.block > div > a > h3`
Sell It Where You Live `section.block > div > a > h3`
Post a Classified in Minutes `section.block > div > a > h3`
Put Your Business in the Spotlight `section.block > div > a > h3`

These are opportunities to improve the legibility of your content.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Joliet, IL \| 1m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Edison-Metuchen, NJ \| 1m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Lacey, NJ \| 32m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Plainfield, IL \| 38m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Huntington, NY \| 49m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Elmhurst, IL \| 47m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Worcester, MA \| 54m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Crystal Lake-Cary, IL \| 57m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Joliet, IL \| 43m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Darien, CT \| 1h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Windsor Locks-East Windsor, CT \| 55m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Banning-Beaumont, CA \| 1h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Woodbridge, NJ \| 39m `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Haverford-Havertown, PA \| 1h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Darien, IL \| 1h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Marblehead, MA \| 1h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
West Orange, NJ \| 1h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Pittsburgh, PA \| 1h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Great Neck, NY \| 2h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Darien, IL \| 2h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Hillsborough, NJ \| 2h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
West Orange, NJ \| 3h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Milford, CT \| 3h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Novato, CA \| 2h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Rohnert Park-Cotati, CA \| 2h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Bel Air, MD \| 3h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Framingham, MA \| 3h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Troy, MI \| 3h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Levittown, PA \| 3h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Eagan, MN \| 4h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Berlin, CT \| 4h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Upper West Side, NY \| 4h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Temecula, CA \| 1h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Plainfield, IL \| 4h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Lacey, NJ \| 4h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Darien, IL \| 4h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
West Chester, PA \| 5h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Winnetka-Glencoe, IL \| 3h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Marlborough, MA \| 5h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`
Annapolis, MD \| 3h `article.styles_ArticleCard__ZF3Wi > div.styles_Card__Content__lz0WO > div.styles_Card__TextContentWrapper__ccXOQ > h6.styles_Card__LabelWrapper__e_6qr`

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.