So if earnestness is to rule the day, allow me to say that my point was more serious than mere pedantry. Because most of us here are software people living highly visual environments, and because our thinking is shaped by language that disproportionally based on visual metaphors, we tend to assume that "interfaces" are necessarily visual systems. They are not. They can be auditory and even tactile. If an audio message gives incorrect, contradictory, or badly-structured information, then that's no less an interface failure than a badly-designed web page. In this case, both the audio message and the alert interface shared a common point of failure: a deep, seemingly institutional inattention to how information is presented and interpreted. In both cases, doing a better job with the interfaces is hardly rocket science; that's not the interesting part of this fiasco. The interesting part is: why didn't the institutions care about this, how did the project managers fail to spot the problems, and how should this change procurement and management practices in the future?
Hopefully that's a bit less pedantic!
Being a mod has got to be tough: you're not allowed to look away from the assholes; you're required to look directly at them. After dealing with the 10,000th jerkwad, an optimistic reading of what anyone says has got to be challenging. So divergent readings are totally understandable, and thanks for the reminder that when using flippancy or sarcasm online, it's a good idea to telegraph one's amiable intent.
https://news.ycombinator.com/newsguidelines.html