AI bias
Last reviewed
May 31, 2026
Sources
29 citations
Review status
Source-backed
Revision
v3 ยท 4,673 words
Improve this article
Add missing citations, update stale details, or suggest a clearer explanation.
Suggest edit
CtrlK
Last reviewed
May 31, 2026
Sources
29 citations
Review status
Source-backed
Revision
v3 ยท 4,673 words
Add missing citations, update stale details, or suggest a clearer explanation.
AI bias refers to systematic errors in artificial intelligence systems that produce unfair, discriminatory, or skewed outcomes. These errors typically reflect and amplify existing societal biases related to race, gender, age, socioeconomic status, or other protected characteristics. AI bias can emerge at any stage of the machine learning pipeline, from data collection and labeling to model training and deployment. As AI systems have become embedded in consequential decisions about hiring, lending, criminal justice, and healthcare, identifying and mitigating bias has become one of the most pressing challenges in AI ethics and AI safety.
AI bias occurs when an AI system consistently produces results that are systematically prejudiced due to flawed assumptions in the machine learning process. Unlike random errors, which distribute unpredictably, bias introduces a directional skew that tends to favor certain groups over others. The concept encompasses both technical failures (a model that performs worse on certain demographic groups) and social harms (outcomes that reinforce historical patterns of discrimination).
The term is sometimes used interchangeably with "algorithmic bias," though the two are subtly different. Algorithmic bias refers specifically to bias introduced by the algorithm itself, while AI bias is broader, covering biases in training data, evaluation metrics, deployment contexts, and feedback loops. A perfectly designed algorithm can still produce biased results if it is trained on biased data or deployed in a biased context [1].
AI bias is not a single, monolithic problem. It manifests in different forms depending on where in the development pipeline it originates and how it affects end users. Understanding these distinctions is essential for developing targeted mitigation strategies.
Researchers have identified several distinct types of bias that affect AI systems. The following table summarizes the major categories.
| Type of bias | Description | Example |
|---|---|---|
| Training data bias | The data used to train a model does not accurately represent the population or phenomenon it is meant to model | A facial recognition system trained primarily on light-skinned faces performs poorly on darker-skinned faces |
| Algorithmic bias | The model's architecture or optimization objective introduces systematic distortions | A recommendation algorithm that optimizes for engagement amplifies sensational or divisive content |
| Selection bias | The process for choosing training examples is not random, leading to a non-representative sample | A medical dataset drawn only from urban hospitals does not generalize to rural populations |
| Measurement bias | The features or labels used to train the model are proxies that do not accurately capture the intended concept | Using arrest rates as a proxy for crime rates, when arrests themselves reflect policing biases |
| Historical bias | The training data accurately reflects reality, but reality itself embeds historical injustices | A hiring model trained on past hiring decisions reproduces the gender imbalance of the workforce |
| Representation bias | Certain groups are underrepresented or overrepresented in the training data relative to the target population | A language model trained on English-language internet text underperforms on dialects and languages spoken by smaller communities |
| Aggregation bias | A single model is applied across diverse subpopulations that have different underlying patterns | A clinical model developed on one ethnic group is applied to all patients without adjustment |
| Evaluation bias | The benchmarks and metrics used to evaluate a model do not reflect real-world performance across all groups | A model appears accurate overall but has significantly higher error rates for minority subgroups |
| Deployment bias | A model is used in contexts different from those it was designed for | A risk assessment tool designed for one jurisdiction is deployed in another with different demographics |
| Feedback loop bias | A model's predictions influence future data collection, reinforcing the original bias | Predictive policing systems direct patrols to areas with high historical arrest rates, generating more arrests in those areas |
These categories are not mutually exclusive. A single AI system can suffer from multiple types of bias simultaneously, and the interactions between them can amplify the overall effect [2].
Several high-profile cases have drawn public attention to the problem of AI bias and spurred regulatory and academic responses.
One of the most widely discussed cases of AI bias involves COMPAS (Correctional Offender Management Profiling for Alternative Sanctions), a risk assessment tool used by courts across the United States to predict the likelihood that a defendant would reoffend. In 2016, the investigative journalism organization ProPublica published an analysis of COMPAS risk scores for over 7,000 defendants in Broward County, Florida. The investigation found that Black defendants were almost twice as likely as white defendants to be falsely flagged as high risk for recidivism, while white defendants were more likely to be incorrectly labeled as low risk despite going on to commit new crimes [3].
Northpointe (now Equivant), the company that developed COMPAS, disputed ProPublica's findings, arguing that the tool was equally calibrated across racial groups, meaning that defendants assigned the same risk score had similar recidivism rates regardless of race. This disagreement highlighted a fundamental tension in fairness measurement: different fairness criteria can be mathematically incompatible. A tool can be calibrated (equal predictive value across groups) and still have unequal error rates across groups, a result sometimes called the "impossibility theorem" of fairness [4].
The COMPAS controversy became a touchstone in debates about the use of AI in criminal justice. It demonstrated that even when an algorithm does not explicitly use race as an input, it can produce racially disparate outcomes through correlated features such as zip code, employment history, and prior arrests.
In 2018, Reuters reported that Amazon had abandoned an internal AI recruiting tool after discovering that it systematically discriminated against women. The tool had been trained on resumes submitted to the company over a ten-year period. Because the technology industry is predominantly male, the historical data reflected this imbalance. The system learned to penalize resumes that included the word "women's" (as in "women's chess club captain") and to downgrade graduates of all-women's colleges [5].
Amazon's engineers attempted to correct the bias by removing explicitly gendered terms, but the system continued to find proxy signals that correlated with gender. The company ultimately scrapped the tool entirely. The case became a cautionary tale about the risks of training AI systems on historical data that embeds existing inequalities, even when the goal is to improve objectivity in hiring.
In December 2019, the National Institute of Standards and Technology (NIST) published the most comprehensive study to date on demographic differences in facial recognition performance. The study evaluated 189 algorithms from 99 developers using 18.27 million images of 8.49 million people drawn from databases maintained by the State Department, the Department of Homeland Security, and the FBI [6].
The findings were stark. For one-to-one matching (verifying that two photos show the same person), many algorithms were 10 to 100 times more likely to produce a false positive match for Black or East Asian faces compared to white faces. For one-to-many matching (searching a database for a match), African-American women had the highest false positive rates, putting this group at the greatest risk of being incorrectly identified. American Indian faces were also frequently misidentified [6].
Earlier work by Joy Buolamwini and Timnit Gebru at MIT, published in their 2018 "Gender Shades" study, had documented similar disparities. They found that commercial facial recognition systems from IBM, Microsoft, and Face++ had error rates of up to 34.7% for darker-skinned women compared to 0.8% for lighter-skinned men. The NIST study confirmed these patterns across a much larger set of algorithms and provided the most authoritative evidence to date of systematic bias in facial recognition technology [7].
In October 2019, Ziad Obermeyer and colleagues published a landmark study in Science examining a widely used healthcare algorithm that affected the care of approximately 200 million patients annually in the United States. The researchers found that at a given risk score, Black patients were significantly sicker than white patients with the same score. The algorithm had effectively determined that Black patients needed less care than equally sick white patients [8].
The root cause was a design choice: the algorithm used healthcare spending as a proxy for health needs. Because Black patients in the United States historically spend less on healthcare (due to barriers including lower insurance coverage, reduced access to care, and systemic mistrust of the medical system), the algorithm interpreted lower spending as lower need. When the researchers corrected the algorithm to predict actual health measures rather than spending, the percentage of Black patients receiving additional care increased from 17.7% to 46.5% [8].
This case illustrated how bias can arise not from malicious intent but from seemingly reasonable technical decisions. The choice of a proxy variable, healthcare costs, encoded structural inequalities into the algorithm's predictions.
Beyond these landmark cases, AI bias has been documented in numerous other contexts.
| Domain | Case | Finding |
|---|---|---|
| Hiring | University of Washington study (2024) | AI resume screening tools favored white-associated names 85% of the time; Black male-associated names were never preferred over white counterparts [9] |
| Language models | GPT-series and others | Large language models have been shown to associate certain professions, traits, and behaviors with specific genders and racial groups [10] |
| Credit scoring | Apple Card (2019) | Apple's credit card algorithm gave men significantly higher credit limits than women with similar financial profiles, prompting a regulatory investigation [11] |
| Image generation | Generative AI tools (2023-2024) | Text-to-image models generated images reinforcing racial and gender stereotypes when prompted with occupation-related terms [12] |
| Advertising | Facebook ad delivery (2019) | Facebook's ad delivery system showed housing and employment ads to racially and gender-skewed audiences even when advertisers did not target by demographics [13] |
AI bias originates from multiple interconnected sources throughout the machine learning pipeline.
Training data is the most frequently cited source of AI bias. Machine learning models learn patterns from data, and if that data reflects historical inequalities or underrepresents certain groups, the model will reproduce and often amplify those patterns. For example, if a natural language processing model is trained on text from the internet, it will absorb the stereotypes, prejudices, and cultural assumptions embedded in that text [10].
Data bias can take several forms: sampling bias (the data is not representative of the population), label bias (the labels assigned to data points reflect human prejudices), and temporal bias (the data reflects outdated social norms). Even datasets that are carefully curated can contain subtle biases if the underlying phenomena they measure are themselves shaped by inequality.
The process of labeling training data introduces another source of bias. In supervised learning, human annotators assign labels to examples, and these labels become the ground truth that the model learns to predict. If annotators bring their own biases to the labeling process, those biases propagate through the model. For instance, annotators might rate the same behavior differently depending on whether they believe the subject is male or female, young or old, or from a particular racial background.
Crowdsourced labeling, which is common in large-scale machine learning, is particularly susceptible to this problem. The demographics of the annotator pool (often concentrated in specific countries and socioeconomic groups) can shape the labels in ways that do not generalize to the broader population.
Even when race, gender, or other protected attributes are not explicitly included as features, models can learn to use proxy variables that are highly correlated with these attributes. Zip code, for example, is closely correlated with race in the United States due to historical patterns of residential segregation. Similarly, first name, educational institution, and even browser type can serve as proxies for demographic characteristics. Removing protected attributes from a dataset, a practice sometimes called "fairness through unawareness," is therefore insufficient to eliminate bias [14].
Feedback loops occur when a model's predictions influence the very data that is later used to retrain or evaluate it. Predictive policing provides a clear example: if an algorithm directs police to neighborhoods with high predicted crime rates, officers in those areas will make more arrests, generating data that appears to confirm the algorithm's predictions and leading to even more patrols in the same areas. The result is a self-reinforcing cycle that concentrates enforcement on specific communities regardless of the underlying crime rate [15].
Similar feedback loops can occur in hiring (where biased screening leads to a workforce that reinforces the model's existing preferences), content recommendation (where engagement-optimized algorithms create filter bubbles), and credit scoring (where denied applicants cannot build the credit history needed to improve their scores).
Quantifying fairness is a prerequisite for measuring and mitigating bias. Researchers have developed a range of formal fairness metrics, each capturing a different aspect of equitable treatment. The following table describes the most commonly used metrics.
| Metric | Definition | Intuition |
|---|---|---|
| Demographic parity (statistical parity) | The probability of a positive outcome is the same across all groups defined by a protected attribute | Selection rates should be equal regardless of group membership |
| Equalized odds | True positive rates and false positive rates are equal across groups | The model should be equally accurate for all groups, both in correctly identifying positives and in avoiding false alarms |
| Equal opportunity | True positive rates are equal across groups (a relaxation of equalized odds) | Qualified individuals should have an equal chance of being correctly identified, regardless of group |
| Calibration | Among individuals assigned a given risk score, the actual outcome rate is the same across groups | A score of 70% should mean a 70% chance regardless of the individual's group membership |
| Predictive parity | The positive predictive value (precision) is equal across groups | Among those predicted positive, the actual positive rate should be the same across groups |
| Individual fairness | Similar individuals should receive similar predictions | Two people who differ only in their protected attribute should get the same outcome |
| Counterfactual fairness | The prediction would remain the same if the individual's protected attribute were different | Changing someone's race or gender in a counterfactual scenario should not change the model's decision |
A critical finding in the fairness literature is that many of these metrics are mutually incompatible. In particular, demographic parity, equalized odds, and calibration generally cannot all be satisfied simultaneously unless the base rates are identical across groups. This is known as the impossibility theorem of fairness, and it means that practitioners must make explicit value judgments about which form of fairness to prioritize in a given application [4].
Efforts to reduce AI bias span the entire machine learning lifecycle and can be categorized into three broad phases: pre-processing (before training), in-processing (during training), and post-processing (after training).
Data auditing involves systematically examining training data for representation gaps, labeling inconsistencies, and proxy variables. Organizations like the Data & Trust Alliance have developed standards for data provenance and bias assessment. Structured documentation practices, such as "datasheets for datasets" (proposed by Timnit Gebru and colleagues in 2018) and "data cards" (developed by Google), provide standardized templates for recording the origins, composition, and known limitations of training datasets [16].
Diverse and representative datasets can reduce representation bias. This may involve oversampling underrepresented groups, collecting new data from diverse sources, or using synthetic data generation to balance the dataset. However, simply increasing diversity does not address all forms of bias, particularly historical bias embedded in the labels themselves.
Re-weighting assigns different weights to training examples based on their group membership, giving more influence to underrepresented groups during training. Sampling techniques such as oversampling minority groups or undersampling majority groups can achieve a similar effect.
Fairness constraints add mathematical penalties to the model's loss function that discourage discriminatory outcomes. For example, a constraint might penalize the model for having different false positive rates across racial groups. These constraints allow practitioners to trade off a small amount of overall accuracy for improved equity across groups.
Adversarial debiasing uses a technique inspired by generative adversarial networks. A primary model is trained on the prediction task while an adversary model simultaneously attempts to predict the protected attribute from the primary model's predictions. The primary model is penalized for making it easy for the adversary, encouraging the model to produce predictions that are independent of the protected attribute [17].
Fair representation learning transforms input features into a representation space where the protected attribute is less predictable, while preserving the information needed for the task.
Threshold adjustment modifies the decision thresholds applied to a model's outputs. For example, if a hiring model produces a score between 0 and 1, different cutoff thresholds can be applied for different groups to achieve equalized odds or demographic parity.
Reject option classification allows the model to abstain from making a decision when the prediction falls in an ambiguous region, deferring to human judgment for borderline cases.
Calibration adjusts the model's output probabilities to ensure that they are equally well-calibrated across groups.
Several open-source toolkits have been developed to support bias detection and mitigation in practice.
| Tool | Developer | Description |
|---|---|---|
| AI Fairness 360 (AIF360) | IBM (now an LF AI project) | An extensible toolkit offering over 70 fairness metrics and 13 bias mitigation algorithms covering pre-processing, in-processing, and post-processing stages [18] |
| Fairlearn | Microsoft | A Python package for assessing and improving fairness, with visualization dashboards and mitigation algorithms including exponentiated gradient and threshold optimization [19] |
| What-If Tool | An interactive visual tool for exploring machine learning model behavior across different subgroups, integrated with TensorFlow and available in Jupyter notebooks [20] | |
| Aequitas | University of Chicago | An open-source bias auditing toolkit that generates fairness reports for classification models across multiple metrics and group definitions [21] |
| Responsible AI Toolbox | Microsoft | A suite of tools including error analysis, interpretability, fairness assessment, and causal inference dashboards [22] |
| Learning Interpretability Tool (LIT) | Google PAIR | A visual, interactive tool for understanding model behavior across text, image, and tabular data, supporting fairness analysis through slicing and aggregate metrics [23] |
These tools have been widely adopted in both industry and academia. AI Fairness 360, for example, includes algorithms such as optimized preprocessing, reweighing, adversarial debiasing, reject option classification, disparate impact remover, learning fair representations, equalized odds post-processing, and the meta-fair classifier. It supports models trained in popular frameworks like PyTorch and TensorFlow [18].
AI bias has become a central focus of AI regulation efforts worldwide.
The EU AI Act, which entered into force on August 1, 2024, takes a risk-based approach to AI regulation. High-risk AI systems, including those used in employment, credit scoring, education, and law enforcement, must meet strict requirements for data quality, bias testing, and documentation. The Act requires that training, validation, and testing datasets be "relevant, sufficiently representative, and to the best extent possible, free of errors and complete." Providers of high-risk systems must implement technical and organizational measures to detect and correct bias [24].
The US lacks comprehensive federal legislation on AI bias, though several sector-specific and state-level measures have emerged. The Equal Employment Opportunity Commission (EEOC) issued guidance in 2023 on the application of Title VII of the Civil Rights Act to AI-based hiring tools. Colorado's AI Act (SB 24-205), signed in May 2024, was the most comprehensive state-level regulation, requiring developers and deployers of high-risk AI systems to use reasonable care to avoid algorithmic discrimination. However, enforcement was stayed by a federal court on April 27, 2026, following a lawsuit by xAI and intervention by the US Department of Justice, which challenged the law on constitutional grounds. A replacement bill, SB 26-189, was signed on May 14, 2026, pending rulemaking [25][27].
New York City's Local Law 144, which took effect in July 2023, requires employers using automated employment decision tools to conduct annual bias audits and publish summary results.
The landmark AI bias lawsuit Mobley v. Workday reached critical milestones in early 2026. In February 2026, a federal court in California certified the case as a nationwide collective action on age discrimination claims and authorized notice to potential class members alleging that Workday's AI-driven hiring software unlawfully filtered out applicants based on age, race, and disability. In a March 2026 ruling, the court rejected Workday's argument that the Age Discrimination in Employment Act does not cover job applicants, treating the software vendor as an "agent" of employers for liability purposes. The decision significantly broadens the potential liability framework for AI hiring tools [28].
ISO/IEC TR 24027:2021 provides a technical report on bias in AI systems and AI-aided decision making, offering a taxonomy of biases and mitigation approaches. The OECD AI Principles, adopted in 2019 and updated in 2024, include fairness and non-discrimination as core principles that member countries should promote in AI development and deployment [26].
Several fundamental challenges complicate the effort to address AI bias.
Defining fairness. As noted above, multiple definitions of fairness exist, and they are often mathematically incompatible. Different stakeholders may prioritize different fairness criteria based on their values, the application context, and the populations affected. There is no universally agreed-upon definition of what constitutes a "fair" AI system [4].
Measuring bias. Detecting bias requires access to data on protected attributes, but many organizations do not collect or are legally prohibited from collecting such data. This creates a paradox: the information needed to detect bias is often the information that privacy laws are designed to protect.
Intersectionality. Bias can be compounded at the intersection of multiple protected attributes. A model that appears fair when evaluated separately by race and by gender may still discriminate against specific subgroups, such as Black women. Evaluating bias at the intersection of all relevant attributes requires exponentially more data and raises additional statistical challenges.
Trade-offs with accuracy. Bias mitigation techniques often involve trade-offs with overall model performance. Imposing fairness constraints may reduce accuracy for some groups or overall. Practitioners must navigate these trade-offs in a principled way, and there is ongoing debate about how much accuracy loss is acceptable in exchange for improved equity.
Scale and automation. As AI systems are deployed at increasing scale, the potential impact of biased decisions grows correspondingly. An individual human recruiter might screen hundreds of resumes; an AI system can screen millions. Bias that might be statistically insignificant at small scale can cause substantial harm when applied to millions of decisions.
Bias in generative AI. The rise of large language models and image generation systems has introduced new dimensions of bias. These systems can generate stereotypical or offensive content, reinforce cultural assumptions, and produce outputs that are less accurate or useful for marginalized groups. Testing and mitigating bias in open-ended generative systems is substantially more difficult than in traditional classification tasks because the output space is essentially unbounded.
AI bias remains a significant and evolving challenge. Several trends characterize the current landscape.
Regulatory pressure is increasing. The EU AI Act's high-risk system requirements are in effect for GPAI and Annex I systems from August 2026, though the Digital Omnibus agreement reached on May 7, 2026 extended most Annex III use-based high-risk AI deadlines to December 2027. Colorado's AI Act enforcement was stayed in April 2026 following constitutional litigation, but its replacement law SB 26-189 continues the anti-discrimination framework. The trend remains toward mandatory rather than voluntary bias assessment [24][25][27].
Tooling is maturing. The ecosystem of bias detection and mitigation tools has expanded significantly. Tools like AI Fairness 360, Fairlearn, and the What-If Tool are widely used in industry, and commercial offerings have emerged to serve organizations without dedicated ML fairness teams. Integration of fairness checks into MLOps pipelines is becoming standard practice at large technology companies.
Research is advancing. Academic and industry research continues to develop new fairness metrics, mitigation techniques, and evaluation frameworks. Areas of active research include causal fairness (using causal inference to reason about the sources and effects of bias), fairness in foundation models, and intersectional fairness assessment.
Challenges persist. Despite progress, bias continues to surface in deployed systems. The 2024 University of Washington study on resume screening tools demonstrated that even recently developed AI hiring systems exhibit significant racial bias [9]. A related 2026 Stanford study published in the journal Science found that sycophantic AI systems affirmed users' actions 49% more often than human advisors, raising additional concerns about AI systems reinforcing user biases rather than correcting them [29]. The proliferation of generative AI has created new vectors for bias that existing tools and frameworks are still catching up to address. The gap between bias detection (identifying that a problem exists) and bias remediation (fixing it without introducing new problems) remains wide.
Industry adoption is uneven. Large technology companies with dedicated responsible AI teams have made measurable progress in integrating bias assessment into their development processes. Smaller organizations and those outside the technology sector often lack the expertise, resources, and awareness to conduct meaningful bias evaluations.