For about twenty years, website accessibility was told to companies in a fairly predictable way. It was presented as an "ethical choice with side benefits" — do a good deed by including people with disabilities, and as a side effect get some SEO advantage, some usability improvement for everyone, and a nice image of an inclusive brand. It was a frame that pushed accessibility into the drawer of medium priorities — useful, to be considered when time is found, certainly to be tackled sooner or later. That drawer, for the vast majority of SMEs, stayed closed.
That frame no longer describes reality. In recent years the European regulatory structure has transformed digital accessibility from a choice into an obligation, with a scope of application that is significantly broader than many companies think. The European Accessibility Act — EU Directive 2019/882, transposed in Italy with Legislative Decree 82/2022 — became operational in 2025 with obligations that extend from large companies to private SMEs, exempting only micro-enterprises (fewer than ten employees and annual revenue not exceeding two million euros). The administrative sanctions provided in Italy for non-compliance reach up to forty thousand euros, and beyond the sanction dimension there's the reputational and commercial one that the regulation indirectly activates.
The operational consequence is simple: an Italian SME that today plans its website, its e-commerce platform, its application, or that has a newly designed one, must build it accessible from the start. Not as an ethical choice, not for brand positioning, but because it's the legal requirement. The companies that treated accessibility as a postponable theme find themselves today in an exposed position. Those that kept building sites without accessibility are building assets that the regulation considers non-compliant.
This is the first level. There's a second level, equally important, concerning how the digital system is evolving: search engines, generative AI systems, social platforms have progressively integrated accessibility signals into their algorithms for evaluating and distributing content. A non-accessible site isn't only non-compliant with the regulation — it's also a site that's read worse by the machine, distributed worse by the algorithms, cited less by generative AI systems when a user asks for information about the sector.
Accessibility is therefore today both a regulatory requirement and a concrete commercial variable. Treating it still as an "ethical choice with side benefits" is a wrong reading of the context.
What "accessibility" of a site really means
It's worth articulating what "accessible site" concretely means, because the generic version of the concept leaves whoever receives it without real operational tools.
Digital accessibility is the property of a site, an application, a digital service of being usable by people with different cognitive, physical, sensory characteristics, through different tools, in different contexts of use. People with visual disabilities use screen readers that read the site's content aloud — a site that isn't correctly structured is for them literally unreadable. People with motor disabilities use the keyboard or pointing systems alternative to the mouse — a site that requires specific mouse gestures excludes them. People with hearing disabilities don't hear audio or video content without subtitles or transcriptions — a site that relies only on audio to convey information excludes them. People with cognitive disabilities or specific learning disorders need content structured with clarity, comprehensible visual hierarchies, direct language — a chaotic or overloaded site is for them an obstacle.
The technical reference standard is the Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium. The current version is 2.2, while WCAG 3 is in development. The WCAG articulate accessibility on four fundamental principles:
Perceivable. The information and the interface components must be presented in ways that users can perceive through at least one of their available senses. Images must have alternative text descriptions, videos must have subtitles, audio must have transcriptions, the contrast between text and background must be sufficient for legibility even with reduced vision.
Operable. The interface and navigation must be usable with different tools. Everything must be accessible from the keyboard, interaction times must not be limiting, content must not provoke adverse reactions (flashes, animations that trigger epileptic seizures), navigation must be comprehensible and predictable.
Understandable. The site's content and the interface's functioning must be understandable. The language must be identifiable, the language must be appropriate to the target audience, interfaces must behave in predictable ways, the user's errors must be identifiable and resolvable.
Robust. The content must be compatible with present and future assistive technologies. The code must be standardized, semantic, well-structured, so that tools like screen readers, alternative keyboards, voice-recognition systems can interpret it correctly.
Three progressively more stringent levels of compliance are defined by the WCAG: A (minimum level), AA (standard level, the one European regulations typically refer to), AAA (maximum level, relevant only for specific contexts). The operational target for most sites is the AA level.
The regulatory perimeter, articulated for what it is
It's worth articulating precisely what the European regulation requires today, because there's a lot of confusion on this point and companies often think they aren't involved when in fact they are.
The European Accessibility Act applies to a set of digital and physical products and services. As regards digital, it covers among other things: e-commerce platforms, banking services for consumers, digital books and e-readers, passenger transport services, telephony services, self-service terminals (ATMs, automatic ticket machines), on-demand audiovisual communication services. It applies to all companies that place these products or services on the European market, regardless of their location — even non-EU companies operating on the EU market are involved.
The only total exemption from the obligations is for micro-enterprises that provide services: companies with fewer than ten employees and annual revenue or total balance sheet not exceeding two million euros. All other companies — small, medium, large — are subject to the obligations.
Products and services placed on the market after 28 June 2025 must be accessible from the moment they're placed. For products and services already present on the market before that date and not substantially modified, a transitional period until 28 June 2030 is provided for adaptation. Five years that may seem long but that require structured planning, because making an existing site accessible is work that can take months.
The sanctions for non-compliance in Italy, according to the current regulatory framework, can reach up to forty thousand euros. To these must be added the indirect consequences: challenges by associations protecting the rights of people with disabilities, reports that can reach the institutional channels, reputational damage in the case of public findings, possible litigation with users who find themselves excluded from your services.
To this is added the Legge Stanca (Law 4/2004 and subsequent amendments), which obliges Italian public administrations to make their sites accessible and which now extends its reach through Legislative Decree 82/2022.
In summary: accessibility for the vast majority of Italian companies is today a regulatory obligation, not an option. Understanding it is the first step. Planning its implementation is the second.
The commercial dimension: accessibility as a market variable
There's an operational dimension that many companies underestimate, and that is probably more relevant than the sanction dimension in the medium term: accessibility has become a concrete commercial variable.
The actual audience is broader than it seems. People with disabilities in the world are about fifteen percent of the population, but the number of people who benefit from accessible systems is significantly larger. Elderly people with reduced vision. People with temporary disabilities (an arm in a cast, an injured eye). People in non-optimal contexts of use (a site consulted under strong sun, with audio in a noisy environment, with a slow connection). Non-native speakers who struggle with complex content. The audience potentially impacted by accessibility is much broader than just the target with recognized disability.
Search engines reward accessibility. Accessibility practices — well-structured semantic HTML code, alternative descriptions of images, clear content hierarchies, contained loading times, comprehensible navigation — partly overlap with the practices that improve SEO ranking. An accessible site is generally a site that search engines read better, understand better, index better. Investing in accessibility produces returns also on these concrete commercial metrics.
Generative AI systems read accessible sites better. This is a new dimension that many companies haven't yet internalized. When a user asks a generative AI system for information about a sector or a product, the system looks for information in sites it can read well. Sites with a clear semantic structure, with correctly labeled content, with appropriate metadata are read more easily and cited more frequently. Sites with a disordered structure, with content not semantically labeled, with a dependence on visual elements not described textually are read worse and cited less. For companies starting to cover so-called GEO (Generative Engine Optimization), accessibility is an integral part of the strategy.
The user experience improves for everyone. An accessible site is generally a clearer, more navigable, faster, more organized site. These characteristics don't produce value only for users with disabilities — they produce value for all users, and they translate into concrete commercial metrics: time spent on the site, conversion rate, user satisfaction, reduction of the abandonment rate.
Brand positioning evolves. In a cultural context where companies are evaluated on the consistency between declared values and operational practices, accessibility is one of those dimensions where misalignment is easily visible. A company that talks about "inclusion" and "social responsibility" while maintaining a non-accessible site sends contradictory signals that the contemporary public reads with greater attention than it did in the past.
How to make a site accessible, in practice
The operational approach to making an existing website accessible or to designing a new accessible one is articulated on specific levels. It's worth naming them without going into technical details that would require specialist skills, but with enough precision to orient the decisions of those who lead a company.
Initial accessibility audit. For an existing site, the first step is to understand the current level of accessibility and identify the areas of non-compliance. This is done through a combination of automatic analysis tools and specialist manual review. Automatic tools — WAVE, Axe, Lighthouse, and others — identify a significant portion of the problems but not all of them. Manual review, ideally with the involvement of testers with real disabilities, identifies the problems that only actual use by users with assistive technologies can detect.
Progressive adaptation of content. Existing content can be progressively adapted: adding alternative descriptions to images, subtitles to videos, transcriptions to audio, review of color contrast, reorganization of the semantic structure of the pages. It's work that can be distributed over time but that requires attention and discipline.
Technical code review. For many sites, reaching WCAG compliance requires interventions on the HTML, CSS, JavaScript code. Correct semantic structures, keyboard navigability, ARIA attributes where appropriate, predictable behavior of interfaces. It's work that requires specific technical skills, and companies often discover that their web-development vendor doesn't have consolidated accessibility skills.
Testing with real users. Automatic tools and manual review give a technical assessment. Testing with users who use assistive technologies in daily life — blind people who use screen readers, people with motor disabilities who use only the keyboard, and so on — produces information that no automatic audit generates. It's an investment that few make and that makes the difference between technical accessibility and substantial accessibility.
Ongoing maintenance. Accessibility isn't a project that ends with the launch of the compliant site. Every content update, every new functionality, every design change can introduce new accessibility problems. Structuring the publishing and development processes so that accessibility is systematically verified is essential to maintain compliance over time.
Accessibility statement. European regulations provide that companies subject to the obligations publish an accessibility statement accessible from the site, in which they declare the level of compliance reached, any areas of non-compliance, ways to contact the company in case of problems. It's a formal document with specific requirements, not a generic informational page.
A practice to avoid: overlays
It's worth dedicating specific attention to a practice that many companies are discovering as an "easy solution" and that the accessibility community evaluates critically: accessibility overlays. They're toolbars or widgets that can be added to an existing site with a JavaScript script, and that promise to make the site accessible with one click — generally through a menu that lets the user modify contrast, text size, and other display settings.
The commercial promise of these solutions is seductive: contained payment, quick installation, "WCAG compliance" reached in minimal time. The operational reality is more complex, and deserves to be known.
Overlays can offer some superficial functionalities of visual adaptation, but they don't solve the structural accessibility problems that require interventions on the code and the structure of the site. People with real disabilities, who already use their own assistive technologies (screen readers, alternative keyboards, magnification software), in many cases don't use overlays — indeed, overlays can interfere with the functioning of their technologies. The community of people with disabilities has published critical statements toward these solutions, and many accessibility lawsuits in the United States have involved sites that used overlays believing they were compliant.
The operational message is clear: overlays aren't a shortcut to compliance. They can be used as a complement to a site that is already structurally accessible, never as a substitute for the real work of accessibility.
What AI tools have changed for those tackling accessibility
AI has significantly changed the economics of accessibility work in recent years. It's worth articulating the changes, because some companies are ignoring real operational advantages.
Automatic generation of alternative descriptions. The images of a site can be processed by AI vision models that generate alternative text descriptions. The descriptions require human review for accuracy and contextualization, but the starting point is today much faster than it was even just five years ago. For sites with thousands of images, this radically changes the sustainability of the intervention.
Automatic transcription of audio and video. Voice-recognition technologies today produce professional-quality transcriptions for most audio content in the main languages. For subtitling videos, AI has made accessible at minimal cost work that until recently required dedicated transcribers.
AI-assisted accessibility audit. Automatic audit tools have become more sophisticated thanks to the integration of AI components that identify accessibility problems more subtle than those traditional tools captured. Specialist human verification remains indispensable for the most contextual problems, but the automatic filter has improved significantly.
Generation of accessible code. AI-assisted development tools can generate code that integrates accessibility practices by default — correct semantic structure, appropriate ARIA attributes, correct handling of keyboard navigation. For companies developing new sites or new functionalities, the cost of accessibility "done well from the start" is significantly reduced compared to the past.
Ongoing monitoring. The accessibility of a site can be monitored in an automated and ongoing way, with alerts when changes are introduced that compromise its compliance. It's a level of vigilance that five years ago required significant investments and that today is accessible as a service.
What remains human — and indispensable — is the dimension of specialist judgment, of understanding the needs of real users, of verifying the actual experience. But the volume of repetitive technical work that absorbed most accessibility interventions is progressively automatable, freeing resources for higher-value activities.
Website accessibility has left the phase in which it was a strategic choice with its own implementation timing. It has entered the phase in which it's a system of obligations and market standards that apply regardless of the company's will. The companies that have understood this are building compliant digital presences, readable by search engines and AI systems, accessible to a broader audience than the one they served before. The companies that keep treating it as a "theme to tackle when we have time" are finding themselves exposed: to sanctions, to challenges, to the loss of visibility on the digital channels that progressively reward accessibility as a quality variable.
The operating rule is simple. If your company falls within the perimeter of the European Accessibility Act — almost all Italian companies above the micro-enterprise threshold — accessibility is today an obligation, and the investments to make it effective are part of ordinary planning, not extraordinary. If your company is exempted from the direct obligations (micro-enterprises), accessibility nonetheless remains a commercial variable that the digital system rewards, and ignoring it means leaving value on the table for reasons that no longer hold up.
The moment to seriously tackle the accessibility of your site isn't "sooner or later." It's now. The companies that tackle it with structured preparation build digital assets that work better on multiple dimensions at the same time. Those that postpone it accumulate technical debt that becomes progressively more costly to pay off.