@aral @nah @fvsch @sonny @matt
Two GNOME cycles, when people are actively working on accessibility this year, is a long time.
Before panicking, consider: a reason it's been targetted to GNOME 48 (a year from now) and not 47 is, devs are collectively aware that not everything is ready for this to happen in 47, and that it is reasonably likely that a11y would be working by 48.
The cited link (!99) says pointblank it is a blocker.