shawna-slh
commented
7 years ago If we want to refine this idea, here are some thoughts and questions:
-
Implement \ Tutorials, Tips, Examples -- When the Components list is done, maybe put Examples as it's own sub-section?
-
Implement \ How to reference the guidelines and How they are developed -- I put these there here because they are directly related to the Guidelines; however, they are not directly related to Implementing. Perhaps they should go elsewhere -- or even maybe not have in primary nav, and just link all places relevant, e.g., Policies pages?
-
Promote / Managing Accessibility -- Managing Accessibility kinda goes with Implement, but maybe better here because Implement focuses more on the actual developing. I'm inclined to put it under Promote, and just make sure there are plenty of links to it in relevant places, such as the main Intro.
-
Evaluation and Report Language (EARL) Overview doesn't fit smoothly anywhere. The audience is tool developers. Possibly it would be better in the Evaluate section -- however, that mostly has a totally different primary audience. (Also, I like having ARIA under the "specifications" subheading, and it's good for it to have another bullet. ;-) So I'd be inclined to have it under Implement.
-
Selecting and Using Authoring Tools for Web Accessibility -- Maybe not have in main nav – archive until it gets updated?
-
Accessibility Principles -- Later when rejigging content, make Accessibility Principles an easy direct landing page, and then add it to the top level navigation.
James-Green
Here is a Navigation idea (straw proposal) based on:
This would be for an interim navigation while we are making more significant changes to content, e.g., reorganizing the pages under How People with Disabilities Use the Web.
Feel free to tweak directly via GitHub (or pull request if you can't Commit directly)