Skip to content

Commit

Permalink
Remove explainer edits from this methods PR
Browse files Browse the repository at this point in the history
  • Loading branch information
Michael Cooper committed Jul 22, 2021
1 parent c79c8fb commit 192ad2d
Showing 1 changed file with 30 additions and 34 deletions.
64 changes: 30 additions & 34 deletions explainer/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -68,12 +68,12 @@ <h2>Background and development history</h2>
<p>
The Silver Task Force of the Accessibility Guidelines Working Group and the W3C Silver Community group have partnered to produce the needs, requirements, and structure for the new accessibility guidance. To date, the group has:
<ol>
<li>Researched accessibility guidance needs; </li>
<li>Developed problem statements and opportunities to improve accessibility guidance; </li>
<li>Received input from industry leaders for directions to proceed; </li>
<li>Drafted requirements for the project (they will be reviewed after public feedback from the First Public Working Draft); </li>
<li>Created and tested prototypes for aspects of the project; and </li>
<li>Created a First Public Working Draft and a heartbeat update draft. </li>
<li>Researched accessibility guidance needs
<li>Developed problem statements and opportunities to improve accessibility guidance
<li>Received input from industry leaders for directions to proceed
<li>Drafted requirements for the project (they will be reviewed after public feedback from the First Public Working Draft)
<li>Created and tested prototypes for aspects of the project
<li>Created a First Public Working Draft
</ol>

<section>
Expand All @@ -97,44 +97,40 @@ <h2>Goals</h2>
<h3>Goals for Inclusion</h3>
<p>These goals come from the <a href="https://w3c.github.io/silver/requirements/index.html#design-principles">Silver Requirements Design Principles</a>. The creation process for the guidelines should:</p>
<ul>
<li>Actively recruit a diverse range of people with disabilities in recognition of the importance of their contributions to accessibility standards and solutions. Review and monitor whether people are included. Continually evaluate inclusive features of available tooling and procedures. </li>
<li>Facilitate global participation and feedback.</li>
<li>Set goals for Diversity, Equity, Inclusion. Include a goal for more recruiting of younger accessibility experts. </li>
<li>Actively recruit a diverse range of people with disabilities in recognition of the importance of their contributions to accessibility standards and solutions. Review and monitor whether people are included. Continually evaluate inclusive features of available tooling and procedures.
<li>Facilitate global participation and feedback.
</ul>
</section>
<section id="ContentGoals">
<h3>Goals for Content</h3>
<ul>
<li>Support the needs of a wide range of people with disabilities and recognize that people have individual and multiple needs.</li>
<li>Be flexible enough to support the needs of people with disabilities and keep up with emerging technologies. The information structure allows guidance to be added or removed.</li>
<li>Be written in plain language, as easy as possible to understand. We need a definition of plain language that includes the ease of translation. Ideally, it will be a broadly accepted definition internationally.</li>
<li>Improve the ability to support automated testing where appropriate and provide a procedure for repeatable tests when manual testing is appropriate.</li>
<li>Be data-informed and evidence-based where possible. We recognize that research and evidence are influenced by the number of people with a particular disability, by the size of the body of research, and by the difficulty in capturing data regarding some disabilities or combination of disabilities. The intent is to make informed decisions wherever possible to ensure that the needs of all people with disabilities are prioritized, including needs that differ from the majority. In situations where there is no evidence or research, valid data-gathering methods should be used to obtain and evaluate information from advocacy groups, people with lived experience and other subject matter experts.</li>
<li>Be written so the Guideline content is usable in adaptable and customizable ways. For example, Silver content is available to be extracted by users to adapt to their needs.</li>
<li>Support the needs of a wide range of people with disabilities and recognize that people have individual and multiple needs.
<li>Be flexible enough to support the needs of people with disabilities and keep up with emerging technologies. The information structure allows guidance to be added or removed.
<li>Be written in plain language, as easy as possible to understand. We need a definition of plain language that includes the ease of translation. Ideally, it will be a broadly accepted definition internationally.
<li>Improve the ability to support automated testing where appropriate and provide a procedure for repeatable tests when manual testing is appropriate.
<li>Be data-informed and evidence-based where possible. We recognize that research and evidence are influenced by the number of people with a particular disability, by the size of the body of research, and by the difficulty in capturing data regarding some disabilities or combination of disabilities. The intent is to make informed decisions wherever possible to ensure that the needs of all people with disabilities are prioritized, including needs that differ from the majority. In situations where there is no evidence or research, valid data-gathering methods should be used to obtain and evaluate information from advocacy groups, people with lived experience and other subject matter experts.
<li>Be written so the Guideline content is usable in adaptable and customizable ways. For example, Silver content is available to be extracted by users to adapt to their needs.
</ul>
</section>
<section id="ConformanceGoals">
<h3>Goals for Conformance</h3>
<p class="ednote">The goals are based on the <a href="https://www.w3.org/WAI/GL/task-forces/silver/wiki/Silver_Research_Archive" target=blank>Silver research</a>, the results from the <a href="https://www.w3.org/community/silver/draft-final-report-of-silver/" target=blank>Silver Design Sprint</a>, and input from the Silver Community Group and Task Force.</p>
<ul>
<li>Better align conformance with the experiences of people with disabilities, and keep in mind that people with different disabilities have different experiences.</li>
<li>Treat the needs of all disabilities equitably. </li>
<li>Support a measurement and conformance structure that includes guidance for a broad range of disabilities. This includes more attention to the needs of low vision and cognitive accessibility, whose needs may not fit the true/false statement success criteria of WCAG 2.x. </li>
<li>Consider the needs of more organizations.</li>
<li>Be user-oriented instead of page-oriented. Think about what is the person trying to do.</li>
<li>Wherever possible, preserve the organization’s investment in training, tooling, and knowledge. </li>
<li>Better align conformance with the experiences of people with disabilities, and keep in mind that people with different disabilities have different experiences.
<li>Treat the needs of all disabilities equitably.
<li>Support a measurement and conformance structure that includes guidance for a broad range of disabilities. This includes more attention to the needs of low vision and cognitive accessibility, whose needs may not fit the true/false statement success criteria of WCAG 2.x.
<li>Consider the needs of more organizations
<li>Be user-oriented instead of page-oriented. Think about what is the person trying to do.
<li>Wherever possible, preserve the organization’s investment in training, tooling, and knowledge.
<li>Support the ability for organizations to choose parts of their site or product for conformance (a logical subset of a site or product).</li>
<li>Create a more flexible conformance model that addresses the challenges in applying the 2.x conformance model to large, complex, or dynamic websites and web applications.
<ul>
<li>Help organizations prioritize things that have a greater impact on improving the experience of people with disability. </li>
<li>Develop a more flexible method of measuring conformance that is better suited to accommodate dynamic or more regularly updated content.</li>
</ul>
<li>Remove “accessibility supported” as an author responsibility, and help developers of authoring tools, browsers, and assistive technologies learn the behaviors that users expect of their products. <span class="ednote"> Note: This requires more detailed discussion in AGWG. It does not yet have consensus. </span></li>
<li>Improve tests so that repeated tests get more consistent results.</li>
<li>Increase the ability to create more automated tests.</li>
<li>Lower the cost of accessibility testing.</li>
<li>Do not increase the testing burden. </li>

<li>Remove “accessibility supported” as an author responsibility, and help developers of authoring tools, browsers, and assistive technologies learn the behaviors that users expect of their products.
<li>Improve tests so that repeated tests get more consistent results.
<li>Increase the ability to create more automated tests.
</ul>
</section>
</section>
Expand All @@ -144,8 +140,8 @@ <h2>Non-Goals or Out-of-Scope</h2>
<li>Non-web emerging technologies (this may change as the charter is clarified)
<li>Normative requirements for platforms, operating systems, software in the web technology stack (etc.)
<ul>
<li>We want to point to external accessibility guidance by the vendor</li>
<li>We want to document the needs of people with disabilities where vendor accessibility guidance is lacking</li>
<li>We want to point to external accessibility guidance by the vendor
<li>We want to document the needs of people with disabilities where vendor accessibility guidance is lacking
</ul>
</li>
</ul>
Expand All @@ -165,7 +161,7 @@ <h3>Structure of these guidelines</h3>
<p>Some of these sections are in this document. You can find others in links within the sections.</p>
</details>
<figure id="guidelines-structure-diagram" aria-labelledby="guidelines-structure-description" class="figure-float">
<img src="../guidelines/img/structure-core.svg" />
<img alt="" src="../guidelines/img/structure-core.svg" />
<figcaption>Core Structure</figcaption>
</figure>
<p><a href="#guidelines-structure-diagram">Figure 1</a> shows <span id="guidelines-structure-description">the core structure of WCAG 3.0. WCAG 3.0 has three levels of content with associated documentation. Guidelines form the top level. Each guideline contains multiple outcomes, with associated critical errors and outcomes scoring. Each outcome contains multiple methods, with an associated description and examples, tests, and test scoring.</span></p>
Expand Down Expand Up @@ -203,7 +199,7 @@ <h4>Outcome rating</h4>
<section>
<h3>Methods structure</h3>
<figure id="method_screenshot" aria-labelledby="method_screenshot_description" class="figure-float screenshot">
<img src="../guidelines/img/method.png" />
<img alt="" src="../guidelines/img/method.png" />
<figcaption>Screenshot of a Method for Structured Content</figcaption>
</figure>
<p>Each outcome has one or more <a href="#methods-structure">methods</a>. There are three types of methods:</p>
Expand Down Expand Up @@ -254,16 +250,16 @@ <h4>Additional Documentation and Scoring Information</h4>
<p>Some of these sections are in this document. You can find others in links within the sections.</p>
</details>

<p>The core structure has inter-relationships with supporting documents and the scoring process. <span id="guidelines--full-structure-description"> Functional needs inform both outcomes and functional categories. The tests within methods are used to inform the scores for each outcome. Then outcome scores are aggregated to create scores by functional category and an overall score. These then result in a bronze rating. Silver and gold ratings build on the bronze rating to demonstrate improved accessibility. General information about guidelines is available in How-To documents. </span></p>
<p>The core structure has inter-relationships with supporting documents and the scoring process. <span id="guidelines--full-structure-description"> Functional needs inform both outcomes and functional categories. The tests within methods are used to inform the scores for each outcome. Then outcome scores are aggregated to create scores by functional category and an overall score. These then result in a bronze rating. Silver and gold ratings build on the bronze rating to demonstrate improved accessibility. General information about guidelines is available in How To documents. </span></p>
<figure id="guidelines-full-structure-diagram" aria-labelledby="guidelines--full-structure-description" class="figure-full">
<img src="../guidelines/img/structure-scoring.svg" />
<img alt="" src="../guidelines/img/structure-scoring.svg" />
<figcaption>Documentation and Scoring Structure</figcaption>
</figure>
<section>
<h3>How tos</h3>
<p>The <a>How-To</a> content provides explanatory material for each guideline that applies across technologies. This guidance explains how to apply the concepts presented in the guidelines for non-technical readers. This plain language resource includes information on getting started, who the guideline helps and how, as well information for project managers, designers and developers.  </p>
<figure id="howTo_screenshot" aria-labelledby="howTo_screenshot_description" class="figure-float screenshot">
<img src="../guidelines/img/how-to.png" />
<img alt="" src="../guidelines/img/how-to.png" />
<figcaption>Example screenshot of a How-To for Structured Content</figcaption>
</figure>
<p id="howTo_screenshot_description">The example of a How-To for Structured Content provides basic information organized by tabs to help people get started with accessibility for structured content, plan for implementing accessible structured content across a project, design accessible structured content, and basics for developers new to accessibility of structured content. It also includes information on examples, the outcomes for meeting the guideline, and resources.</p>
Expand Down

0 comments on commit 192ad2d

Please sign in to comment.