See title 
It would be a welcoming addition to make larger PvP battles a bit more clear.
Yes, because what Blizzard needs is more ablist color-coding excluding the 8% of people who can’t use it.
How about just putting the class/spec as a text on the health bar.
I have an addon that’ll do that as a plug-in to ElvUI. If I can manage that, surely Blizzard can.
What’s ablist?
Edit: English isn’t my first language so I didn’t quite get the message 
Ignoring the needs of folks who are unable to use mainstream whatever.
8% of human beings are colorblind. Blizzard has a long, long history of encoding information primarily or solely using colors leaving that population out in the cold.
Well, makes sense that colorblind ppl would not benefit from that. Maybe we should add 2 new options then:
- use class colors on target frame
- replace avatar with spec icon on target frame
this way everyone could benefit and it allows even more customization:)
I had an addon that just put the localized class and spec right on the nameplate in PVP.
Don’t see any reason Blizzard couldn’t offer that as an option other than their primary design constraint being punative.
Adding options to help color-sighted people play the game doesn’t prevent colorblind people from having their own options. You shouldn’t criticize color coding or any other quality of life feature just because you can’t personally use it. Instead, try to be more inclusive and request additional options for different kinds of players. Color coding itself isn’t ablist.
OP, I have the code for you:
hooksecurefunc("HealthBar_OnValueChanged", function (self)
if UnitIsPlayer(self.unit) and UnitIsConnected(self.unit) then
local c = RAID_CLASS_COLORS[select(2,UnitClass(self.unit))];
if c then
self:SetStatusBarColor(c.r, c.g, c.b)
self:SetStatusBarDesaturated(true)
else
self:SetStatusBarColor(0.5, 0.5, 0.5)
self:SetStatusBarDesaturated(true)
end
elseif UnitIsPlayer(self.unit) then
self:SetStatusBarColor(0.5, 0.5, 0.5)
self:SetStatusBarDesaturated(true)
else
self:SetStatusBarColor(0.0, 1.0, 0.0)
self:SetStatusBarDesaturated(true)
end
end);
hooksecurefunc("UnitFrameHealthBar_Update", function (self)
if UnitIsPlayer(self.unit) and UnitIsConnected(self.unit) then
local c = RAID_CLASS_COLORS[select(2,UnitClass(self.unit))];
if c then
self:SetStatusBarColor(c.r, c.g, c.b)
self:SetStatusBarDesaturated(true)
else
self:SetStatusBarColor(0.5, 0.5, 0.5)
self:SetStatusBarDesaturated(true)
end
elseif UnitIsPlayer(self.unit) then
self:SetStatusBarColor(0.5, 0.5, 0.5)
self:SetStatusBarDesaturated(true)
else
self:SetStatusBarColor(0.0, 1.0, 0.0)
self:SetStatusBarDesaturated(true)
end
end);
Just go to addon.bool.no if you don’t know how to make that into an addon.
The Human Interface Design Guidelines published more than 30 years ago specifically state that one should not encode primary information in colors for exactly this reason.
Blizzard has a long, long, long history of doing exactly that.
The LAST thing Blizzard needs is encouragement to do it some more.
Threat is STILL encoded solely as colors.
It takes something like ElvUI Black and White to interpret threat if you’re colorblind.
Again, the fact that color coding exists doesn’t prevent them from allowing for multiple options. Call people whatever -ist you want, but most people find color coding to be extremely useful. As you stated, 92% of people will be able to use color to distinguish between different things in the UI. I’ve already agreed with you that they should include more options for colorblind players, but I’m not going to stop using colors to encode information in my own interface just because you’re resentful about it.
Furthermore, color coding can be a way to mitigate other disabilities such as poor vision, illiteracy due to brain damage, etc. Every feature they add can be viewed as a way to include more people, but you choose to view it as discriminatory and exclusive somehow.
If color coding is ablist by nature, then video games themselves are ablist. They require vision, hearing, motor skills, etc. Not all people are capable of those things. For that matter, life itself is also ablist.
The OP specifically requested this feature, presumably because they would find it useful. If you would find text-based information more useful to you, then maybe you should make your own thread with that request. There’s no need to hijack someone’s thread to complain, and that’s where I’ll leave it.
1 Like
My point is that Blizzard quite often doesn’t provide multiple options.
Threat is still currently only available as a color option, for example.
Blizzard does not need encouraging “suggestions” to repeat that abysmal ablist pattern.
/console threatShowNumeric 1
Cool. I have an addon for that now, but cool.
I may dump my addons to see what that looks like in practice (and put them back after).
I can’t see any difference using threatShowNumeric 1. Still get a change in gray shade for the health bar of the target.
I personally use Omen, it’s just an objectively better display of Threat.
Mine uses a minimalist approach. Two symbols on the health bar of the enemy.
++ for full threat
± for losing threat (supposed to be plus dash - but the forums keep making it this)
-+ for gaining threat
– for on the threat table but not significant.
Bracketed by << >> if tagged by opposing faction.
Side by side indicators if you have a pet and that pet is on the unit’s threat table (a spiff that Blizzard’s system doesn’t even offer as far as I know - separate threat indicators for pet threat).
So, a tagged mob that you have no significant threat that your pet is tanking would look like this: << – ++ >>.