We keep talking about digital accessibility as an optional nice-to-have that gets tacked on at the end of a project if there is budget left, if the client insists, or if an audit happens to land badly. Meanwhile, SEO has been benefiting from it for fifteen years, user experience has always depended on it, the law now imposes it on private companies as well as the public sector, and agentic AI systems just discovered what screen reader users already knew. Strange.<\/p>\n\n\n\n\n\n\n\n
Over my 18 years of experience in this field, I have observed one constant: HTML semantics, the thing I was taught as an obvious given and have been repeating ever since, is the only skill that benefits everyone at the same time. Everyday people. People with disabilities, who need a genuinely accessible web. And now machines, Google yesterday, AI agents today.<\/p>\n\n\n\n
The way I approach this topic will inevitably be through my own lens: that of a front-end developer turned UX designer, then accessibility auditor, who ended up writing two books on the subject. (more on that later)<\/p>\n\n\n\n
Let\u2019s walk through, or walk through again, four areas where accessibility has already proven its worth: SEO, user experience, GEO and the agentic experience, and finally the legal and professional landscape, which just shifted under our feet.<\/p>\n\n\n\n
How do you define HTML semantics without turning it into an entire course? One image is enough. Picture a warehouse where every box carries a precise label: \u201cfragile,\u201d \u201cstackable,\u201d \u201copen first,\u201d rather than just another anonymous box among many.<\/p>\n\n\n\n
Semantic HTML is exactly that. A Over my years of experience in this field, I have observed one constant: that label, once applied correctly, benefits three audiences that have long been treated separately. Search engines, which have always read it to index your pages. People who navigate differently, by keyboard, by screen reader, or simply with different display needs. And, more recently, AI agents, which have to decide where to click on your behalf without ever seeing your interface. These are the three areas we will walk through now, in that order.<\/p>\n\n\n\n So what really connects accessibility and search engine optimization? The same skeleton of tags.<\/p>\n\n\n\n I have been interested in code quality as a source of SEO data for a long time. As early as 2015, I was already documenting the value of schema.org microdata<\/a>, a vocabulary distinct from accessibility but built on the same idea: giving your markup structured meaning rather than leaving it flat, to help search engines understand what they are reading. Accessibility and HTML semantics follow a similar logic, with a different starting goal, usability by humans and assistive technologies, but with an identical side effect: the reference documentation<\/a> on web accessibility confirms it, search engines \u201cgive more weight to keywords contained in titles, links, etc., than to keywords contained in non-semantic A clean heading hierarchy, an Tip: next time someone sells you accessibility and SEO as two separate projects with two separate budgets, ask about the Let\u2019s move to another often-overlooked aspect. I am sometimes asked to choose between a beautiful form and an accessible form. The question itself is the problem.<\/p>\n\n\n\n My audit of ten WordPress form plugins<\/a> shows this plainly: I advised plugin developers to \u201cget into accessibility and get trained, because it is going to become a selection criterion,\u201d and the finding, plugin after plugin, was the same. Labels not linked to their fields. Error messages poorly announced, or not announced at all, to screen readers and other assistive technologies, yet perfectly visible to an everyday visitor (if there happens to be one at that exact moment \ud83d\ude03). Border contrasts at 1.74:1 when the recommendation is 3:1. These are not isolated accessibility flaws. They are usability flaws, plain and simple, that penalize a visually impaired person just as much as someone in a hurry on mobile in bright sunlight.<\/p>\n\n\n\n That is the whole point of a genuine accessibility audit<\/a>: it does not just tick WCAG boxes, it reveals usability problems that affect everyone. A form that cannot be navigated by keyboard is a form that will block disabled users just as much as power users who rely on the keyboard out of habit. Since when do we want frustrating experiences for our users?<\/p>\n\n\n\n Navigation that is inconsistent for a screen reader is often just as inconsistent for a sighted eye, which simply compensates with more visual cues. Want to start auditing your own forms right now? Check your labels, your contrasts, your error handling, your keyboard navigation. These are the same four points that come up, again and again, in my analyses.<\/p>\n\n\n\n A form is the beginning of a conversation. Not a data collection exercise where all the effort falls on the person answering. And a failed conversation, in writing, cannot be fixed on the fly.<\/p>\n\n\n\n And here comes a new chapter. Over the past few months, everyone has been discovering GEO, Generative Engine Optimization (optimizing to be cited by generative AI rather than ranked in a list of blue links). And guess what shows up there, once again.<\/p>\n\n\n\n A recent GEO guide<\/a> puts it plainly: \u201cif it is hard for AI engines to access (slow loading times, poor HTML structure, lack of markup), it risks going unnoticed.\u201d And further down, in the same list of technical factors: \u201ccompliance with accessibility standards (contrast, keyboard navigation, alt text) opens your site to all audiences and strengthens its machine readability.\u201d<\/p>\n\n\n\n To understand why, picture this. Imagine every web page has an invisible twin, an accessibility tree, the structure browsers build behind the scenes to give every element a role, a name, and a state. Screen readers have always used it to navigate without ever seeing the page. AI agents, those new tools that crawl the web, fill out forms, and click on your behalf, just discovered they can use it in exactly the same way. They do not see your beautiful design. They read the structure.<\/p>\n\n\n\n The CEO of Deque Systems, an accessibility tools vendor since 1999, sums up<\/a> the shift underway: agentic AI bots now account for more web requests worldwide than humans themselves. And meanwhile, according to the WebAIM Million 2026 report cited there, 95.9% of home pages still contain detectable accessibility failures. See the problem. We are building a web increasingly read by machines that need structure, on foundations that still do not have any.<\/p>\n\n\n\n \u201cAccessible for humans becomes visible for AI,\u201d as one marketer quoted by Deque put it. A maxim that has the merit of being true, and one that should be enough to convince those for whom the ethical argument alone was never enough to move the needle.<\/p>\n\n\n\n (I am not saying ethics should need a business argument to matter, but if one is needed, here is a remarkably effective one \ud83d\ude42)<\/p>\n\n\n\n Between us, it is not as if accessibility professionals had not been shouting for decades that this would need to happen eventually. Back in 2022, while testing WordPress form plugins, I was already writing to the teams building them that a \u201cEuropean Directive with the pleasant name European Accessibility Act is going to take effect sometime in 2025.\u201d In 2024, in an article on inclusion, I noted that the EAA \u201crequires its member states to adopt an accessible design approach by 2025.\u201d<\/p>\n\n\n\n Also in 2022, I was warning on LinkedIn that designers and developers needed to train up for their own employability, and I even wrote a series of books about it. I was also warning about the dream sellers and hot air merchants who were about to flood the market: accessibility overlays<\/a>, weekend auditors, and consulting firms \u201cspecialized in accessibility since 2025\u201d \ud83e\udee3<\/p>\n\n\n\n What concretely changes for the private sector: consumer computers and smartphones, ATMs and payment terminals, telephony services, banking services, transport, e-commerce, e-books. This is no longer the narrow scope of the public sector we had gotten used to. It is the private sector, broadly, now falling within the scope of a legal obligation, with designated enforcement authorities in every member state to make sure it is respected.<\/p>\n\n\n\n And just as I predicted, the dream sellers and hot air merchants have indeed flooded the market.<\/p>\n\n\n\n In short, if your profile as a designer or developer does not include accessibility skills, it will not just be less good. It will be out of compliance, and maybe even out of the market.<\/p>\n\n\n\n Ready to step outside your professional comfort zone? Because there is an angle we still do not talk about enough: accessibility as a hiring argument.<\/p>\n\n\n\n The most recent studies from France Travail (the 2026 BMO survey<\/a>) put the recruitment difficulty rate in digital roles at around 49.5%, compared to 43.8% across all sectors combined.<\/p>\n\n\n\n The main reason? Difficulty finding qualified profiles.<\/p>\n\n\n\n I will let you calculate what that means at the scale of every large company that will have to comply with the EAA now and over the coming years, on products already on the market that benefit from a transition period until 2030. One more string to your bow, let\u2019s say.<\/p>\n\n\n\n Let\u2019s recap. SEO has benefited from semantics since Google has existed. User experience has always depended on it, accessibility or not. GEO and AI agents just discovered an accessibility tree that screen readers have been walking through for, what, 20 years?<\/p>\n\n\n\n The law, meanwhile, has stopped asking for your opinion since June 28, 2025. And the job market is slowly starting to fall in line behind all of this.<\/p>\n\n\n\n I am deliberately laying it on thick in this article, but the reality has been there for a long time: most of the time, we do nothing but relegate accessibility to the rank of nice-to-have, when it is the only cross-cutting skill that serves everyday people, disabled people, and now the machines reading the web on your behalf, all at once.<\/p>\n\n\n\n You might tell me the topic is too vast, that it would take months to cover it properly. And you would be right. But at the same time, that only reinforces my point: this is not a project to keep postponing.<\/p>\n\n\n\n So, as a designer or developer, what is the most recent skill you have picked up in your field? And more importantly: does building up your skills in digital accessibility not sound like a good plan for what comes next?<\/p>\n\n\n\n We keep talking about digital accessibility as an optional nice-to-have that gets tacked on at the end of a project if there is budget left, if the client insists, or if an audit happens to land badly. Meanwhile, SEO has been benefiting from it for fifteen years, user experience has always depended on it, the […]<\/p>\n","protected":false},"author":4,"featured_media":8981,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_bluesky_dont_syndicate":"","_bluesky_syndication_accounts":"","_bluesky_syndication_text":"","footnotes":""},"categories":[656,658,776],"tags":[],"coauthors":[597],"class_list":["post-8983","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-seo","category-the-blog","category-user-experience"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t<button><\/code> says \u201cI am actionable.\u201d A <nav><\/code> says \u201cI am a path to somewhere else.\u201d An <h2><\/code> says \u201cI structure the content, I am not just bigger than the text around me.\u201d A <div><\/code> on its own says nothing. It waits for meaning to be given to it, or it just serves as a decorative element.<\/p>\n\n\n\n<\/a>SEO: semantics has been paying off for a long time<\/h2>\n\n\n\n
<div><\/code>s.\u201d<\/p>\n\n\n\nalt<\/code> attribute that actually describes the image, a link label that says where it leads rather than a vague \u201clearn more,\u201d these are exactly the same elements a screen reader and an indexing bot will look for to understand your page. This is not a happy coincidence. It is the same information, structured once, consumed twice.<\/p>\n\n\n\nalt<\/code> text, the single <h1><\/code>, the explicit link text. You will get the same answer on both sides.<\/p>\n\n\n\n<\/a>User experience: accessible means usable, for everyone<\/h2>\n\n\n\n
<\/a>GEO and the agentic experience: the same semantics, for new readers<\/h2>\n\n\n\n
<\/a>What the EAA officially changed, since June 2025<\/h2>\n\n\n\n
<\/a>What it earns you, very concretely<\/h2>\n\n\n\n
<\/a>What if we had to conclude?<\/h2>\n\n\n\n
<\/a>Sources & Resources<\/h2>\n\n\n\n
\n