Walsall issue Roman Dixon injury update, as Ryan Leak absence explained
The Walsall right-back has not featured since making his debut in their League Two opener.
Walsall boss Lee Grant says full-back Roman Dixon is continuing to build-up his fitness in training, after missing the past six matches with a knock.
The 21-year-old, who was released by Everton prior to joining the Saddlers, has not featured since making his debut in a 3-0 opening day win at Gillingham on August 15.
Dixon returned to training nearly two weeks ago, but is still working his way towards being ready to play.
“Roman trained today [at Essington on Saturday]. He’s on the grass with a small group,” Grant revealed.
“That’s a mark of how tough it is at the moment. We’ve got really good players at the training ground, training this morning.
“So, yes Roman was working today and hopefully he’ll have a good week.”
Leak absence explained


Ryan Leak played the full 90 minutes in the 0-0 draw at Exeter City, but was not involved for the Saddlers’ successive goalless stalemate against Rochdale on Saturday.
But Grant has reassured that Leak’s absence was merely down to competition for places at the back, as Declan Skura returned to help Walsall register their sixth clean sheet in eight games.
“There is just no ego in this group, which is unbelievable,” he added.
“Leaky is one of our most experienced, he’s worn the armband for me in the first game of the season and had every right to play today.
“That’s the sort of recurring theme. At any point, does Harrison Burke deserve not to be playing, or has shown me that there’s holes in his game and isn’t working incredibly hard. The answer is no.
“So Leaky deserved to play today. That’s the truth and Burkey deserved to play today if I’m being really honest, but my two centre halves that played were outstanding.
“That’s just how it’s going to be and how it’s got to be.”
Comment Guidelines
Iconic Media encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.
