WCAG 2.2 success criterion 2.4.1 Bypass Blocks (Level A)
Keyboard and screen reader users need a way past the header and menu on every page. Without a "Skip to content" link they must press Tab through dozens of menu links before reaching the post. A skip link that points at an ID that does not exist is worse: it is there, it gets pressed, and nothing happens.
Who it affects: Keyboard, screen reader and low-vision users — every visitor meets the page title, language, landmarks, keyboard focus, target sizes and zoom settings on every page.
Checked in review mode's Whole page tab, on the rendered page. It looks for a skip link among the first three items that take keyboard focus: a link to #something. If there is none, that is a warning when the page also has no main landmark, and a tip when it has one. If the skip link points at an ID that is not on the page, that is an error.
Add a "Skip to content" link as the first focusable item, pointing at the id of the element that wraps the main content (for example href="#main" and <main id="main">). Most accessibility-ready themes include one, and WordPress adds one automatically to block themes whose templates use a <main> element; it can stay hidden until it receives keyboard focus.
This check is free. Open any post, choose Accessibility in the admin bar, then the Whole page tab: Lumtera checks the page as your browser renders it, theme, menus and footer included, one page at a time. Lumtera Pro also checks on a daily or weekly schedule, fetching up to 25 key pages and templates from the server as a logged-out visitor, for pages that have neither a main landmark nor a working skip link, and emails you (or posts to Slack) when a new error appears.
All 64 checks, the editor sidebar, Elementor panel and site report — free, with no account and no page limits.