Accessibility statement

Courtesy translation. This is an English translation of a document originally written in Italian, provided to make it readable. The Italian version is the binding one: in case of any discrepancy between the two texts, the Italian text prevails.

Social Web Automation is committed to making its website usable by anyone, including people who browse with a screen reader, by keyboard only, with enlarged text or with high contrast. This page states where we are, what has been verified and what has not.

1. Reference standard

The reference is the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, cited by the European standard EN 301 549 and, in Italy, by Law 4/2004 as amended by Legislative Decree 82/2022 implementing the European Accessibility Act.

2. Conformance status

We declare partial conformance with WCAG 2.1 AA. “Partial” is not a convenient formula: it means the criteria listed under point 3 have been verified and are met, while those under point 4 have not yet been verified with automated tools and complete manual testing.

3. What has been verified

• Alternative text: every informative image has a description; decorative ones are marked as such.
• Heading structure: one h1 per page and a hierarchy with no skipped levels.
• Form labels: every field has an associated label or an aria-label.
• Link text: no “click here” or “read more” without context.
• Page language: declared and correct on the English pages too, where it is set before the page is first painted.
• Zoom and mobile devices: content stays readable and usable up to 200% zoom and on narrow screens.
• Skip to content: every page opens with a keyboard-reachable “Skip to content” link.
• Light and dark themes: both designed, not produced by automatic inversion.

4. Known limitations

We write them down because knowing where the site is weak is more useful than a generic statement.

• Colour contrast: verified on the main surfaces, not yet on every combination of every component in both themes.
• Keyboard path: navigable, but tab order and focus visibility have not been tested page by page.
• Screen reader testing: a full cycle with NVDA, VoiceOver or JAWS has not yet been run.
• Attached documents: any PDFs generated by the services are not guaranteed to be accessible.
• Third-party content: embedded social posts, where present, follow the accessibility of the platform hosting them, not ours.

5. How to report a barrier

If something stops you using the site, write to swsdautomation@gmail.com saying which page it is and what you were trying to do. We reply within 30 days. You do not need to know the technical name of the problem: “I cannot fill in the form with the keyboard” is a perfect report.

If the answer does not satisfy you, you can turn to the Agenzia per l’Italia Digitale (AgID), which runs the complaint mechanism provided for by Law 4/2004.

6. How we improve

Accessibility is checked when a page is added or a shared component changes, not once a year. The limitations under point 4 are on the work list: when one is closed, this page changes together with the site, not afterwards.

7. Date of this statement

Written on 8 September 2026 on the basis of an internal review of the code and the public pages. It was not carried out by a third-party evaluator.