Show Summary Details

Page of

PRINTED FROM OXFORD HANDBOOKS ONLINE (www.oxfordhandbooks.com). (c) Oxford University Press, 2015. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Handbooks Online for personal use (for details see Privacy Policy).

date: 22 November 2017

Abstract and Keywords

This chapter describes several instances of linguistic bigotry against speakers of African American Vernacular English. Race, language, and the Ebonics controversy are reviewed prior to the presentation of experimental evaluations of linguistic profiling related to housing discrimination across the United States. Evidence pertaining to racially motivated linguistic discrimination is presented in reference to technical phonetic evaluations of diverse American dialects. The experimental findings, although derived from research on housing discrimination, prove relevant to other forms of linguistic prejudice; evidence of vitriolic linguistic ridicule surfaced during the George Zimmerman murder trial in response to the testimony of Rachel Jeantel. Due to substantial linguistic bias in America (and elsewhere), the need for educational programs that expose linguistic prejudice and prepare students who may become victims of linguistic discrimination will be necessary. Concluding remarks synthesize observations regarding linguistic profiling in housing, on the job, in the courts, and in educational contexts.

Keywords: linguistic profiling, linguistic discrimination, housing discrimination, African American Vernacular English, Rachel Jeantel

Access to the complete content on Oxford Handbooks Online requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can''t find the answer there, please contact us.