WeWeb and accessibility

Hi everyone! I’m really loving WeWeb, have been experimenting with it using various data sources and it works a charm.

I was wondering about accessibility, and I couldn’t find any related topics in the forum. From my playing around with it, it seems like most obvious accessibility requirements (as listed on Introduction to Web Accessibility | Web Accessibility Initiative (WAI) | W3C) can be built in to a WeWeb app (provided you make the effort to do so!) but I was wondering if anyone had come across any accessibility related problems when building with WeWeb? Just want to make sure I fully understand what I’m getting myself in to before committing.

Hello
I’m reopening the subject because it’s a legal obligation to be WCAG compliant :clamp: , and I’d like to know if anyone has any tips on Weweb (I’m not talking about general W3C recommendations, but about Weweb-related tools or plugins to add) for checking the compliance rate or digital accessibility deficiencies on Weweb, either continuously or when the site goes online?
Thanks in advance :grinning:

Hi @marie and @oli :wave:

We have tried to respect accessibility standards in the past, but it hasn’t been a primary focus. Most of the accessibility work will need to be done by you as the user. This includes researching the standards and implementing them using available attributes in WeWeb. Basic features like alt text for images and semantic tags are available, but for more advanced accessibility features, you’ll need to do it yourself.