Circuit aims to provide an accessible experience for all users. On this page, you can learn more about how we support accessibility, our approach to accessibility, how to report an issue, and future enhancements.
Our approach
Our approach to accessibility includes:
Following web industry standards, like WCAG Level AA
Making accessibility features and standards part of the main virtual tour experience, instead of providing a "lite" or separate experience
Working with editors to ensure content is authored with accessibility in mind
Prioritizing feedback, bug reports, or fixes related to accessibility needs
Ensuring accessibility is an ongoing part of our software development cycle
Standards
WCAG
Circuit follows the Web Content Accessibility Guidelines (WCAG), version 2.1, Level A and AA. These guidelines include a lot of the important basics of web accessibility from WCAG 2.0, such as keyboard navigation, focus management, content alternatives and adequate visual contrast, as well as more advanced standards in WCAG 2.1 such as single pointer gestures, device orientation options, and text that is more flexible according to user settings.
In many jurisdictions, this level of accessibility support satisfies legislative requirements for web accessibility.
To learn more about WCAG 2.1, check out these resources:
Web Content Accessibility Guidelines (WCAG) 2.1 official page
How to Meet WCAG (Quickref Reference) for a detailed look at each guideline
WCAG 2.1 Updates
In Q3 of 2024, we released two sets of updates to address gaps in WCAG 2.1 conformance. As a result, we support all 12 of the new A and AA criteria. For more details please consult the August 2024 VPAT (see below for how to request your copy).
For an example of recent changes, learn more about the improvements made to labels in Circuit:
Voluntary Product Accessibility Template (VPAT)
For more details on how we meet WCAG 2.0, 2.1, and 2.2, please ask for a copy of the latest VPAT from any member of our team, or email us at accessibility@madewithcircuit.com.
Creating accessible content
The Circuit CMS includes many features to help ensure we collect the content that we need to publish accessible tours.
At a minimum:
Always provide titles on your images, which are used as text descriptions. To see images that are missing titles, navigate to Images > Missing Titles in the CMS
Always provide guide card content, which acts as a fallback for multimedia
Ensure that you make use of accessibility features in any outside platforms that you're integrating with Circuit. This may include video providers like YouTube or Vimeo, or form creators like your CRM.
Check out resources like Accessibility in Writing when writing content
Keep an eye out for notes on best practices throughout the Help Centre.
Reporting a deficiency or unmet requirement
If you have any questions or concerns about accessibility in Circuit, please let us know. We prioritize bug reports related to accessibility. Any details related to devices, browsers, or content are appreciated and will help us review and replicate any issue that might be present.
To let us know, simply reach out on Intercom, or email accessibility@madewithcircuit.com directly.
Roadmap
WCAG 2.2
Circuit partially supports some WCAG 2.2 criteria but has not completed a full review of potential deficiencies or gaps. We don't currently have a scheduled timeline for 2.2 support, but expect to implement it in future.
💡 Need more help?
Send us a message and we will be happy to assist you.