Exercise 3: Why One Heading Structure Serves Both Accessibility and SEO — Possible Solution ==================================================================== WHAT web-accessibility1-2 BUILT HEADING HIERARCHY FOR ------------------------------ Per this chapter, web-accessibility1-2 taught heading structure — one clean h1, logically nested h2/h3 underneath, no skipped levels — specifically to support screen-reader users navigating a page by landmark. A screen reader can jump directly between headings, and a consistent, logical hierarchy is what makes that navigation genuinely useful rather than confusing. WHAT THIS CHAPTER USES THE SAME STRUCTURE FOR ------------------------------ Per this chapter, "the exact same structure a screen reader relies on to understand a page's own outline is what a crawler uses to understand which content is the main subject versus a subsection." A crawler reading a page's headings is doing something structurally identical to a screen reader's own navigation — extracting an outline of the page's own organization from the heading tags, in order to figure out what the page is really about and how its content is organized. WHY THE UNDERLYING NEED IS THE SAME FOR BOTH ------------------------------ Both a screen reader and a crawler face the identical problem: neither can visually see and instantly grasp document structure the way a sighted reader looking at font sizes and layout can. Both instead rely entirely on the semantic heading tags themselves to reconstruct that structure programmatically. Since the actual need — "give me a reliable, non-visual way to understand this page's own outline" — is identical in both cases, the same solution (clean, logically nested headings) satisfies both needs simultaneously. WHY NO SEPARATE MARKUP APPROACH IS NEEDED ------------------------------ Per this chapter's own finding-box, "nothing about the markup changes here — the accessibility win and the SEO win come from the identical heading structure, built once." Because both consumers (screen reader, crawler) are reading the same HTML heading tags in the same way, there is no conflict to resolve and no separate accessibility-only or SEO-only version of the markup to maintain — one correctly structured set of headings serves both purposes without compromise on either side. WHY THIS WORKS AS AN ANSWER ------------------------------ It identifies the shared underlying need (a non-visual way to reconstruct page structure) that both a screen reader and a crawler have, and explains why satisfying that one need with correct heading markup automatically satisfies both the accessibility and SEO purposes at once, rather than requiring two separate implementations.