Can the person who suggested or implemented this masterpiece in poor UI design comment on the reasoning behind it?
Wow, you have perfect timing orioncrack!
Ironically, the UX team is getting ready to run some feedback sessions on some new designs for alerting in the next several weeks. Feel free to email me directly at kellie.mecham@solarwinds.com to learn more, set up a time to take a sneak peek at early designs, and give us your thoughts on the new concepts. We will happily take some time to fall on our swords about this page as part of that.
Thanks!
Kellie
Like many of the strange and arcane views into the dark underbelly of Alert management in Orion, it was designed to to confuse the enemy.. anyone not trained in the black arts of alert management were frightened away by the ghostly text and cryptic descriptions...
Perhaps this person was also the guy that told MS to remove the start button from Windows.
Genius.
I can see the reason clearly the 'for' - ie: those with 20/20 vision can cleanly see what is being used easier, since only those options ticked are clearly visible.
However as orioncrack points out it doesn't help all - especially when there's the attempt to adopt the Accessibility - W3C for both websites and their apps.
Here in Aus the gov has a mandatory requirement http://webguide.gov.au/accessibility-usability/accessibility/ to meet WCAG2 as also noted here Web Accessibility Initiative (WAI) - home page.
Perhaps a slightly bolder font for those being used? Or even a per user option to hide all not used (ie don't load the list of all) maybe the way to go.
They should simply revert to how it was.
Rely on the check box and keep all alert objects text black regardless of status.
I WANT to see my disabled monitors. They should NOT be hidden. They should not be barely visible gray.
