Sunday, 19 February 2012

ESPN punishes employees over Lin headline

ESPN punishes employees over Lin headline

ESPN punishes employees over Lin headline, ESPN Fires Lin Headline Writer, The network acts quickly after an insensitive headline about the NBA player is pulled from its site. ESPN hasn't always been quick to admit and rectify its mistakes. But in the 36 hours after the racially insensitive headline "Chink in the armor" appeared on its mobile website about Jeremy Lin, the Worldwide Leader issued a strongly-worded apology and now has handed out punishments.

In a "Follow-up statement and action" released Sunday morning, ESPN announced the following:

At ESPN we are aware of three offensive and inappropriate comments made on ESPN outlets during our coverage of Jeremy Lin.

Saturday we apologized for two references. We have since learned of a similar reference Friday on ESPN Radio New York. The incidents were separate and different. We have engaged in a thorough review of all three and have taken the following action:

• The ESPN employee responsible for our Mobile headline has been dismissed.

• The ESPNEWS anchor has been suspended for 30 days.

• The radio commentator is not an ESPN employee.

We again apologize, especially to Mr. Lin. His accomplishments are a source of great pride to the Asian-American community, including the Asian-American employees at ESPN. Through self-examination, improved editorial practices and controls, and response to constructive criticism, we will be better in the future.

The anchor, Max Bretos, also said "Chink in the armor," but in what seemed like a non-calculated manner. Judge for yourself:

On Sunday, Bretos tweeted: "My wife is Asian, would never intentionally say anything to disrespect her and that community."

Either way, ESPN appears intent on owning up to this incident and trying to remedy the situation. Considering the unforgivable nature of the comment and the hurt surely caused by it in the Asian-American community, you can't blame Bristol for that.

via: tpg

No comments:

Post a comment