Soccer’s ruling officials have finally said “Enough is enough!” On Thursday, FIFA informed the Mexican Soccer Federation (FMF) that if the homophobic shout that has become “popular” at El Tri matches (and at Liga MX games, too), Team Mexico will be docked 3 points.
For nearly 20 years, Mexico fans have taken to shouting “Puto!” when the opposing team’s goalie takes a free kick and for nearly 10 years FIFA has requested that the FMF take steps to put a halt to it.
During the recent Nations League tournament in the US, Concacaf took steps to address the objectionable chant but El Tri fans ignored the warnings. During the semifinal against Costa Rica and again in the final against Team USA, officials stopped the game for 5 minutes after public address announcements were ignored. The next step would have been sending the players to the locker room for a lengthier pause and a final sanction would have been a forfeit.
Even though the stricter measures were not applied, FIFA decided further action is necessary as it continues to apply anti-discrimination protocols across the world. And now El Tri could be at the mercy of its rabid fan base.
Will El Tri fans police themselves?
Mexico opens its World Cup qualifying schedule on Sept. 2 at Estadio Azteca against Jamaica and that will be the first test. FMF officials must be sweating profusely right now, but they have no one but themselves to blame.
If the chant is heard and the team is docked 3 points, the road to Qatar will immediately become much more difficult.
The offending shout first came to world attention at the 2014 World Cup in Brazil. The resounding roar in the stands caught FIFA’s attention, but FMF and El Tri officials downplayed the shout. When FIFA threatened to take action, the Mexican officials argued that it was a “tradition” (it was only about 10 years old at the time) while also insisting that it was not an offensive term.
More from CONCACAF
- Team Mexico player evaluations from Aussie, Uzbek matches
- First impressions of ‘renovated’ El Tri are underwhelming
- Mexico earns draw in yet another lackluster performance
- El Tri overturns 2-goal deficit to earn draw vs Australia
- El Tri in Big D to face Socceroos at Jerry World
While FIFA simmered, Mexico laughed off the admonition. Soccer’s world governing body then took the step of studying the chant before issuing a determination that it was indeed offensive and would have to be eliminated. Fines would henceforth be issued for each incident. Still, the FMF shrugged at the problem and quietly paid the increasing fines.
As the 2018 World Cup approached, FIFA again warned Mexico and the FMF feigned seriousness, taking rather meek steps to put a halt to the chant (public address announcements at games, videotaped pleas from members of El Tri). All to no effect. The homophobic howl continued unabated.
As fines increased and FIFA told the FMF that penalties would increase, Mexican officials decided it was best to make a concerted effort to address the embarrassing situation. In 2019, the Liga MX established protocols to target the bellowing buffoons. Warnings were issued, new videos were made and game-stoppages were authorized. Still, referees were reluctant to enforce the protocols (were they advised against strictly applying them?).
With the announcements that Concacaf would be cracking down during the Nations League event, El Tri players were once again summoned to participate in the program to squelch the screaming.
And now the FMF’s cavalier attitude toward the issue could have dire consequences for El Tri. It will be interesting whether Olympic officials involve themselves in the controversy as El Tri will be participating in the upcoming Tokyo Games.
Mexican officials will have about six weeks’ worth of Liga MX games before the qualifier against Panama to publicize the seriousness of the situation. Perhaps they will stop games to illustrate genuine determination. Maybe they will try to arrest fans caught yelling the phrase. Or maybe it will take a World Cup ban to make El Tri fans realize that bigotry in any context is unacceptable.