Search Results for: offensive
We have not changed it significantly, but we have added to our guidance on the name of Washington’s NFL team. Here’s an update:
NPR News does not plan to prohibit the use of the full team name. The team’s name is the name and our job is to report on the world as it is, not to take a position or become part of the story.
But, our policy on potentially offensive language states that “as a responsible broadcaster, NPR has always set a high bar on use of language that may be offensive to our audience. Use of such language on the air [and online] has been strictly limited to situations where it is absolutely integral to the meaning and spirit of the story being told.”
That guidance should be kept in mind. Here’s how:
As a network, we do not have much occasion to report on this club. When we do, we can usually refer to it simply as “Washington” or “the team” once we’ve established that we’re talking about the city’s NFL franchise. This line, for example, was on our air after the firing of Washington’s coach: “Last year the Redskins made the playoffs, this year they were only 3-13, Mike Shanahan was held to account.” We could have said: “Last year Washington made the playoffs, this year the team was only 3-13, Mike Shanahan was held to account.”
Headlines about the team (on the few stories we might post about the club that aren’t about the name controversy) can be a difficult issue. “Seahawks Crush Redskins” can be changed to “Seattle Crushes Washington.” But “Giants Crush Redskins” can’t become “New York Crushes Washington” because a reader wouldn’t know if we’re referring to the Giants or the Jets.
Again, we are not prohibiting the use of the full team name. At times, it will have to be used – particularly when reporting about the controversy. At times, it may sound awkward to refer to the club as “Washington” or “the team.” Clarity in our reporting is vital. In some cases, achieving that clarity will require using the team’s name (for instance, to distinguish the club from Washington’s other sports teams). Guests will surely use the word Redskins during interviews.
But we can also be sensitive, avoid overuse of the word and use alternatives – as we would with other potentially offensive language.
(Memmos; Oct. 10, 2014)
A search today for NPR’s latest guidance on the use of potentially offensive language revealed that we hadn’t posted the most recent version.
So, here’s a link to where our latest language about such language can be found. It was written earlier this year:
The biggest change from the previous document is the addition of a lengthy section on “Entertainment and Music Programming.”
Fair warning: As we might say on the air and online, “some of the language in the document will be offensive to many readers.”
The section of the Ethics Handbook that deals with “using potentially offensive language” has been updated with the new link.
This is a good time for a reminder, because one slipped through the cracks on us last week: If there’s potentially offensive language in a piece intended for broadcast — even if the words have been bleeped — stations need to be alerted in the DACS line. Listeners and readers online deserve to be warned as well, of course.
Clarification: No offensive words were heard in the piece referred to above. The words were bleeped.
(Memmos; Aug. 11, 2014)
There is a lengthy document (updated in January 2014) that lays out NPR’s policy on use of offensive language posted online. It is radio-centered, but the same rules apply to what we post on NPR.org.
The policy statement begins with this:
“As a responsible broadcaster, NPR has always set a high bar on use of language that may be offensive to our audience. Use of such language on the air has been strictly limited to situations where it is absolutely integral to the meaning and spirit of the story being told.”
“We follow these practices out of respect for the listener,” the policy continues, and because in the post-Janet Jackson “wardrobe malfunction” world, federal regulators “have taken a much more aggressive line on what they regard as indecent or profane content.” The 2010 decision by a federal appeals court that invalidated the FCC’s indecency policy has not prompted NPR to change its position.
That said, “there are rare instances where we will permit use of profane or indecent languages for news or programmatic reasons. Such an instance is when the use of such language is so vital to the essence of the story that to excise or bleep it would be to distort it or blunt its power and meaning.”
An example (fair warning … you’re about to see an expletive): While traveling with U.S. Army forces in Iraq, NPR’s Eric Westervelt was on the scene when the unit came under fire. At one point in his tape, an American soldier could be heard telling another man to “get the fuck under the truck.”
The NPR policy states that in this case “the use of profanity … is editorially justifiable” because it meets the test of being “vital to the essence of the story” and cutting it out or bleeping the word would alter the power and meaning of the report.
As required by NPR’s policy, “the piece was preceded by a language advisory in the intro read by the host, in addition to the DACS notices in advance to stations. NPR policy is to do both in all such instances for both legal and editorial reasons.”
Online, if sound or text containing potentially offensive language has been approved for use by a Managing Editor or someone above that level, it too must be preceded by text (and in the case of audio, a verbal warning as well) advising the NPR.org audience that what follows contains language some may find offensive. When used in a blog, in most cases the warning should come before a “jump” to a second page. It should require a second “click” to get to the offensive material.
If used online, audio or video containing offensive material should never play automatically. To view or hear it, the user must choose to click “play.”