Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update accessibility support section #658

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Update accessibility support section #658

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 39 additions & 1 deletion guidelines/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -516,10 +516,48 @@ <h4>Steps to Conform</h4>
<h3>Conforming alternative version</h3>
<p class="ednote">For this first draft, the Accessibility Guidelines Working Group has focused on the basic conformance model. For a next draft, we will explore how <a href="https://www.w3.org/TR/WCAG21/#dfn-conforming-alternate-version">conforming alternative versions</a> fit into the new conformance model.</p>
</section>

<section data-status="placeholder">
<h3>Only accessibility-supported ways of using technologies</h3>
<p class="ednote">For this first draft, the Accessibility Guidelines Working Group has focused on the basic conformance model. For a next draft, we will explore how <a href="https://www.w3.org/TR/WCAG21/#cc4">accessibility-supported</a> fits into the new conformance model.</p>
<div class="ednote">
<p>The subgroup has been discussing how we should handle the “<a href="https://www.w3.org/TR/WCAG21/#cc4">accessibility-supported</a>” concept in WCAG 3. The subgroup identified the following two directions and there are five options for the first direction at this time.</p>
<ol>
<li>
Keep “accessibility-supported” (AS) concept
<ol style="list-style:Lower-alpha">
<li>as-is (i.e., without test files and testing results).</li>
<li>Develop a database (including test files and testing results).</li>
<li>Develop test files at least (without testing results).</li>
<li>Keep limited to documented Methods (without test files and testing results).</li>
<li>Promote AS issues in each Guideline in WCAG 3 as well as supporting documents (without test files and testing results).</li>
</ol>
</li>
<li>Remove AS.</li>
</ol>
<p>For the next step, the subgroup must first decide if WCAG 3 must keep the “accessibility-supported” concept (#1) or not (#2). If WCAG 3 will keep AS (#1), there are five options (from a. to e. above) to improve and clarify the “accessibility-supported” concept in WCAG 3.</p>
<p>Here are questions the subgroup will need to address based on our findings so far:</p>
<ul>
<li>
Should we keep the “accessibility-supported” concept or not?
<ul>
<li>Pros and Cons on “Keep” vs “Remove” are available in draft format.</li>
</ul>
</li>
<li>
If yes, what form should AS take? (Example: a. ～ e. above)
<ul>
<li>Should we modify the definition of the term “accessibility-supported” if needed?</li>
</ul>
</li>
</ul>
<p>The subgroup has identified the following outstanding issues:</p>
<ul>
<li>It has been a big challenge to secure robust human resources and funding to create test files and test them with a wider range of ATs and UA. What level of effort is needed to sustain test files and test results, and in multiple languages. What resources are available for this effort?</li>
<li>There is an older prototype “<a href="https://www.w3.org/WAI/accessibility-support/">Web Accessibility database</a>” which was not approved (and not maintained) due to the scalability issues. Does this prototype serve as a proof of concept? What is missing from this prototype?</li>
</ul>
</div>
</section>

<section data-status="exploratory">
<h3>Defining conformance scope</h3>
<p>When evaluating the accessibility of content, WCAG 3.0 requires the outcomes apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more sub-sets of the whole. Reasons for this include:</p>
Expand Down