Merge pull request #2131 from w3c/Understanding-technique-references-…

…nonexistent

Updating technique placeholder

understanding/21/concurrent-input-mechanisms.html

@@ -47,8 +47,8 @@ <h2>Techniques</h2>
 			<section id="sufficient">
 				<h3>Sufficient</h3>
 				<ul>
-          <li>@@ Only using high-level, input-agnostic event handlers (<code>focus</code>, <code>blur</code>, <code>click</code>) in Javascript (operating systems/UAs fire these events for all input mechanisms).</li>
-          <li>@@ Registering event handlers for keyboard/keyboard-like and pointer inputs simultaneously in Javascript (see <a href="https://w3c.github.io/pointerevents/#examples">Example 1 in Pointer Events Level 2</a>)</li>
+          <li>Only using high-level, input-agnostic event handlers, such as <code>focus</code>, <code>blur</code>, <code>click</code>, in Javascript (Potential future technique).</li>
+          <li> Registering event handlers for keyboard/keyboard-like and pointer inputs simultaneously in Javascript; see <a href="https://w3c.github.io/pointerevents/#examples">Example 1 in Pointer Events Level 2</a> (Potential future technique)</li>
         </ul>
 			</section>
 			<section id="failure">

understanding/21/content-on-hover-or-focus.html

@@ -117,8 +117,8 @@ <h2>Techniques</h2>
 				<h3>Sufficient</h3>
 					<ul>
 						<li><a href="../../techniques/client-side-script/SCR39.html">Making content on focus or hover hoverable, dismissible, and persistent</a></li>
-						<li>@@ ARIA: Using role="tooltip"</li>
-						<li>@@ CSS: Using hover and focus pseudo classes</li>
+						<li>ARIA: Using role="tooltip" (Potential future technique)</li>
+						<li>CSS: Using hover and focus pseudo classes (Potential future technique)</li>
 					</ul>
 			</section>
 			<!--<section id="advisory">
@@ -128,8 +128,8 @@ <h2>Advisory</h2>
 				<h2>Failure</h2>
 				<ul>
 					<li><a href="../../techniques/failures/F95.html">F95</a></li>
-					<li>@@ Failure to make content dismissable without moving pointer hover or keyboard focus</li>
-					<li>@@ Failure to meet by content on hover or focus not remaining visible until dismissed or invalid</li>
+					<li>Failure to make content dismissable without moving pointer hover or keyboard focus (Potential future technique)</li>
+					<li>Failure to meet by content on hover or focus not remaining visible until dismissed or invalid (Potential future technique)</li>
 				</ul>
 			</section>
 		</section>

understanding/21/label-in-name.html

@@ -109,15 +109,15 @@ <h2>Advisory Techniques</h2>
                </p>
 				<ul>
 					<li><a href="https://www.w3.org/WAI/GL/2016/WD-WCAG20-TECHS-20160105/G162">G162: Positioning labels to maximize predictability of relationships</a></li>
-					<li>@@ If an icon has no accompanying text, consider using its hover text as its accessible name</li>
+					<li>If an icon has no accompanying text, consider using its hover text as its accessible name (Potential future technique)</li>
 				</ul>
 			</section>
 			<section id="failure">
 				<h2>Failure Techniques</h2>
 				<ul>
 					<li><a href="../../techniques/failures/F96">F96: Failure due to the accessible name not containing the visible label text</a></li>
-					<li>@@ Accessible name contains the visible label text, but the words of the visible label are not in the same order as they are in the visible label text</li>
-					<li>@@ Accessible name contains the visible label text, but one or more other words are interspersed in the label</li>
+					<li>Accessible name contains the visible label text, but the words of the visible label are not in the same order as they are in the visible label text (Potential future technique)</li>
+					<li>Accessible name contains the visible label text, but one or more other words are interspersed in the label (Potential future technique)</li>
 				</ul>
 			</section>
 		</section>

understanding/21/pointer-cancellation.html

@@ -75,7 +75,7 @@ <h3>Sufficient</h3>
 					<ul>
 						<li><a href="../../techniques/general/G210" class="general">G210</a></li>
 						<li><a href="../../techniques/general/G212" class="general">G212</a></li>
-						<li>@@ Touch events are only triggered when touch is removed from a control.</li>		
+						<li>Touch events are only triggered when touch is removed from a control (Potential future technique)</li>		
 					</ul>
 			</section>
 			<!--<section id="advisory">

understanding/21/reflow.html

@@ -96,17 +96,17 @@ <h3>Sufficient Techniques</h3>
             <li><a href="../../techniques/css/C38">C38</a></li>
             <li><a href="../../techniques/client-side-script/SCR34" class="script">SCR34</a></li>
             <li><a href="../../techniques/general/G206" class="general">G206</a></li>
-            <li>@@ New: Using PDF/UA when creating PDFs.</li>
+            <li>Using PDF/UA when creating PDFs (Potential future technique)</li>
         </ul>
     </section>
     <section id="advisory">
         <h2>Advisory Techniques</h2>
        <ul>
          <li><a href="../../techniques/css/C34">C34</a></li>
          <li><a href="../../techniques/CSS/C37">CSS, Fitting images to the viewport;</a></li>
-         <li>@@ CSS, Reflowing simple data tables.</li>
-         <li>@@ CSS, Fitting data cells within the width of the viewport.</li>
-         <li>@@ Mechanism to allow mobile view at any time</li>
+         <li>CSS, Reflowing simple data tables (Potential future technique)</li>
+         <li>CSS, Fitting data cells within the width of the viewport (Potential future technique)</li>
+         <li>Mechanism to allow mobile view at any time (Potential future technique)</li>
          </ul>
 
     </section>

understanding/22/accessible-authentication-no-exception.html

@@ -90,16 +90,16 @@ <h3>Sufficient Techniques for Accessible Authentication</h3>
                 <a href="../../techniques/general/G218.html" class="general">Email link authentication</a>
             </li>
             <li>
-                @@ Providing a properly marked up email and password inputs.
+                Providing a properly marked up email and password inputs (Potential future technique)
             </li>
             <li>
-                @@ Providing WebAuthn as an alternative to username/password.
+                Providing WebAuthn as an alternative to username/password (Potential future technique)
             </li>
             <li>
-                @@ Providing a 3rd party login using oAuth.
+                Providing a 3rd party login using oAuth (Potential future technique)
             </li>
             <li>
-                @@ Using two techniques to provide 2 factor authentication.
+                Using two techniques to provide 2 factor authentication (Potential future technique)
             </li>
          </ol>
 

understanding/22/accessible-authentication.html

@@ -113,16 +113,16 @@ <h3>Sufficient Techniques for Accessible Authentication</h3>
                 <a href="../../techniques/general/G218.html" class="general">Email link authentication</a>
             </li>
             <li>
-                @@ Providing a properly marked up email and password inputs.
+                Providing a properly marked up email and password inputs (Potential future technique)
             </li>
             <li>
-                @@ Providing WebAuthn as an alternative to username/password.
+                Providing WebAuthn as an alternative to username/password (Potential future technique)
             </li>
             <li>
-                @@ Providing a third-party login using oAuth.
+                Providing a third-party login using oAuth (Potential future technique)
             </li>
             <li>
-                @@ Using two techniques to provide two-factor authentication.
+                Using two techniques to provide two-factor authentication (Potential future technique)
             </li>
          </ol>
 

understanding/22/focus-appearance-minimum.html

@@ -362,7 +362,7 @@ <h3>Additional Techniques (Advisory)</h3>
          <h3>Failures</h3>
          <ol>
             <li>
-                @@@ Using a CSS border for inline text which can wrap
+                Using a CSS border for inline text which can wrap (Potential future technique)
             </li>
          </ol>
       </section>

understanding/22/redundant-entry.html

@@ -97,7 +97,7 @@ <h3>Sufficient Techniques for Redundant Entry</h3>
 
          <ul>
             <li><a href="../../techniques/general/G221">"Provide data from a previous step in a process</a></li>
-            <li>@@@ Not requesting the same information twice in multiple steps.</li>
+            <li>Not requesting the same information twice in multiple steps (Potential future technique)</li>
          </ul>
 
       </section>