This episode of the Jukebox Podcast (WP Tavern) features Jessica Lyschik, who argues that creating accessibility-ready WordPress themes is far more achievable than many developers assume. Recorded at WordCamp Europe 2026, the conversation breaks down why accessibility matters, where to start, and how recent changes in WordPress (especially block themes) make the work simpler.
Who is Jessica Lyschik?
Jessica has been part of the WordPress community since the mid-2000s and has worked professionally in the ecosystem since 2015. Over time she taught herself accessibility practices, contributed to theme reviews, and now helps other developers translate accessibility guidelines into practical, repeatable steps.
Why accessibility matters (beyond the legal side)
Jessica frames accessibility as both a moral obligation and a practical advantage. Making sites work for people with different abilities is the right thing to do, and it can also expand your audience and even increase sales. She pointed out a modern twist: AI agents and automated assistants rely on correctly structured HTML and semantic markup to parse and interact with sites. If your site is built accessibly, it’s easier for both assistive technologies and future AI agents to read and act on content—so accessibility can improve discoverability and functionality in new ways.
The common fear and the documentation gap
Many theme developers are put off by the phrasing of the WordPress “accessibility-ready” requirements. The rules can read as cryptic or incomplete because they describe what must be achieved without always explaining the specific technical steps. Jessica recommends clearer documentation that maps requirements to concrete HTML/CSS practices. When explained plainly—use main, header, footer, proper heading order, visible focus styles, etc.—these items are often straightforward to implement.
Low-hanging fruit: quick wins you can do now
Jessica shared practical changes that make a big difference and are quick to implement:
– Add meaningful alt text to all images (available in the Media Library or directly in block settings).
– Ensure links are visually distinguishable (for example, detectable underlines or clear contrast).
– Implement skip-to-content links so keyboard and assistive technology users can bypass repeated navigation.
– Use semantic HTML elements: main, header, footer, nav, and correct heading levels (H1, H2, H3 sequence).
– Add aria-labels to icon-only buttons so their purpose is announced by screen readers.
These are measurable, low-effort improvements that, once built into a theme or workflow, prevent a lot of future rework.
Why block themes make accessibility easier
Block themes shift responsibility for some accessibility details to Core. If you use the right blocks and configure template parts correctly, WordPress outputs appropriate markup and handles things like accessible search and comment forms. For example, assigning a group block as your site’s main content or using the header/footer template parts means proper semantic tags are generated automatically. That reduces the manual work required in classic themes and makes it simpler to ship accessible defaults.
Build accessibility in from the start
A recurring point: adopt accessibility as a habit early in development. Fixing issues after a site is built can multiply the work—changing a component in one place might need to be repeated across many pages or sites. If you design accessible components and templates up front, you save time and reduce friction for colleagues who would otherwise view accessibility as a chore.
Accessibility-ready tag and the theme repository
WordPress.org provides an accessibility-ready tag for themes that meet a set of requirements (currently 18). Those requirements include things like semantic markup, keyboard navigability, and providing an accessibility.txt to describe what has been implemented. There’s even a new guideline discouraging themes from recommending or requiring plugins that aren’t accessible. However, the majority of themes in the repository don’t carry the accessibility-ready tag—only a small fraction do—so Jessica advocates for gradual improvement rather than enforcing rigid exclusion, which would be impractical given the large number of themes available.
Interdisciplinary awareness
Accessibility isn’t only a developer concern. Content creators, designers, and SEO teams should understand the basics: correct heading structure, meaningful link text, and the need for alternative text on images. While developers implement the technical side, the whole team contributes to an accessible experience.
AI agents and the future of accessibility
Jessica highlighted an emerging reason to prioritize accessible markup: AI agents. These tools parse site content to perform tasks like shopping or scheduling. They don’t “see” pages visually; they rely on semantic HTML and correct attributes. In that sense, an accessible website is easier for an agent (or assistive tech) to navigate and interact with—making accessibility investments future-proof.
Who to follow and where to learn more
Jessica recommends following accessibility-focused people and resources in and outside the WordPress ecosystem. Names mentioned include Joe Dolson, Rian Rietveld, Amber Hinds, Anne-Mieke Bovelett, and Sara Soueidan. The WCAG specification is the baseline, but it can be dense; practical tutorials, talks, and approachable guides are often more useful for developers getting started. Jessica plans to share curated links and resources to help people adopt accessible practices.
Final takeaways
– Accessibility is often easier than it looks once you translate requirements into concrete HTML and template patterns.
– Block themes lower the barrier by giving developers accessible building blocks from Core.
– Small, consistent habits—like always adding alt text or labeling icon-only buttons—prevent a lot of work later.
– Accessibility benefits real people now and also helps future tools (like AI agents) interact with your site.
For more details and links mentioned during the conversation, check the episode show notes on the WP Tavern podcast page. Jessica’s talk from WordCamp Europe 2026 is also available for viewing if you want to see her walk through the theme requirements and examples.