Please DM or email me these documents. Thank you.

Hi, just adding on to the colorblind asks. So, for me being color blind, but not black and white. I struggle when there isn’t enough contrast between colors of lines meant to communication meaning. Here’s a couple ideas to help:

1. So, understanding that there is a limit is important. You could notify when the color scheme will cause problems for people that can’t differentiate the colors accurately.
2. For much of my diagramming, I actually make the line segments thinker as more pixels can help me distinguish the color better. This could be a great toggle for styling to help with productivity.
3. In a similar vein as number 2, styling to a limited set of dash styles can help augment the styling to help.
4. In other products like Splunk, mouse overs from the legend to highlight the corresponding line in a graph is helpful. Technically, they cause the others to fade. It’s still slower to consume, but does help. In this case, it has the benefit of really helping presenters or readers to consume a diagram even if they aren’t colorblind in some form.

Hope that helps.

Thanks @chaocipher for the feedback! We will make sure to consider this as we continue to make improvements to accessibility in our products!

Please provide an Accessibility Statement for Lucid, including company strategy for accessibility, an accessibility audit report from an independent third party and any relevant future plans. 

Thanks for reaching out Debbie! I will message you with more details!

Please let me know if a VPAT with 508 and WCAG 2.1 or 2.2 is available.  We are looking to have documentation ahead of the April 2026 deadline.  Thank you

Hi all! I’m Micah, Lucid’s community manager, and I’m excited to share several updates relating to accessibility in our products.

First, I’d like to share a heartfelt thank you for your engagement and insights you’ve shared in this conversation. Your time and thoughtfulness have done a lot to help us understand what you’d like to see when working in Lucid. We couldn’t, and wouldn’t want to, do it without you! 

New accessibility hub and Lucidspark Voluntary Product Accessibility Template (VPAT)

Now, you can find all information and resources on accessibility, including Lucid’s official accessibility statement and compliance information, at lucid.co/accessibility. Additionally, you can follow the instructions on this page to access the Lucidchart and new Lucidspark VPAT. 

Take a look at this post to learn more about these updates:

Thank you for your feedback here, ​@Ria S, ​@amcallisterocad , ​@ruviwije  , ​@Pamela J , ​@gcander , ​@David , ​@JoshMCCKC  , and ​@Debbie Ginsburg !

Status update on other accessibility-related requests

In addition to the VPAT, this thread contains other feedback and feature requests for accessibility features. This is tremendously important to us! We're happy about the progress we're making with accessibility, and while we've not built all of these features, our product team will incorporate these insights as we move forward. We’d like to provide the following status updates:

• Screen reader support (requested by ​@Ria S  , ​@KCatterall  ): We’re thrilled to support this! Find comprehensive information about this in our Use a screen reader in Lucid article from our Help Center. 

• Dark mode/high-contrast mode/colorblind-friendly mode (requested by ​@k.kompaniets, ​@Aileen C  , ​@Rob F , ​@Tomo  , ​@mduran  , ​@chaocipher ): these modes are currently not on our roadmap. Workarounds and further context are available within this thread:

However, our product team is exploring a solution of using patterns as color fill for shapes, which may help with these use cases. When we’re able, we’ll provide an update in this thread:

Finally, you may also find it helpful to utilize accessibility best practices in this Make Lucid documents more accessible article from our Help Center. In particular, Themes allow you to style your document with darker or higher contrast visuals. For more information on how to use this tool, please refer to this Apply preset themes to style shapes in Lucidchart article.

• Voice command integration (requested by ​@Ria S): While Lucid doesn’t officially support specific voice command software, we do follow accessibility standards that enable a better experience for voice command (Semantic HTML elements, descriptive labels, and ARIA when necessary.) Additionally, we recently added a user setting to disable single character hotkeys so that speech input users can say single characters without accidentally triggering hotkeys.

• “Simple” UI (requested by ​@rafaalb07  ): We’d love to hear more about this! While we don’t have immediate developments here to share, we’re eager to learn more about what specific elements you’d like to see in this experience via this community’s Product Feedback space. 

In order to provide clarity on your feature requests and feedback moving forward, we plan to close this larger thread and manage requests about accessibility improvements individually. This will allow us to better provide status updates as we continue to make progress. We’re happy to close this latest round of development with VPAT and screen reader support, and for all other outstanding requests described above, we’ll continue to manage them separately in this community’s Product Feedback space.

Note: If you are a user on a FedRAMP account, please use this form to share any feedback or feature requests.