Table of contents
Ah, a new project. A blank canvas ready to be filled. Hopefully, you've already faced the struggles of implementing accessibility in an un-accessible project and this time you're adamant in avoiding all the hassle and troubles you've already experienced. Let's try to draft a sort of roadmap for a new project that will introduce progressively all the accessibility features and, equally important, will grant our application to be future-proof and fruible to alternative (not only assistive) technologies as much as possible.
In larger projects various teams, with different scopes, cooperate together: I’ll try to separate all the content in different roadmaps, to help those gropus focusing more on what is up to them in a more specific way, or for a single group project to tackle development phases one after the other. No need to stress that “everyone should be (at least) aware of every aspeto”, to fully understand the requirements and the logics.
Keep in mind: what follows is just a proposal, so you should evaluate and adapt it to your project, and above all will not grant automatically that your project will be totally accessible. By the way, there's not such a thing as “totally accessible”: accessibility can be evaluated but not quantified, and it's not a fixed value to reach, but a path to walk and constantly adjust.