That's why I said diminishing accessibility and slowly cutting off disabled users. This obviously isn't going to happen immediately, but every new feature will be less accessible and maybe even not provide accommodations entirely.
Possibly true but I would imagine the team created an internal Bible of all accessibility requirements and that all of that information wasn't siloed in the heads of each employee in that department.
It's a sign of where it's going though. Will the accessibility info be kept up to date? Will the other teams pay attention to it as much if there's not an internal "force" keeping it on people's mind? Will it be considered at a similar level again in the future? The answer to all of these might be "yes," but getting rid of the employees who are most responsible for this doesn't exactly strike me as an act that views a11y favourably.
There's presumably a gap between the current level and what's legally required, and they can afford to let things slip a bit without getting in trouble.
And I'm sure it'll stay on that unvisited Confluence page for a year or so till some doing some cleanup goes "A11y team? They left agees ago." and deletes it.