That's why I always treat designs in Figma etc. only as ideas or intended guidance for implementation, and validate them by bringing them into life as early as possible within the user's medium — the browser.
The web development community talks a lot about single-page apps, but are we all on a single page? Here's my ontology of web app architectures, organized by rendering and navigation.
I asked myself, what am I doing on my website that is so complex that needs all that JavaScript code to decide what to render and how to render on my webpage? Next.js was trying to render the webpage from the server side, so why won’t I send the HTML directly myself?
HTML event handlers are those onxxx attributes and properties many of us are used to, but do you know how they actually work? If you're writing custom elements and would like them to have such event handlers, what would you have to do? And what would you possibly be unable to implement? What differences would there be from native event handlers?
The most important mindset to adopt before talking about specific technologies, is to think about who your users are and how they will be accessing the service you're building. This should be the primary driver in your decision making, because the experiences you're building are for the users.
Common Accessibility Issues of Norwegian Mobile Banking Applications
To sum it up really quickly - not a single app conforms to Web Content Accessibility Guidelines version 2.0 (or 2.1 / 2.2) - and with that also with EN 301 549 version 3.2.1. This is perhaps not something new to people that understand the requirements and it doesn't mean that apps are totally inaccessible.
It’s been a couple of years since container queries started landing in browsers… so why isn’t anyone using them? It turns out that container queries are kinda tricky; they’re not as straightforward as media queries. In this tutorial, we’ll break it all down and make sense of them, so that you can start using them in your work.