Skip to content

Commit

Permalink
Finishing header plus URI redesign under Challenge #1 per Michael's p…
Browse files Browse the repository at this point in the history 
…referred pattern.
  • Loading branch information
@sajkaj
sajkaj committed Dec 13, 2019
1 parent aca5d4f commit 08099aa
Showing 1 changed file with 114 additions and 19 deletions.
133 changes: 114 additions & 19 deletions conformance-challenges/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -215,79 +215,174 @@ <h3>
<p>Ensuring keyboard operability of all functionality currently requires a human to manually navigate through content to ensure all interactive elements are in the tab order and can be fully operated using the keyboard.</p>
</section>
<section>
<h3>Character Key Shortcuts (Success Criterion 2.1.4)</h3>
<h3>Character Key Shortcuts
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#character-key-shortcuts">Success Criterion 2.1.4</a>
</p>

<p>Single key presses can be applied to content via a script but whether and what these key presses trigger can only be determined by additional human evaluation.</p>
</section>
<section>
<h3>Timing Adjustable (Success Criterion 2.2.1)</h3>
<h3>Timing Adjustable
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#timing-adjustable">Success Criterion 2.2.1</a>
</p>

<p>There is currently no easy way to automate checking whether timing is adjustable. Ways of controlling differ both in naming, position and approach (including dialogs/popups before the time-out) and depends on how the server registers user interactions (e.g. for automatically extending the time-out).</p>
</section>
<section>
<h3>Pause, Stop, Hide (Success Criterion 2.2.2)</h3>
<h3>Pause, Stop, Hide
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#pause-stop-hide">Success Criterion 2.2.2</a>
</p>

<p>Typically the requirement to control moving content is provided by interactive controls placed in the vicinity of moving content, or occsionally at the beginning of content. Since position and naming vary, this assessment can not currently be automated (this involves checking that the function works as expected).</p>
</section>
<section>
<h3>Three Flashes or Below Threshold (Success Criterion 2.3.1)</h3>
<h3>Three Flashes or Below Threshold
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#three-flashes-or-below-threshold">Success Criterion 2.3.1</a>
</p>

<p>There are currently no known automated tests that are accurately able to assess areas of flashing on a webpage.</p>
</section>
<section>
<h3>Bypass Blocks (Success Criterion 2.4.1)</h3>
<h3>Bypass Blocks
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#bypass-blocks">Success Criterion 2.4.1</a>
</p>

<p>While it can be determined that native elements or landmark roles are used, there is currently no automted way to determine whether they are used to adequately structure content (are they missing out on sections that should be included). The same assessment would be needed when other Techniques are used (structure by headings, skip links).</p>
</section>
<section>
<h3>Page titled (Success Criterion 2.4.2)</h3>
<h3>Page titled
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#page-titled">Success Criterion 2.4.2</a>
</p>

<p>Automating a check for whether the page has a title is simple, ensuring that the title is meaningful and provides adaquate context is not.</p>
</section>
<section>
<h3>Focus Order (Success Criterion 2.4.3)</h3>
<h3>Focus Order
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#focus-order">Success Criterion 2.4.3</a>
</p>

<p>There is currently no way to automate ensuring that focus handling with dynamic content (e.g. moving focus to a custom dialog, keep focus in dialog, return to trigger) follows a logical order.</p>
</section>
<section>
<h3>Link Purpose (Success Criterion 2.4.4)</h3>
<h3>Link Purpose (In Context)
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#link-purpose-in-context">Success Criterion 2.4.4</a>
</p>

<p>Automated tests can check for the existence of links with the same name, as well as check whether links are qualified programmatically, but checking whether the link text adequately describes the link purpose still involves human judgment.</p>
</section>
<section>
<h3>Multiple ways (Success Criterion 2.4.5)</h3>
<h3>Multiple ways
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#multiple-ways">Success Criterion 2.4.5</a>
</p>

<p>Automated tests can validate whether pages can be reached with multiple ways(e.g. nav and search), but will miss cases where exceptions hold (all pages can be reached from anywhere) and still require human validation..</p>
</section>
<section>
<h3>Headings and Labels (Success Criterion 2.4.6)</h3>
<h3>Headings and Labels
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#headings-and-labels">Success Criterion 2.4.6</a>
</p>

<p>The determination of whether headings are descriptive depend on an assessment of the context of web content headed or labeled and is therefore predominantly a human assessment.</p>
</section>
<section>
<h3>Pointer Gestures (Success Criterion 2.5.1)</h3>
<h3>Pointer Gestures
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#pointer-gestures">Success Criterion 2.5.1</a>
</p>

<p>There are currently no known automated checks that would accurately detect complex gestures - even when a script indicates the presence of particular events like touch-start, the event called would need to be checked in human evaluation.</p>
</section>
<section>
<h3>Pointer Cancellation (Success Criterion 2.5.2)</h3>
<h3>Pointer Cancellation
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#pointer-cancellation">Success Criterion 2.5.2</a>
</p>

<p>When mouse-down events are used (this can be done automatically), checking for one of the four options that make it OK looks definitely like a human task.</p>
</section>
<section>
<h3>Motion Actuation (Success Criterion 2.5.4)</h3>
<h3>Motion Actuation
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#motion-actuation">Success Criterion 2.5.4</a>
</p>

<p>Event suspect may be detected automatically but whether there are equivalents for achieving the same thing via user interface components will require a human check.</p>
</section>
<section>
<h3>On Focus (Success Criterion 3.2.1)</h3>
<h3>On Focus
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#on-focus">Success Criterion 3.2.1</a>
</p>

<p>There is currently no reliable way to accurately automate checking whether a change caused by moving focus should be considered a change of content or context.</p>
</section>
<section>
<h3>On Input (Success Criterion 3.2.2)</h3>
<h3>On Input
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#on-input">Success Criterion 3.2.2</a>
</p>

<p>There is currently no reliable way to accurately automate checking whether changing the setting of any user interface component should be considered a change of content or context, or to automatically detect whether relevant advice exists before using the component in question.</p>
</section>
<section>
<h3>Error Identification (Success Criterion 3.3.1)</h3>
<h3>Error Identification
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#error-identification">Success Criterion 3.3.1</a>
</p>

<p>Insuring whether an error message correctly identifies and describes an error accurately currently requires using human judgment.</p>
</section>
<section>
<h3>Labels or Instructions (Success Criterion 3.3.2)</h3>
<h3>Labels or Instructions
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#labels-or-instructions">Success Criterion 3.3.2</a>
</p>

<p>Edge cases (are labels close enough to a component to be perceived as a visible label) will require a human check. Some labels may be programmatically linked but hidden or visually separated from the element to which they are linked. Whether instructions are necessary and need to be provided will hinge on the content. Human check needed.</p>
</section>
<section>
<h3>Error Suggestion (Success Criterion 3.3.3)</h3>
<h3>Error Suggestion
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#error-suggestion">Success Criterion 3.3.3</a>
</p>

<p>Whether a suggestion is helpful / correct currently requires human judgment.</p>
</section>
<section>
<h3>Name, Role, Value (Success Criterion 4.1.2)</h3>
<h3>Name, Role, Value
</h3>
<p class="sc-link">
<a href="https://www.w3.org/TR/WCAG21/#name-role-value">Success Criterion 4.1.2</a>
</p>

<p>Incorrect use of ARIA constructs can be detected automatically but constructs that appear correct may still not work, and widgets that have NO Aria (but need it to be understood) can go undetected. Human post-check of automatic checks is still necessary.</p>
</section>
</section>
Expand Down

0 comments on commit 08099aa

Please sign in to comment.