W3C
Web Accessibility Initiative
What’s up with all those repositories?!
Title Text
It’s easier than that.
(I hope!)
wai-website
wai-website-components
wai-website-jekyll-templates
resources
wai-training
wai-policies-prototype
wai-inclusion
wai-bcase
…
CSS, JavaScript
HTML
Resources
1. Simple Pages
For example:
https://github.com/w3c/wai-selecting-eval-tools
One page resources that have
nothing in common with other pages.
2. Resources
For example:
https://github.com/w3c/wai-training
A collection of data or pages that is (usually)
rendered with a common navigation.
3. Complex Resources
For example:
https://github.com/w3c/wai-policies-prototype
A collection of data or pages that is (usually)
rendered with a common navigation, but which functionality is unique to this resource.
All resources draw their HTML templates, CSS and JavaScript from the same linked repos as wai-website.
Additional CSS & JavaScript can be provided.
But usually it is useful for others, too.
For example in the wai-tutorials, we reference WCAG SCs and techniques. This is available to all pages now. 👍🏼
The base repository:
Complex Resources need some more configuration
For example:
Where do I find my content?
- Simple Page: index.md
- Resource: _resource_name folder
- Complex Resource: _resource_name folder, but could be not HTML/Markdown
How do I edit content?
- Find content file
- Click the edit button (top right)
- If editor: You should have write access and not need to fork.
- If reviewer: Submit the change as a pull request.
- Once saved/pulled: The page is immediately rendered at https://w3c.github.io/wai-repository_name/
Q&A
wai-repos-tpac17
By Eric Eggert
wai-repos-tpac17
- 2,574