Hacker News Reader

Comment by simonw | Hacker News Reader

What's the accessibility story for Unpoly?

I'm always interested in ways of building partial page fetches, dropdown menus etc in a way that is thoroughly tested to work well with common screenreaders.

I'd love to see a frontend framework that includes detailed documentation (and ideally video demos) demonstrating how effective their ARIA screenreader stuff is.

View on HN

Unpoly lead dev here

Unpoly takes special care to always move the focus to the next relevant element in an interaction. E.g. when a link updates a fragment, the focus is moved to that fragment. Or when an overlay is closed, focus is returned to the link that originally opened that overlay.

More details can be found here: http://triskweline.de/unpoly2-slides/#78

Feel free to install a screen reader and play with the demo app (https://demo.unpoly.com/).

Probably the right place to ask this:

The slide said

> DEMO OF SERVER-SIDE APP ISSUES

> Link to demo app (https://demo.unpoly.com/)

> (press Start Classic on first page)

but there is no “Start Classic”?

The slides are out of date, both when they talk about the demo and in API details.

This is excellent - thanks for the reply. Those slides answered my question really well, and it looks like you've put a lot of thought into this.

Why would the story be different than SPAs? The screenreaders read final html in the browser. It shouldn't matter if comes from server rendered template OR javascript template rendered on the client.

Seems like it depends on how you code the html/templates not how they are rendered?

SPAs very often have terrible accessibility. I think it's important for frameworks that help people build interactive applications (SPA or otherwise) to provide the best possible defaults, plus guidance as to how to use them to build accessible interfaces.

Reply on news.ycombinator.com