diff --git a/techniques/aria/ARIA24.html b/techniques/aria/ARIA24.html index 31f242ef06..381f71161a 100644 --- a/techniques/aria/ARIA24.html +++ b/techniques/aria/ARIA24.html @@ -15,11 +15,6 @@

Metadata

advisory

-
-

When to Use

-

This technique is applicable to Markup languages that support ARIA.

-
-

Description

diff --git a/techniques/client-side-script/SCR39.html b/techniques/client-side-script/SCR39.html index 4bce0e2862..56f88e344e 100644 --- a/techniques/client-side-script/SCR39.html +++ b/techniques/client-side-script/SCR39.html @@ -29,7 +29,6 @@

Description

Examples

-

Content preview for links

When hovering over or focusing on a link, a content preview for the link appears just above or below that link. diff --git a/techniques/css/C39.html b/techniques/css/C39.html index 84687a78e7..2c5577becf 100644 --- a/techniques/css/C39.html +++ b/techniques/css/C39.html @@ -17,7 +17,7 @@

Metadata

When to Use

-

+

CSS which causes motion that is triggered by user interactions.

diff --git a/techniques/failures/F102.html b/techniques/failures/F102.html index 311c8fb20f..b080c9a30e 100644 --- a/techniques/failures/F102.html +++ b/techniques/failures/F102.html @@ -8,7 +8,6 @@

Failure of Success Criterion 1.4.10 due to content disappearing and not being available when content has reflowed

Metadata

-

Provide information below to help editors associate the technique properly. Contents of the meta section are not output by the processor.

diff --git a/techniques/failures/F105.html b/techniques/failures/F105.html index 6bbbb182ca..a43791e9ac 100644 --- a/techniques/failures/F105.html +++ b/techniques/failures/F105.html @@ -8,7 +8,6 @@

Failure of Success Criterion 2.5.1 due to providing functionality via a path-based gesture without simple pointer alternative

Metadata

-

Provide information below to help editors associate the technique properly. Contents of the meta section are not output by the processor.

Applies to 2.5.1 Pointer Gestures

Failure Technique

@@ -55,14 +54,5 @@

Related Techniques

  • Providing single point activation for a control slider
    • - diff --git a/techniques/failures/F97.html b/techniques/failures/F97.html index 60bb45ac67..a4509cc518 100644 --- a/techniques/failures/F97.html +++ b/techniques/failures/F97.html @@ -14,7 +14,7 @@

    Metadata

    When to Use

    -

    All technologies that allow the viewing of content to be restricted to one orientation.

    +

    All technologies that allow the viewing of content to be restricted to one orientation.

    Description

    diff --git a/techniques/general/G211.html b/techniques/general/G211.html index bb306acccc..cf948ee9d8 100644 --- a/techniques/general/G211.html +++ b/techniques/general/G211.html @@ -14,11 +14,11 @@

    Metadata

    When to Use

    -

    This technique applies to all web technologies that include interactive controls (such as links or form inputs).

    +

    This technique applies to all web technologies that include interactive controls (such as links or form inputs).

    Description

    -

    The objective of this technique is to ensure that speech input users can operate web content reliably while not adversely affecting other users of assistive technology.

    +

    The objective of this technique is to ensure that speech input users can operate web content reliably while not adversely affecting other users of assistive technology.

    When speech input users interact with a web page, they usually speak a command followed by the reference to some visible label (such as text beside an input field or inside a button or link). For example, they may say "click search" to activate a button labelled Search. When speech recognition software processes speech input and looks for matches, it uses the accessible name of controls. Where there is a mismatch between the text in the label and the text in the accessible name, it can cause issues for the user. The simplest way to enable speech input users and meet 2.5.3 Label in Name is to ensure that the accessible name matches the visible text label.

    Determining the appropriate label

    Sometimes more than one text string will be positioned in the vicinity of a control that could be considered a candidate for its label. For example, a set of inputs that each have their own labels may also be preceded by a heading, an instruction or a group label (such as an HTML legend/fieldset or an ARIA group or radiogroup). Note that the term "group label" means something different than "label", both programmatically and in regard to 2.5.3 Label in Name.

    @@ -207,18 +207,15 @@

    Expected Results

    Resources

    -

    Provide links to external resources that are relevant to users of the technique. This section is optional.

    - -
    -

    Resources

    -

    Provide links to external resources that are relevant to users of the technique. This section is optional.

    - -
    diff --git a/techniques/general/G218.html b/techniques/general/G218.html index 9ba522a508..8e08c3b495 100644 --- a/techniques/general/G218.html +++ b/techniques/general/G218.html @@ -13,7 +13,7 @@

    Metadata

    Applicability

    -

    Technologies that support authentication.

    +

    Technologies that support authentication.

    Description

    diff --git a/techniques/general/G219.html b/techniques/general/G219.html index 38cebb61ab..249f4ec9a4 100644 --- a/techniques/general/G219.html +++ b/techniques/general/G219.html @@ -8,7 +8,6 @@

    Ensuring that an alternative is available for dragging movements that operate on content

    Metadata

    -

    Provide information below to help editors associate the technique properly. Contents of the meta section are not output by the processor.

    2.5.X Dragging

    Sufficient

    @@ -56,14 +55,9 @@

    Expected Results

    -
    -

    Resources

    - -
    diff --git a/techniques/general/G220.html b/techniques/general/G220.html index c899d2eb7a..117c490165 100644 --- a/techniques/general/G220.html +++ b/techniques/general/G220.html @@ -13,7 +13,7 @@

    Metadata

    Applicability

    -

    Technologies that contain links

    +

    Technologies that contain links

    Description

    diff --git a/techniques/html/H100.html b/techniques/html/H100.html index c6c226136f..c350bba316 100644 --- a/techniques/html/H100.html +++ b/techniques/html/H100.html @@ -13,7 +13,7 @@

    Metadata

    Applicability

    -

    Technologies that support authentication.

    +

    Technologies that support authentication.

    Description

    diff --git a/understanding/21/animation-from-interactions.html b/understanding/21/animation-from-interactions.html index cc383509e8..d5b51b9378 100644 --- a/understanding/21/animation-from-interactions.html +++ b/understanding/21/animation-from-interactions.html @@ -84,16 +84,6 @@

    Sufficient

  • Gx: Allowing users to set a preference that prevents animation.
    • - diff --git a/understanding/21/identify-changes.html b/understanding/21/identify-changes.html deleted file mode 100644 index d3e11a4d8f..0000000000 --- a/understanding/21/identify-changes.html +++ /dev/null @@ -1,77 +0,0 @@ - - - - - WCAG 2.0 Understanding Page - - - -

    Understanding {Shortname}

    -
    -

    Intent

    -

    This section contains the main explanatory content of the Understanding. It explains why the Guideline or Success Criterion exists and, at a high level, how to meet it.

    -
    -
    -

    Benefits

    -

    This explains how following the success criterion benefits particular types of users with disabilities.

    - -
    -
    -

    Examples

    -

    Examples in Understanding pages are normally simple lists of hand-waving examples. Sometimes, examples are instead provided in sub-sections with headings. In either case, examples should stay high-level and not get into code specifics, which is for techniques.

    - -
    -

    Example

    -
    -
    -
    -

    Resources

    -

    - -
    -
    -

    Techniques

    -
    -

    This section references techniques that can be used to meet the Guideline or Success Criterion. There are sub-sections for sufficient techniques, advisory techniques, and failures.

    - -

    Remove any parts of the template that are not used, such as the section and heading for situations, sub-lists of techniques, or the "AND" construction. Also remove the square brackets around placeholder optional components.

    -
    -
    -

    Sufficient

    -

    Techniques that are sufficient to meet the Guideline or Success Criterion.

    -
    -

    Situation

    -
      -
    • ID [AND ID]* [using] - -
      • -
    -
    -
    -
    -

    Advisory

    -

    Techniques that are not sufficient by themselves to meet the Guideline or Success Criterion.

    -

    Same template as sufficient techniques.

    -
    -
    -

    Failure

    -

    Techniques that document conditions that would cause the page not to meet the Guideline or Success Criterion, even if sufficient techniques are also used.

    -

    Same template as sufficient techniques.

    -
    -
    - - diff --git a/understanding/21/interruptions-minimum.html b/understanding/21/interruptions-minimum.html deleted file mode 100644 index f493e03deb..0000000000 --- a/understanding/21/interruptions-minimum.html +++ /dev/null @@ -1,91 +0,0 @@ - - - - - Understanding Interruptions (Minimum) - - - -

    Understanding Interruptions (Minimum)

    -
    -

    Intent

    -

    The intent of this Success Criterion is to avoid interrupting users during their interaction with a Web page. When users are distracted, especially users with impaired attention or memory, they may forget what they were doing and abandon the task. This can happen even when the original task is extremely important.

    -

    Where a site may generate interruptions, the user must be able to postpone or suppress them, such that:

    - -

    Changes in content that are not initiated by the user must be avoided. Secondary content (such as special offers or complementary material) should be easily identified, controlled and turned off.

    -

    Other potential distractions are covered by existing WCAG Success Criteria Pause, Stop, Hide, Audio Control, Three Flashes or Below Threshold, Low or No Background Audio, Timing Adjustable. These success criteria are aimed at specific considerations which can have repercussions on certain user groups, but also have a broader effect of reducing distractions for all users.

    - -
    -
    -

    Benefits

    - -
    -
    -

    Examples

    -
    -

    Popus can be turned off by the user

    -

    Overlays, such as those designed to notify the user of new features, can be easily toggled off by the user through a 'show no more messages' checkbox on the overlays. Instructions on how to re-enable the overlays are included if the user chooses this option.

    -
    -
    -

    Chat functions can be disabled

    -

    A chat function that offers real-time assistance can be closed by users, so that they are not distracted by new content which appears that is not the result of their actions. A prominent mechanism to re-open the chat function is available.

    -
    -
    -

    Status updates can be turned off by the user

    -

    Status notices which appear in a region of the screen, and which may distract certain users, can be disabled through a checkbox. The same checkbox allows the user to toggle the updates back on.

    -
    -
    - -
    -

    Resources

    - -
    -
    -

    Techniques

    -
    -

    Sufficient

    -

    Techniques that are sufficient to meet the Guideline or Success Criterion.

    -
    -

    Situation

    -
      -
    • ID [AND ID]* [using] - -
      • -
    -
    -
    -
    -

    Advisory

    -

    Techniques that are not sufficient by themselves to meet the Guideline or Success Criterion.

    -

    Same template as sufficient techniques.

    -
    -
    -

    Failure

    -

    Techniques that document conditions that would cause the page not to meet the Guideline or Success Criterion, even if sufficient techniques are also used.

    -

    Same template as sufficient techniques.

    -
    -
    - - \ No newline at end of file diff --git a/understanding/21/label-in-name.html b/understanding/21/label-in-name.html index 83569a2eea..87e2fbd3c5 100644 --- a/understanding/21/label-in-name.html +++ b/understanding/21/label-in-name.html @@ -125,7 +125,6 @@

    Sufficient Techniques

    Advisory Techniques

    -

    Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.

    -
    -

    Resources

    - -

    Techniques

    diff --git a/understanding/21/target-size-enhanced.html b/understanding/21/target-size-enhanced.html index 4fe12313eb..6690225d7c 100644 --- a/understanding/21/target-size-enhanced.html +++ b/understanding/21/target-size-enhanced.html @@ -73,7 +73,6 @@

    Examples

    Resources

    -