--- title: #226 – Jessica Lyschik on Why Accessibility in WordPress... description: WordPress developer and accessibility advocate Jessica Lyschik discusses how achieving the 'accessibility-ready' tag for WordPress themes is more approachable... canonical: https://daily.dev/posts/226-jessica-lyschik-on-why-accessibility-in-wordpress-themes-is-easier-than-you-think-d1xdrjorn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: #226 – Jessica Lyschik on Why Accessibility in WordPress Themes Is Easier Than You Think | daily.dev og:description: WordPress developer and accessibility advocate Jessica Lyschik discusses how achieving the 'accessibility-ready' tag for WordPress themes is more approachable... og:url: https://daily.dev/posts/226-jessica-lyschik-on-why-accessibility-in-wordpress-themes-is-easier-than-you-think-d1xdrjorn og:image: https://api.daily.dev/og/posts/d1XDrJORN.png og:image:alt: #226 – Jessica Lyschik on Why Accessibility in WordPress Themes Is Easier Than You Think og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # #226 – Jessica Lyschik on Why Accessibility in WordPress Themes Is Easier Than You Think **[WP Tavern](https://daily.dev/sources/wptavern)** · 42 min read · 1 upvotes · 0 comments ## Summary WordPress developer and accessibility advocate Jessica Lyschik discusses how achieving the 'accessibility-ready' tag for WordPress themes is more approachable than most developers assume. She covers practical quick wins like using correct HTML semantic tags, adding alt text to images, and configuring skip-to-content links. Block themes are highlighted as significantly easier for accessibility since WordPress Core handles many requirements automatically. The conversation also touches on the 18 accessibility-ready requirements in the wordpress.org theme repository, the need for better documentation, and an interesting angle on how AI agents — like screen readers — depend on properly structured HTML to navigate and interact with websites. Jessica advocates for building accessibility in from the start rather than retrofitting it later. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What percentage of WordPress.org themes currently have the accessibility-ready tag? Roughly 1.5 percent of themes in the wordpress.org repository carry the accessibility-ready tag. Out of about 14,700 total themes, only around 270 meet the requirement, reflecting how few theme developers pursue the designation despite it being achievable with focused effort on HTML structure, alt text, and skip links. _Anyone weighing whether to pursue theme accessibility compliance can track community standards like this on daily.dev._ ### Why does WordPress make skip-to-content links so much easier in block themes than classic themes? In block themes, WordPress Core automatically generates a skip-to-content link when a developer places the content in a group block and assigns it the main HTML tag, requiring no manual coding. In classic themes, developers must build the skip link, correct HTML5 landmark tags, and accessible comment and search forms manually, making block themes significantly less error-prone for accessibility. _Developers comparing classic and block theme workflows can follow accessibility implementation differences on daily.dev._ ### How do AI agents relate to web accessibility for developers building websites? AI agents interacting with websites function essentially like screen readers, relying on correctly structured HTML, labels, and semantic markup rather than visual cues to understand and act on a page, such as completing a purchase. Because of this, sites built with accessibility best practices are better positioned for agentic browsing and shopping, and Google has stated it will focus on accessibility for AI agents. _Developers preparing sites for AI agent interactions can follow how accessibility and agentic browsing intersect on daily.dev._ ## Similar posts on daily.dev - [\#212 – Anne Bovelett on How Web Accessibility Boosts Traffic, SEO, and Revenue](https://daily.dev/posts/212-anne-bovelett-on-how-web-accessibility-boosts-traffic-seo-and-revenue-od4sapdnz) · WP Tavern · 2 upvotes · 0 comments - [WordPress Accessibility Issues That Are Getting Sites Sued in 2026](https://daily.dev/posts/wordpress-accessibility-issues-that-are-getting-sites-sued-in-2026-qyaexajrx) · SitePoint · 2 upvotes · 0 comments - [Accessibility Improvements in WordPress 6.9](https://daily.dev/posts/accessibility-improvements-in-wordpress-6-9-ycmzpcd0g) · Make WordPress Core · 0 upvotes · 0 comments - [The Person on the Other Side of the Screen](https://daily.dev/posts/the-person-on-the-other-side-of-the-screen-akolddhr5) · Medium · 1 upvotes · 0 comments --- Tags: [#html](https://daily.dev/tags/html), [#wordpress](https://daily.dev/tags/wordpress), [#accessibility](https://daily.dev/tags/accessibility) [View this post on daily.dev](https://daily.dev/posts/226-jessica-lyschik-on-why-accessibility-in-wordpress-themes-is-easier-than-you-think-d1xdrjorn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"#226 – Jessica Lyschik on Why Accessibility in WordPress Themes Is Easier Than You Think","url":"https://daily.dev/posts/226-jessica-lyschik-on-why-accessibility-in-wordpress-themes-is-easier-than-you-think-d1xdrjorn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/226-jessica-lyschik-on-why-accessibility-in-wordpress-themes-is-easier-than-you-think-d1xdrjorn"},"datePublished":"2026-07-22T13:05:33.664Z","dateModified":"2026-09-14T06:02:28.220Z","description":"WordPress developer and accessibility advocate Jessica Lyschik discusses how achieving the 'accessibility-ready' tag for WordPress themes is more approachable...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/32536ff9af4a0e7a4c40fe934894e401?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/32536ff9af4a0e7a4c40fe934894e401?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"WP Tavern","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"WP Tavern","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/9c71049d2e544dd19b21e71a45e797d4","url":"https://daily.dev/sources/wptavern"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/226-jessica-lyschik-on-why-accessibility-in-wordpress-themes-is-easier-than-you-think-d1xdrjorn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"html,wordpress,accessibility","timeRequired":"PT42M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"WP Tavern","item":"https://daily.dev/sources/wptavern"},{"@type":"ListItem","position":3,"name":"#226 – Jessica Lyschik on Why Accessibility in WordPress Themes Is Easier Than You Think"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/226-jessica-lyschik-on-why-accessibility-in-wordpress-themes-is-easier-than-you-think-d1xdrjorn#faq","mainEntity":[{"@type":"Question","name":"What percentage of WordPress.org themes currently have the accessibility-ready tag?","acceptedAnswer":{"@type":"Answer","text":"Roughly 1.5 percent of themes in the wordpress.org repository carry the accessibility-ready tag. Out of about 14,700 total themes, only around 270 meet the requirement, reflecting how few theme developers pursue the designation despite it being achievable with focused effort on HTML structure, alt text, and skip links. Anyone weighing whether to pursue theme accessibility compliance can track community standards like this on daily.dev."}},{"@type":"Question","name":"Why does WordPress make skip-to-content links so much easier in block themes than classic themes?","acceptedAnswer":{"@type":"Answer","text":"In block themes, WordPress Core automatically generates a skip-to-content link when a developer places the content in a group block and assigns it the main HTML tag, requiring no manual coding. In classic themes, developers must build the skip link, correct HTML5 landmark tags, and accessible comment and search forms manually, making block themes significantly less error-prone for accessibility. Developers comparing classic and block theme workflows can follow accessibility implementation differences on daily.dev."}},{"@type":"Question","name":"How do AI agents relate to web accessibility for developers building websites?","acceptedAnswer":{"@type":"Answer","text":"AI agents interacting with websites function essentially like screen readers, relying on correctly structured HTML, labels, and semantic markup rather than visual cues to understand and act on a page, such as completing a purchase. Because of this, sites built with accessibility best practices are better positioned for agentic browsing and shopping, and Google has stated it will focus on accessibility for AI agents. Developers preparing sites for AI agent interactions can follow how accessibility and agentic browsing intersect on daily.dev."}}]} ```