Legge Stanca Accessibility Law in Italy: What Businesses Need to Know

The Legge Stanca Accessibility Law in Italy requires public websites and online services to be accessible to people with disabilities. Businesses that provide digital services to public bodies or operate public-facing services must understand what the law requires, which technical rules apply, and how to prove compliance.

What is the Legge Stanca accessibility law in Italy?

Legge Stanca is the common name for Italy’s accessibility law for information and communication technology. It was created to make digital tools usable by people with sensory, cognitive, motor, or neurological impairments. The law sets legal obligations for public administrations and for private parties that supply services to the public sector.

Purpose and legal alignment

The law’s purpose is to remove barriers in websites, web apps, and other digital services. It is aligned with European accessibility rules, and it refers to technical standards that mirror internationally recognised guidance such as the Web Content Accessibility Guidelines (WCAG).

Who must comply

Primary duty holders are central and local public administrations, public bodies and public companies. Private businesses must comply when they operate online services for public administrations, receive public funding, or win public contracts that require accessible deliverables.

Which technical standards apply

Compliance is judged against technical requirements published by Italy’s digital authority. Those requirements reference recognised standards for web and app content, document formats, and ICT products. WCAG is the common baseline used across Europe for conformance levels.

Key obligations businesses need to know

• Deliver accessible content that meets the applicable technical rules for web and mobile interfaces.
• Publish an accessibility statement describing conformance and known shortcomings.
• Provide a feedback and complaint channel to report accessibility barriers and request alternative formats.
• Include accessibility clauses in procurement and contracts when supplying public sector clients.
• Monitor and maintain accessibility after launch through testing and updates.

Step-by-step compliance checklist for businesses

Follow these steps to move from uncertainty to a maintainable compliance programme.

1. Run a discovery audit. Identify all public-facing sites, web apps, PDF and Office documents, online forms and multimedia files.
2. Perform an automated scan to find obvious failures. Use manual testing for keyboard access, screen reader behaviour and form labels.
3. Prioritise fixes by impact. Start with navigation, forms, headings and images without text alternatives.
4. Update policies and procurement templates so suppliers must deliver accessible outputs and provide test reports.
5. Publish an accessibility statement that lists conformance level, exceptions and a contact for feedback.
6. Set a schedule for periodic reviews and user testing with people with disabilities.

Accessibility auditing: what to require from a vendor

Ask auditors to combine automated tools and manual checks. A robust report shows:

• Which pages and templates were tested and why those were chosen.
• Which WCAG criteria were checked and the conformance level used for assessment.
• Concrete examples of failures with screenshots and steps to reproduce.
• A remediation plan that estimates effort by task and impact on users.
• Evidence of testing with assistive technologies such as screen readers and keyboard-only navigation.

Common mistakes and practical fixes

Businesses often miss simple issues that block many users. Fix these first.

• Missing or incorrect alt text on images. Provide concise, descriptive alt text or mark decorative images as null.
• Forms without labels or with placeholder text only. Use visible labels and link them to the inputs.
• PDFs and scanned documents that are images only. Supply tagged PDFs or accessible HTML alternatives.
• Video with no captions or no audio description. Add captions and offer transcripts or described versions when needed.
• Overuse or misuse of ARIA. Use ARIA to enhance semantics, not to replace proper HTML structure.

Procurement and contract clauses

Include clear accessibility obligations in requests for proposals and contracts. Require suppliers to:

• Deliver a signed accessibility conformance statement against the chosen standard.
• Provide test evidence and remediation timelines as part of acceptance criteria.
• Maintain accessibility during warranty and support periods.

Enforcement, complaints and remedies

Authorities oversee compliance and handle complaints from users. Public organisations usually must publish a contact point for accessibility problems. When a service is found non-compliant, the provider must fix issues and update the accessibility statement. Administrative measures can follow in persistent cases.

Practical scenario: a small web agency delivering a public sector site

Start the project with an accessibility requirement in the brief. Deliver a simple conformance plan: baseline audit, iterative fixes during development, final manual and automated testing, and a published accessibility statement. Include time and budget for fixing issues found during acceptance testing.

Next steps and resources

If your organisation must comply, start with a scope inventory and a basic audit. Train designers and developers on semantic HTML, keyboard access and accessible forms. Keep copies of test reports and the accessibility statement as proof of due diligence.

For technical reference, consult the Web Content Accessibility Guidelines and the technical guidance published by the Italian digital authority. Use accredited auditors for formal assessments when required by contract or procurement rules.