@simon Just noting that these are nowhere near as accessible...

@simon Just noting that these are nowhere near as accessible as the built-in, non-async versions, particularly with a screen reader. A totally fixable problem, just wanted to make you aware.

Like 7 December at 20:58 | Wall-to-wall | Open on dragonscave.space

5 comments

James Scholes

@simon I see there's already https://github.com/simonw/prompts-js/issues/5, which will go a long way.

7 December at 21:01 | Open on dragonscave.space

Stuart Langridge

@jscholes @simon ah, I came to point out <dialog>, indeed :) this is entirely what it's for, and it's designed well at it

7 December at 21:46 | Open on mastodon.social

Simon Willison

@sil @jscholes I just shipped a new version that uses dialog and I think it's a lot better, but would love to hear any accessibility feedback on it https://tools.simonwillison.net/prompts-js

7 December at 22:19 | Open on fedi.simonwillison.net

Thomas Steiner :chrome:

@simon @sil @jscholes I'd engineer it by creating a set of `<template>`s for all dialog types (maybe lazily on demand even) and then `clone()` them whenever I need them. Also, I'd make them completely barebones when it comes to design, so they can fit in wherever.

8 December at 6:33 | Open on toot.cafe

Thomas Steiner :chrome:

@simon @sil @jscholes Ah, and I see you have an Issue open for this already, but you really want to allow users to only `import` the dialog type(s) they need. Given what you have, an LLM should be able to get you there.

8 December at 6:43 | Open on toot.cafe

Go Up