[DRAFT] CG Site Redesign - act-rules/act-rules.github.io GitHub Wiki

Purpose

Make the ACT-Rules CG website easier to overview and use, especially for people who are new to this work and want to get involved.

Objectives

The re-design work should (in order of priority) make it easier for:

  1. Non-CG participants to quickly understand what this work is about and how to get involved
  2. New CG participants to learn how to contribute (eg. review-, write-, and implement rules)
  3. Seasoned CG participants to find the resources they need (eg. running test cases etc.)
  4. Various other stakeholders to find the information they need (eg. managers, funders, etc.)

Non-Objectives

This website is not intended to define Accessibility Conformance Testing (ACT) and its benefits. Instead, it should link out to relevant W3C pages, such as the ACT Overview page.

Audience

Several audiences need to be addressed by the website. Following the above objectives, they can be categorized in primary and other audiences. Both audiences will be addressed but priority will be given to primary audience in the design.

Primary Audience

  1. Potential CG participant - needs to feel welcomed, supported, and encouraged to participate
  2. Current CG participant - needs to be supported in carrying out their on-going CG tasks
  3. Irregular CG contributor - needs low threshold to contribute (eg. easy to provide feedback)

Example Scenarios

  • Example 1: I can immediately understand what the group does and how it works (potential CG participant)
  • Example 2: I can find helpful resources to help me learn how to contribute (potential CG participant)
  • Example 3: The information is well-structured and does not feel overwhelming/discouraging (potential CG participant)
  • Example 4: I want to {review-, suggest-, write-, or implement} rules and can find information on how to contribute (current CG participant)
  • Example 5: I have comment on a {rule or test case} and am able to send it very easily (irregular CG contributor)
  • Example 6: I only want to see what implementations there are and can find this information (irregular CG contributor)
  • Example 7: I want to run my implementation on test cases and was able to do that easily (current CG participant & irregular CG contributor)

Other Audience

  • Tool/Methodology producer - needs to understand what this group does any why they should participate
  • Tool/Methodology consumer - needs to understand how this work related to them and how to leverage it
  • Other experts and advocates - need to understand how this work helps improve accessibility overall

Example Scenarios

  • Example 8: I can immediately understand what the group does and how it benefits accessibility overall (all)
  • Example 9: I can immediately understand what the group does and how it relates to my own situation (all)
  • Example 10: I can easily track the progress of this group and get an idea on the current trajectory (all)

Information Architecture

  • Homepage - brief description and tile-design for different activities: "view rules and implementations", "contribute and get involved", "about this group"
    • Rules - list of completed rules with clear disclaimer about their W3C (non-)standing
      • Test Cases - list of test cases from completed rules (with same disclaimer)
      • Implementations - list of implementations for the completed rules with "add your implementation" link
      • Glossary - list of definitions created by the CG and disclaimer about their W3C (non-)standing
      • Draft Rules - list of rules in development with clear disclaimer about their CG (non-)standing
    • Contribute - brief overview on ways to contribute and get involved (maybe also tile-design?)
      • Compare Your Implementation - description of how to compare rules automatically and manually
      • Add Your Implementation - description of how to provide implementation reports for listing
      • Provide Feedback on Rules - description of how to review, with links to further documentation
      • Suggest or Write New Rules - description of how to write, with links to further documentation
    • Documentation - @@@
      • Review Process - @@@
      • Rule Template - @@@
      • Review Guide - (detailed step-by-step guide) @@@
      • License - @@@
      • ... - @@@
    • About - @@@
      • Mission Statement - @@@
      • Why This Matters - @@@
      • ... - @@@