Skip to content Todd Libby

Enough with "Dark Patterns" Already!

This Isn't Going To Go Over Well

and I couldn't be any more invested in wanting to have a contentious debate about it. If you disagree, you disagree. Think long about it before contacting me. Just because it doesn't directly affect you doesn't mean it doesn't affect someone else. That goes for anything in this world.

Your Naming Conventions Are Suspect

"The colors black and white have long carried opposite connotations. Black has connoted evil and disgrace, while white has connoted decency and purity."
Longshore, D. (1979). Color Connotations and Racial Attitudes. Journal of Black Studies, 10(2), 183–197. http://www.jstor.org/stable/2784327 *

The history of the term "dark patterns" as far as I can tell goes back to 2010 when Harry Brignull, a UX designer set up darkpatterns.org, a resource to highlight patterns and anti-patterns on the web.

Brignull since then has rebranded his site to deceptive.design in an attempt to use a more inclusive term for the practice of deception and deceiving users.

Many articles can be found if you search for the term "dark Pattern" and some even highlight Brignull and his steering away from a term that is exclusionary and harmful. These articles want to "stick to calling them dark patterns" because "the term dark pattern has more traction" to quote one article.

To quote Kim Crayton, "Tech is not neutral." and "Unremarkably mediocre white dudes" it sure isn't and I am one of those unremarkably mediocre white dudes.

Then Why Are YOU Writing This Article?

White guys doing white guy things, since tech was built by white guys and is white guy majority in the spots where all the decisions are made and how things are run, it's not surprising that white guys want to still carry this torch (not a tiki torch, although it might as well be) to the end. I mean, look at the numbers from a poll in the 2020 StackOverflow Developer Survey. The numbers don't lie, friend:

A StackOverflow poll showing 68.3% of developers that responded to the survey were of white or European descent while the remaining were 10.4% South Asian, 7.6% Hispanic or Latino/a/x, 4.9% Middle Eastern, 4.6% East Asian, 4.5% Black or African descent and the same for Southeast Asian, 1.7% multiracial, 1.2% biracial, and 0.8% Indigenous such as Native American, Pacific Islander, or Indigenous Australian.

I'm writing it to maybe, perhaps, get at least one person to change and if one changes because of this article or the work that I am doing, then I've done my job but I won't rest with that as the accepted result. "Dark pattern" is problematic.

Tech is not neutral and it is political. So if you have lasted this long let's get into why this thinking is problematic and what I propose we do as a community of "professionals" on the web (I sometimes read the bird site and wonder how some people can be called "professionals").

It is 2023 and we are still, in most places with most people, using the word "dark" when it comes to anti-patterns on the Web. Why? Is it because some white dudes just do not want to embrace change, as they always carry themselves to do?

Is it because we, as a white society, or a society as a whole, we do not wish to embrace the change of a language that has the worst of meaning, origin, and racism?

Your naming conventions are highly suspect.

Racists are usually uncomfortable talking about racism. They immediately curl up like a cat cornered in a bathroom thinking you are going to throw it into the tub full of water. So when I see white dudes in my travels online, especially in the Twitterspace, they are usually recoiling in self-defense when the issue of race or racism is involved in the conversation.

Sorry to burst your little tech bubbles kids, but the Web is political. Programming is political. Accessibility is political. Your job is political. Tech is political.

"Why do we have to bring politics into this?"

Oh, you didn't know?! Tech is political. Therefore, the impetus of me writing this article is to address one of those little corners of our world. User Experience (UX) and the use of the term, "dark patterns". You can agree to disagree and move on with your day, I know I will with people who disagree.

"This has nothing to do with master/main"

They sure as hell do.

Change came around from the usage of the word "master" and GitHub made the change. "Slave" is another term that has been mentioned. There are a lot of problematic terms associated with tech because tech was founded by a group of unremarkably mediocre white men.

Dark isn't just a word in the dictionary, oh no. It is also been known to have designated racial groups since the days when this country was "founded". Along with black, dark and black was the norm and their connotations may well reinforce social norms pertaining to those groups(*).

The reasoning behind the usage of the term can be anywhere from, "What does it matter? I don't see anything wrong with it." to "Why do people overreact to everything these days? Why can't people not look into everything with a microscope?"

White dudes automatically go on the defensive letting people know about the discomfort they are feeling and they look to others cut from the same cloth for comfort. For validation and for support. That's a huge part of the problem.

Why stray from the norm? Why change something that has been "industry standard" since they started their web careers? Fear. Fear of change and fear of being inclusive. So the reasons don't matter, just as long as their discomfort gets them what they want.

There are reasons. The history of the United States, the history of Black people and other people that are underrepresented on and in the Web. The words that have negative connotation towards a select group of people. It doesn't have to be "every" single group of marginalized and underrepresented folks.

We have all heard about it. We all have our biases and opinions, and yet we still, as an industry, clutch to our stringed pearls when someone wants to change something for the betterment of good and inclusion and accessibility.

Deceptive. It's Okay To Use The Word. Honest!

I'm a child of the seventies. I grew up with people that would tell me to suck it up and get used to it. That's the kind of attitude I see permeate through tech to this very day. Especially with the white guys. It's the entitlement. It's the air of ego and of that they are the "alpha male".

Whether they want to admit it or not, I had to. I had to look inward at myself and the way I conducted myself and the things I said and wrote. It's been a twenty year process. It has been all about change.

Change the words, change the attitudes, change the ego, swallow your pride or drown. It's okay to use the word "deceptive", it really is.

I've seen and heard the term thrown around loosely. Loosely as in here and there around Twitter and other places and writings. But never really seeing it take hold in the mainstream. Why? It's time to sunset the old "dark" term and use something that does not invoke negative connotations, words, thoughts, inflections. Period.

Andy Vitale brought up the subject in 2020 and this made me pause then think. There needed to be some kind of change. I agreed with Andy in his tweet, I even think we briefly discussed it but cannot find the tweets (maybe in a DM?).

It's Moved Into The Mainstream

Media outlets online pick up on articles and the terminology fast and they write and publish articels at the same rate. "Dark" has permeated the search engines and we need to change this.

I can see many articles that specifically use "dark" in its headline. "FTC Report Shows Rise In Sophisticated Dark Patterns Designed to Trick and Trap Consumers" for one. Even Wikipedia has an entry for this.

It's time to get rid of the language. Whether it is "deceptive design patterns", "deceptive patterns", "Anti-patterns" or something else. We need to remove "dark" from the terminology. It doesn't make sense to begin with. "Dark" may be because of "perception" to some people, but perception is only a small fraction of what a UX pattern that either harms with intent or without intent really is.

Patterns that harm people, whether it is neurodivergent folks, people with cognitive issues, people with lack of quality education or who have a learning disability are anti-patterns with those patterns that are without intent, deceptive patterns with intent behind them.

Definition Is Everything

According to Dictionary.com, dark is:

adjective, dark·er, dark·est.

  1. having very little or no light: a dark room.
  2. radiating, admitting, or reflecting little light: a dark color.
  3. approaching black in hue: a dark brown.

noun

  1. the absence of light; darkness: I can't see well in the dark.
  2. night; nightfall: Please come home before dark.

verb (used with object)

  1. to make dark; darken.

verb (used without object)

  1. Obsolete. to grow dark; darken.

Why are we using "dark"?! There is no sense to it whatsoever. A "deceptive pattern" or an anti-pattern designed to trick users, whether it is with or without intent, is deceptive. It is a deceptive practice.

Not "dark" like Halloween spooky or scary, not without light, not due to color or light. None of those. None!

My Current Work Behind Deceptive Patterns

Leaving the social and political debates aside, I have brought the term to the W3C in our quest to recognize spots in WCAG that need to be filled. Enter the Framework for Accessibile Specification of Technologies (FAST).

Those patterns or anti-patterns that are used to trick users. Those patterns and anti-patterns that cause harm whether with or without intent. Because it happens in this day and age whether we want to acknowledge it or not. It is there.

The challenge here is filling those gaps because there could be a thousand different use cases to fill a gap. It's work, a lot of work. It's work that I am willing to do though. User needs and functional needs are being carefully looked at and thought about. The group working on this has worked hard to get to the point where we have gotten to and there is more work to be done.

  • blacklist/whitelist
  • master/slave
  • native feature/built-in feature
  • dummy/sample
  • man hours/engineer hours
  • Black Hat/White Hat
  • Grandfather Clause

These terms have been looked at for needing to be changed and there are a lot of articles that can be found here if you're not convinced like I am after doing my research.

Just Stop Already

Stop using "dark". It's easy to do. Maybe it is not easy for those that are still using "master" in their git repos or those that cling to the Indigenous mascots that "aren't hurting anyone" in sports/schools, or those that do the tomahawk chop in Atlanta or at Florida State University, or in Kansas City. If you're resistant to change, because "words is words" than quit reading this and go on with your day. If it's made you think a little, I challenge you to think more and think harder.

People can do this. We are capable of adaptating and change. We're in a world that is so divided but the fact of the matter is we all have to be here until we are not. So why not make it a lot more inclsuive and a lot more accessible for everyone instead of being a remarkably mediocre white dudes game? For anyone else who isn't white, how easy is it for you just to adopt a new term that reflects a change?

Disagree. That's Your Right

You can read this article and say to yourself, "What a load of bullshit. This guy has no idea of what he's talking about." That's your right and that's your opinion and you're entitled to that opinion. Notice I bolded the word "entitled". I did that for a reason. What may not affect you, may affect others. So before you go sounding off on your soapbox on a tangent about how it is not racist (nor do I ever mention it is racist, I mention the connotation of racism).

A great article here by Shaun Morris mentions at the end:

Ironically many opposing changing the terms have the same mindset as those who oppose Agile: resistance to change. “This is how it has always been”. In fact the Agile Manifesto asks us to be “Responsive to Change over following the Plan.” Isn’t systemic racism after 400 years a plan worth changing? In the National Football League, many people did not understand why Colin Kaepernick took a knee during the National Anthem. Today, many are beginning to understand him. Many technologists are looking at changing the terminology and subsequently the culture. Similar to Kaepernick’s situation, many people do not understand why they would want to change technical terminology. Instead there will be outrage at the suggestion. “Imagine the amount of work will take”. “We are going way too far with this”. “People are too sensitive”. Before you rush into judgment I ask you to consider why people are asking for changes. Some will affectively end the conversation and dismiss the core issue outright. Remember underrepresented people do not get the choice to dismiss the core issue of bigotry and systemic racism. It comes when we are out on a casual walk (Elijah McClain) or on a jog (Ahmaud Arbery). It comes when we are sitting in a car (George Floyd). It comes in the dead of night while we are a sleep (Breonna Taylor). It is no respecter of our location. It does not discriminate in favor of our time or convenience. Underrepresented people do not have the choice to dismiss this core issue and go back to work or coding. This type of change gives framework leaders the opportunity to clearly articulate that they support zero tolerance for racism and bigotry.

So you can still disagree, or you can do your research. I did. Inclusivity and accessibility means everyone can be welcome and feel like they belong, not just a select few.

And as the NCSC's Technical Director Ian Levy says in this article:

"If you’re thinking about getting in touch saying this is political correctness gone mad, don’t bother."