Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Research
Data sources: ZENODO
addClaim

Stereotype and Severance: Compounding Harms for Neurodivergent Users Across the Lifecycle of Conversational AI

Authors: Conta, Erika;

Stereotype and Severance: Compounding Harms for Neurodivergent Users Across the Lifecycle of Conversational AI

Abstract

This working paper argues that neurodivergent people, including autistic children, who rely on conversational AI as predictable, stigma-free interlocutors face two distinct, compounding harms across a model's lifecycle. The stereotype harm occurs during use: when users disclose a diagnosis such as autism, recent 2026 audits show models shifting their advice toward disability stereotypes, including discouraging social participation. The severance harm occurs at end of life: when a model to which users have formed a stable, routine-based attachment is deprecated, the abrupt loss imposes affective and functional costs that fall hardest on those who depend on consistency. Drawing on 2026 empirical findings and prior work on AI–human emotional interaction, the paper examines both harms and proposes a neurodivergence-aware framework for bias auditing and lifecycle governance.

Powered by OpenAIRE graph
Found an issue? Give us feedback