Accessibility Statement

We design and build 360sites against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, which includes every WCAG 2.1 AA requirement. Every new or changed screen goes through an accessibility checklist before it ships.

Fully conformant: as far as we know, 360sites meets WCAG 2.1 level AA within the scope below, with no known exceptions. This is a self-assessment, described under “How we test”; if you find a barrier, tell us and we will treat it as a defect.

This statement covers the 360sites web platform at 360sites.io: the public pages, sign-up and sign-in, onboarding, the dashboard, the 360 Site editor, bookings and the public 360 Sites the platform renders, including those served on a creator’s own domain.

It does not cover content that creators add or configure themselves — such as the descriptions they write for their images, the captions they upload for their videos, or color combinations they choose for their site — nor third-party services that open from 360sites, such as Stripe checkout, Google or Facebook sign-in, or the video provider used in calls.

We do not know of any part of 360sites, within the scope of this statement, that fails a WCAG 2.1 level A or AA success criterion. Whether a creator’s images and videos are described and captioned depends on that creator: 360sites offers a description field for the images they publish on their 360 Site and in posts, and a captions field for every video they upload, but does not make them mandatory. Videos embedded from YouTube or Vimeo use that platform’s captions.

This statement is based on a self-assessment, without an independent third-party audit. In October 2026 we reviewed the source code against WCAG 2.1 AA and fixed what we found: form field contrast, page titles, landmarks and headings, a pause control for video backgrounds, form errors and autofill, keyboard alternatives to dragging, visible focus, text contrast and focus handling in dialogs. We then closed the remaining gaps: a pause control for rotating pop-ups and banners, keyboard focus that stays inside every 360 Site dialog, text alternatives and captions for creator media, and a few minor issues with roles, translated labels and target sizes.

Every change is now checked automatically: an accessibility linter, accessibility tests on our shared components, contrast tests on our color tokens, and axe scans of the home page, sign-in and sign-up, onboarding, the 360 Site editor, a public 360 Site with its rotating pop-ups and its contact dialog open, and booking, in light and dark themes. As of 19 October 2026 those scans report no serious or critical issues.

360sites is built to work with recent versions of Chrome, Safari, Firefox and Edge and with the accessibility features of iOS, Android, Windows and macOS. We have not tested it with every assistive technology.

If you find a barrier on 360sites, or you need information from the platform in a different format, write to info@my360sites.com. Tell us the page address, what you were trying to do and the browser or assistive technology you use. We will reply and, when we cannot fix the problem right away, help you complete what you needed by another route.