I am working on my Go UI library called gooey [1] which aims to be a one stop framework to build webview/webview apps in Go and WebASM.

It started out with bindings for the DOM, Web, and Browser APIs, but as of today I now have custom Web Components support (which is a big deal considering Go's type system quirks).

Tomorrow I'm gonna polish some of the UI components and start refactoring my git-evac [2] repo management tool which is the first app using the gooey framework.

[1] https://github.com/cookiengineer/gooey

[2] https://github.com/cookiengineer/git-evac

> Components are bad for web accessibility (aria- property fatigue).

I've been using web components as a vehicle to automate and auto validate accessibility aspects as much as possible, because I think the only way to truly make things sustainably accessible is to find a way to unburden the developer by either inferring as much as possible or making validation a natural part of development rather than a separate testing cycle that will invariably cause accessibility support to become out of sync.

It sounds like you might have similar concerns. Do you have any insights to share along these lines for Gooey?

Looks great! Wish Go wasm modules were smaller.

That’s a great name.