First impressions
"Accessibility" could be a sub-section of "Build". By putting it here we set the pattern to habitually design for accessibility.
Under "Adapt" (i.e. here), refer to "Accessibility" under "Build" and to the relevant section of "Share" (previously "Publish").
For me, the important thing is to ensure that the community is free to Adapt the resource to ensure accessibility (a licensing issue which could be mentioned somewhere under "Share".
We could include some guidelines and/or links to guidelines (as has already been done under Accessibility When Getting OER.
ToDo:
- Optimise, separate concerns, ... wrt Accessibility When Getting OER, Localize/Remix Accessibility, Accessibility When Using OER, and Publishing Accessibility.
- i.e. make a single separate section for this important cross-cutting concern, possibly place it under "Build" and refer to it as needed elsewhere.