While I'll agree that any method to use MS-Access with a screen reader that works is absolutely amazing, this is an instance where I think that "going the GUI route" is a way to make things far, far more difficult than they need be.
I cut my teeth with databases before the age of the GUI interface learning SQL, which is still very widely in use to this day and which is supported (or was, anyway) by MS-Access and a lot of other relational databases.
The amount of work to learn SQL to commit and manipulate databases is not herculean. The ability to deal with it when you're a screen reader user, since SQL is just plain text code, and pretty directly understandable plain text code for most of the basic database wizardry, it's just so much easier to deal with overall. And that even applies to report formatting and generation.
It's worth having a look at SQL as a possible option. You might be pleasantly surprised at what you find.
--
Brian - Windows 10, 64-Bit, Version 21H1, Build 19043
Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.
~Martin Luther King, Jr.