Brilliant read. I love insights like this. Been recently thinking about the 3rd point quite a bit. I've been messing around with toasts and other system-like notifications that result from user interaction and they've been feeling odd UX-wise.
I think your description perfectly sums up why it's not always good to do - it's better to keep the action/reaction localised (probably wise to approach this point on a case-by-case basis though...)
In terms of the screen readers - would that be something you'd be willing to give more examples / critiques of? I'm currently building out an Angular prototype and adding accessibility options, but rather than just check things off a list, I'd like to explore what the labels are actually doing when a screen reader picks them up, and how I can make it better :)
Brilliant read. I love insights like this. Been recently thinking about the 3rd point quite a bit. I've been messing around with toasts and other system-like notifications that result from user interaction and they've been feeling odd UX-wise.
I think your description perfectly sums up why it's not always good to do - it's better to keep the action/reaction localised (probably wise to approach this point on a case-by-case basis though...)
In terms of the screen readers - would that be something you'd be willing to give more examples / critiques of? I'm currently building out an Angular prototype and adding accessibility options, but rather than just check things off a list, I'd like to explore what the labels are actually doing when a screen reader picks them up, and how I can make it better :)
I'm always happy to check out a website, try it out and give feedback (as long as I don't have to pay to sign up :)).