Skip to content

Commit

Permalink
Merge branch 'conformance-challenges-working-draft_Detlev1' into conf…
Browse files Browse the repository at this point in the history 
…ormance-challenges-working-draft

Challenge #1 additions by Detlev Fischer
  • Loading branch information
@sajkaj
sajkaj committed Nov 25, 2019
2 parents 1d3bac7 + 1eb5df3 commit ffa6b10
Showing 1 changed file with 113 additions and 0 deletions.
113 changes: 113 additions & 0 deletions conformance-challenges/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,7 @@ <h3><a href="https://www.w3.org/TR/WCAG21/#identify-input-purpose">Identify Inpu
<h3><a href="https://www.w3.org/TR/WCAG21/#use-of-color">Use of Color (Success Criterion 1.4.1)</a></h3>
<p>This poses the same challenges as Sensory Characteristics (<a href="https://www.w3.org/TR/WCAG21/#sensory-characteristics">Success Criterion 1.3.3</a>).  To discern whether a page fails this criterion programmatically requires understanding the full meaning of the related content on the page and whether any meaning conveyed by color is somehow also conveyed in another fashion (e.g. whether the meaning of the colors in a bar chart is conveyed in the body of associated text or with a striping/stippling pattern as well on the bars, or perhaps some other fashion).</p>
</section>

<section>
<h3><a href="https://www.w3.org/TR/WCAG21/#audio-control">Audio Control[36] (Success Criterion 1.4.2)</a></h3>
<p>An automated test tool would be able to identify media/audio content in a website, identify whether auto-play is turned on in the code, and also determine the duration. However, an automated checking tool
Expand Down Expand Up @@ -132,11 +133,123 @@ <h3><a href="https://www.w3.org/TR/WCAG21/#non-text-contrast">Non-text Contrast
<h3><a href="https://www.w3.org/TR/WCAG21/#text-spacing">Text Spacing[45] (Success Criterion 1.4.12)</a></h3>
<p>This success criterion involves using a tool or method to modify the text spacing and then checking to ensure no content is truncated or overlapping. This is purely a manual process.</p>
</section>
<section>
<h3>Content on Hover or Focus (Success Criterion 1.4.13)</h3>
<p>As content needs to be brought up by hovering the pointer over it (or
keyboard-focus it) to then determine whether the 3 criteria of 1.4.13 are met,
this is by necessity a human test.</p>
</section>
<section>
<h3><a href="https://www.w3.org/TR/WCAG21/#keyboard">Keyboard Operable[47] (Success Criterion 2.1.1)</a></h3>
<p>To ensure keyboard operability of all functionality, it requires a very manual process of navigating through the 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>
<p>single key presses can be applied to content via a script but whether and
what these keypresses trigger can only determined by additional human
checks.</p>
</section>
<section>
<h3>Timing Adjustable (Success Criterion 2.2.1)</h3>
<p>There is no easy way to check automatically whether timing is adjustable. Ways of controlling differ both in naming, position and approach (including dialogs/popups before the time-out) and depend on the way 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>
<p>Typically the requirement to control moving content id provided by some interactive controls placed in the vicinity of moving content, or rarely on a general level at the beginning of content. The fact that position
and naming vary means that an assessment is mostly human task (it will
involve checking that the function works as expected).</p>
</section>
<section>
<h3>Three Flashes or Below Threshold (Success Criterion 2.3.1)</h3>
<p>May be automatable but it involved an assessment of the area of flashing,
so probably human. As this Failure hardly ever occurs, I just mention it for
completeness.</p>
</section>
<section>
<h3>Bypass Blocks (Success Criterion 2.4.1)</h3>
<p>You can determine whether native elements or landmark roles are used but probably not if 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>
<p>Easy to check automatically whether the page has a title but the
descriptive check is a human one. Matching title to h1 will not cover pass
cases where title and h1 differ.</p>
</section>
<section>
<h3>Focus Order (Success Criterion 2.4.3)</h3>
<p>Focus handling with dynamic content (move content to custom dialog, keep
focus in dialog, return to trigger) do not look like they will be automatable
any time soon.</p>
</section>
<section>
<h3>Link Purpose (Success Criterion 2.4.4)</h3>
<p>Automated can check for the existence of same named links and probably check whether they are qualified programmatically, but checking whether the context adequately serves to describe link purpose seems like still
involving human judgment.</p>
</section>
<section>
<h3>Multiple ways (Success Criterion 2.4.5)</h3>
<p>Automatically checking the presence of several ways (e.g. nav and search) helps but may miss cases where exceptions hold (all pages can be reached from anywhere) so needs a human check? But maybe algorithms already
exist to check that.</p>
</section>
<section>
<h3>Headings and Labels (Success Criterion 2.4.6)</h3>
<p>The determination 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>
<p>I am not aware of an automated check that would 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>
<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>
<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>
<p>I suspect it is hard to check automatically whether a change caused by
focusing should be considered a change of content or context.</p>
</section>
<section>
<h3>On Input (Success Criterion 3.2.2)</h3>
<p>I suspect it is hard to check automatically whether a change caused by inputting stuff should be considered a change of content or context, or to automatically detect whether relevant advice exist before the
component in question.</p>
</section>
<section>
<h3>Error Identification (Success Criterion 3.3.1)</h3>
<p>Whether the error message correctly identifies and describes the error will
often involve human judgment.</p>
</section>
<section>
<h3>Labels or Instructions (Success Criterion 3.3.2)</h3>
<p>Edge cases (are labels close enough to a component to be perceived as a visible label) will need human check. Some label may be programmatically linked but hidden or far off. Whether instructions are necessary and
need to be provided will hinge of the content. Human check needed.</p>
</section>
<section>
<h3>Error Suggestion (Success Criterion 3.3.3)</h3>
<p>Whether a suggestion is helpful / correct will often involve human
judgment.</p>
</section>
<section>
<h3>Name, Role, Value (Success Criterion 4.1.2)</h3>
<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 would need it to be understood) can go undetected. Human
post-check of automatic checks seems necessary.</p>
</section>
</section>
<section>
<h2>Challenge #2: Large, complex, and dynamic websites are always “under construction”</h2>
Expand Down

0 comments on commit ffa6b10

Please sign in to comment.