Creatio is now WCAG-compliant!

Starting with version 8.2.2, Creatio conforms to WCAG 2.2 Level AA accessibility standards 🎉

We’ve published official documentation, including a VPAT (Voluntary Product Accessibility Template) here: Creatio accessibility documentation.

 

And we’re not stopping there! In version 8.2.3 and beyond, we’ll continue to roll out improvements to enhance accessibility even further. Check out Creatio release documentation for more details!

We're also preparing customization guides to help ensure that any custom solutions align with WCAG best practices.

 

This opens new opportunities in public sector, healthcare, education, and other industries where accessibility is essential.

Like 1

Like

Share

1 comments

There are many different nuances in the WCAG criteria and how to meet them. We will publish guides, starting with the usage of colors.

 

These are preliminary, simplified, and super-short rules on making your customizations accessible:

 

1. Use Freedom UI.

 

2. Use proper colors.
- Don't put dark text on a dark background or light text on a light background. Ensure that the contrast for text is greater than 4.5:1, and greater than 3:1 for images, icons, and charts that are not just decorations.

- Put a sufficiently dark desktop background image or color to keep the desktop element visible.

You can use the WebAIM Contrast Checker or myriad of other tools to check it.

 

3. Use easy-to-understand titles.

- Fill in a proper title text in every component you can in the Freedom UI page designer.
- Don't delete the page title (big text on the top left side of the page). - Don't hide the titles of inputs in the form (record) pages.

 

4. Translate texts to every language used.

It's better to work with the page where all content is in the language set in the user profile.

 

5. If you are developing more complex interactions in code or even custom components, please:

- Pay attention to operations with browser focus.

- Don't alter basic component interaction patterns.

- Use proper component names and other ARIA properties.

- Check the official WCAG documentation or other resources.

Show all comments