Web Adapter

[floers]

I would like to see a web adapter and I could start working on it. I couldn't find whether there is some ongoing work somewhere so I wanted to ask to make sure there is no duplicate work going on.

Also if someone has any hints for me how to approach this I would be grateful.

[DataTriny]

Hello @floers,

Yes, we have started working on an adapter for the web that you can find on the web-basics branch. It is already quite capable though I haven't touched it in a few months so I would have to check before assessing its exact state.

Would you be interested in taking it over?

[floers]

@DataTriny Based on the web-basics branch I created an example slint app that generates its elements in the dom. So far so good. I am trying to understand how to deal with user input but so far I am stuck. The common lib includes types for user Actions thus I guess there is some infrastructure in accesskit that already receives user input (in my case made via slint) and sends it to accesskit. But Wouldn't I need this the other way round? When a user uses a screen reader to press the DOM button this event needs to get to the slint UI... I am confused on how this should (or even can) work. Could you help me or give me some pointers?

[floers]

Nvm. I kept thinking about this and I got it. I need the action_handler not to implement it but to use it to send actions. I add a (js) on_click handler to a created dom button element which delegates the click via the action_handler. It seems to work fine.

[DataTriny]

Hello @floers, hello @drewcrawford,

Happy to see that this generates interest from both of you, and sorry for not replying before. We don't have an AccessKit matrix space but you can reach out to me in a more direct way there: @DataTriny:matrix.org.

@floers I think you are on the right track with the action handler. I also wanted to try the web adapter with Slint, so I'd be interested to see what you've got.

[floers]

@DataTriny I just pushed my current state here: https://github.com/floers/accesskit/tree/web-basics. In examples/slint-web is a simple slint app and axum web server to host it. You can run it via just wasm && just run (or see the justfile). You can use the browser console to e.g. click a button via JS or set text to the input and send a changed event and the slint app changes accordingly. I think now it is just some tedious work to implement all elements.

I also started with a setup for automated tests that ensure each element is usable via selenium/web driver.

[DataTriny]

I just tested it and it is not usable with a screen reader as is. Moving the focus is unreliable, but I don't know if this is an issue on the Slint side. Cool demo though!