# How to Debug Inclusivity Bugs? A Debugging Process with Information Architecture

arXiv: https://arxiv.org/abs/2202.13303 · HTML: https://mlsanity.com/paper/2202.13303/

## Key facts

- Cited by 1 papers in the map (data through 14 Oct 2026).
- First posted on arXiv 27 Feb 2022.

## Built on by (most cited first, 1 of 1)

- ["Over-the-Hood" AI Inclusivity Bugs and How 3 AI Product Teams Found and Fixed Them](https://mlsanity.com/paper/2510.19033/) (2025)

## Abstract (arXiv)

Although some previous research has found ways to find inclusivity bugs (biases in software that introduce inequities), little attention has been paid to how to go about fixing such bugs. Without a process to move from finding to fixing, acting upon such findings is an ad-hoc activity, at the mercy of the skills of each individual developer. To address this gap, we created Why/Where/Fix, a systematic inclusivity debugging process whose inclusivity fault localization harnesses Information Architecture(IA) -- the way user-facing information is organized, structured and labeled. We then conducted a multi-stage qualitative empirical evaluation of the effectiveness of Why/Where/Fix, using an Open Source Software (OSS) project's infrastructure as our setting. In our study, the OSS project team used the Why/Where/Fix process to find inclusivity bugs, localize the IA faults behind them, and then fix the IA to remove the inclusivity bugs they had found. Our results showed that using Why/Where/Fix reduced the number of inclusivity bugs that OSS newcomer participants experienced by 90%.