Hi there, we’ve got a WeWeb app that is growing in complexity, and we want to make sure it meets at least minimum standards of WCAG accessibility.
I’m looking to work with a consultant to take a look at what we have, talk through implementation of best practice in a WeWeb setting, and provide enough training to help us keep the site maintained in the future.
If this sounds like you, let me know.
You’d probably need to re-write (fork) most of WeWeb’s components to achieve somewhat of an accessibility last time I checked.
Hi @oli
Yes, I can help with making your WeWeb app WCAG-compliant. I have experience implementing accessibility best practices in WeWeb and can review your app, suggest improvements, and guide your team for future maintenance.
Lets connect on shivam76tech@gmail.com
@Broberto That’s interesting - would you be able to expand on any specific blockers around implementing accessibility best practice with the out of the box components?
@Shivam thank you, I’ll be in touch soon!
Sure, I can provide an example that should give you an idea. If you want to change the behavior inside a select, for example add an aria label to options, or wanna make something focusable in the new chat conponent, there is no way of doing this (in a sustainable way) without forking the component. Of course you can add a lot of stuff with what WeWeb offers without forks, but what is the point of having half of the app accessible when the other half is not.
This is one of the reasons why I moved to (AI assisted) coding, because of these limitations can be easily overcomed by using accessibility compliant UI libraries such as reka-ui.
That’s really helpful, thank you @Broberto! Appreciate the example and extra context.
Hi,
I can help assess where things stand and walk you through practical steps to meet WCAG standards in your WeWeb setup.
Happy to provide guidance and training so your team can manage accessibility moving forward.
You can reach out to me on my email here
Colin