|
Top-level
 @zensaiyuki Rhapsode is amongst those screenreaders: <nav> is silenced & it automatically skips to <main>. And UI buttons arbitrarily shuffling around is especially bad when navigating the page with a TV remote! I can't let it happen! Though I will be happy to allow partial page refreshes akin to Intercooler.js. 5 comments
@alcinnz the base html form language is pretty good at expressing semantically what the form is/wants. it’s even a great API definition language, even if the apis amit describes are boring and old fashioned. ideally stuff like css/javascript is only used to enhance the experience- the forms *should* work with javascript and css fully disabled. but as we all know, they typically don’t. @alcinnz but, assuming they did, they fulful the promise of a self describing API. all a client needs to do is understand the html form and it can present any sort of UI it needs to, to fully interact with the api the form describes. it’s really under appreciated how great a design it is. @zensaiyuki Absolutely! Now can I make it a reality? The struggle ofcourse is the majority of forms which like to define their own widgets, there's no way I'll be able to handle that... |
Gregory's Server
@zensaiyuki Forms meanwhile are a very interesting design space for me!
I might struggle to verbalize some/many forms in the wild, but with some minor HTML extensions there's opportunity to build Alexa-level conversational UIs! Though not as many as some may think due to HTML5.
TVs meanwhile needs those forms rendered to their own menus.
In either case I have to seperate forms out into their own mode & disallow styling to make them function well in these mediums.