Coga Resource Plan
This is the overall plan for moving coga resources to the WAI Website.
Each proposed page also has it’s own Design Box at the top of the page.
Current WAI pages for CogA
Related Information
- Spreadsheet of all Coga TF resources (Google Doc)
- Coga TF Planning page on wiki
- Coga TF F2F meeting information
- Source on GitHub
- Deployment on GitHub
Reasoning
Currently, the many Coga resources are a mixture of TR Notes, GitHub Issues and more. Several are very large and the fixed document format of TR Notes can be difficult to read. Moving to the WAI Web site offers the following opportunities
- Easily discovered resources as they coexist with other accessibility information where people are looking
- Better organise existing content, including taking advantage of existing WAI information architecture
- Flexibility to provide better formats. For example can be interactive so easier to navigate and read
- Links can enhance the user experience without causing a jump between the very different web and TR document formats
- More control over editorial process including review access and publishing cadence
- Can ‘dog food’ coga and personalisation
Primary Stakeholders
Creators & Consultants
- Understand broad user requirements
- Meet SCs required for desired conformance
- Learn techniques and best practices
- Able to evaluate and remediate short comings
Standard Makers
- Gain detailed understanding of user requirements, both specific and commonalities
- Identify techniques and technologies that support users as well as gaps that need to be filled
- Be confident that existing and newly developed standard clauses successfully meet coga user requirements
Researchers
- Gain an overview of current corpus
- Identify opportunities for further research
- Confident of evidence base for stated requirements and approaches
Secondary Stakeholders
Policy Makers
- Confident in understanding key user requirements
- Ensure Policy is representative and fit for purpose
Procurers
- Know what to put in contracts to ensure inclusive and legal
Evaluators
- Know what to test and how best to do so.
- Ensure reports are accurate and informative
- Design enhanced evaluations
Practitioners and End Users
- Be confident needs are accurately recorded and encourage new solutions
- Find techniques and tools they can use
New Pages
Exploring
- Purpose: A interactive overview with links to the various coga resources
- Primary audience: Someone who wants to learn about coga in general or in order to perform a task
- Work to complete New content. Integrate into WAI
- Site Path: Accessibility Fundamentals / Cognitive Disabilities
- Current doc: New content
- Estimated effort: medium
- Priority high
About
- Purpose: Introduce cognitive and learning disabilities
- Primary audience: Someone new to coga and wanting understand the general issues user face
- Work to complete Find or create content. Integrate into WAI
- Site Path: Accessibility Fundamentals / Cognitive Disabilities / About
- Estimated effort: medium
- Current doc: ???
- Priority low
Developer Resources
- Purpose: Provide high level info on user needs, barriers, personas, testing.
- Primary audience: Someone wanting to learning how to develop coga inclusive
- Work to complete Copy content from Content Usable and more. Integrate into WAI
- Site Path: Accessibility Fundamentals / Cognitive Disabilities / Design Guide
- Current doc: Working Draft
- Estimated effort: medium
- Priority high
Design Guide
- Purpose: Provide detailed techniques and best practices to address requirements
- Primary audience: Someone wanting specific techniques that address coga requirements
- Work to complete Clean up Design Guide. Create interactive access with links based on TF Mockup. Integrate into WAI
- Site path: Accessibility Fundamentals / Cognitive Disabilities / Design Guide
- Current doc: Working Draft
- Estimated effort: large (x-large)
- Priority high
Gap Analysis
- Purpose: Provide insight into barriers currently faced by users.
- Primary audience: Someone wanting to learning about technical barriers that are not yet addressed.
- Work to complete Clean Up and move content from Gap Analysis. Ignore road map content. For WCAG. Integrate into WAI
- Site path: Accessibility Fundamentals / Cognitive Disabilities / Gap Analysis
- Current doc: Working Draft
- Estimated effort: large
- Priority high
Research Findings
- Purpose: Present Coga TF research in to user requirements Issues Papers on specific barriers faced.
- Primary audience: Someone wanting to understand the barriers faced by users when using technology
- Work to complete Clean up and copy content from User Reseach and Issue Papers. Integrate into WAI
- Site path: Accessibility Fundamentals / Cognitive Disabilities / Research
- Current doc User Research Working Draft & Issue Papers Working Draft
- Estimated effort: x-large
- Priority low
Personas
- Purpose: Provide representative and accurate personas usefull for design activities
- Primary audience: Someone wanting to understand the barriers faced by users when using technology.
- Work to complete Move to existing WAI page, replacing current personas
- Site path: TBD existing persona page?
- Current doc: Working Draft
- Estimated effort: medium
- Priority low
Glossary
- Purpose: Provide definitive definition of terms
- Primary audience: Someone wanting to understand a particular term.
- Work to complete Needs to be created
- Site path: ? - might remain as a doc
- Current doc: Google Doc
- Estimated effort: low
- Priority high
Taskforce
- Purpose: Provide information about the Coga Task Force. To replace the old TF page
- Primary audience: Someone wanting info about the TF, including how to participate.
- Site path: https://www.w3.org/WAI/APA/task-forces/coga and https://www.w3.org/WAI/APA/task-forces/coga/work-statement
- Work to complete Add 2 new pages based on old page. Link from APA WG pages
- Current doc: Taskforce page
- Estimated effort: low
- Priority medium
Editoral process
- Source in GitHub repository - wai-coga
- TF will provide updates via a coga-fiendly contribution channel
- Could be google docs
- Editor (Steve) will take input from TF and merge into source
- Use feature branch and PR to isolate changes
- Commit to master causes push to w3c.github.io
- Provide previews for TF review with links to https://w3c.github.io/wai-coga/
- Local dev & view are possible for faster development
- Publish to live semi manual process
- ping Eric
- TF to decide cadence