Skip to content

Add banner to top of techniques pages, tweak boxout content about techniques #5002

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

Open
patrickhlauke wants to merge 6 commits into
base: main
Choose a base branch
from
+12 −3
Open

Add banner to top of techniques pages, tweak boxout content about techniques #5002

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
40e6e58
Add note/disclaimer box at the top of all techniques
patrickhlauke Mar 17, 2026
aa27cb0
Harmonise boxout content in techniques index and about
patrickhlauke Mar 17, 2026
265de10
Merge branch 'main' into patrickhlauke-techniques-banner
patrickhlauke Mar 19, 2026
0100e3a
Merge branch 'main' into patrickhlauke-techniques-banner
patrickhlauke Apr 5, 2026
970cf66
Move notice into the "About" box. Add conditional for failure techniq…
patrickhlauke Apr 5, 2026
d98760f
Apply suggestions from code review
patrickhlauke Apr 5, 2026
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
5 changes: 5 additions & 0 deletions _includes/techniques/about.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,11 @@ <h2 class="box-h">Obsolete</h2>
</section>
{% endif %}
{% sectionbox "technique" "About this Technique" %}
{% if technique.technology == "failures" %}
<p>Failure examples fail particular WCAG success criteria in isolation, but content can still pass those criteria if it includes additional content or functionality that <strong>does</strong> satisfy the normative requirements. See <a href="about">About WCAG Techniques</a>.</p>
{% else %}
<p>Techniques are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are <strong>not required</strong> to meet WCAG. Content can satisfy the normative requirements of WCAG even if it does not use any of the documented techniques. See <a href="about">About WCAG Techniques</a>.</p>
{% endif %}
{% include "techniques/applicability.html" %}
{% case technique.technology %}
{% when "aria" %}
Expand Down
6 changes: 4 additions & 2 deletions techniques/about.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,11 @@
<main id="main" class="main-content standalone-resource__main">
<h1>About WCAG Techniques</h1>
<aside class="box">
<header class="box-h ">Summary</header>
<header class="box-h">Summary</header>
<div class="box-i">
<p><em>Techniques</em> are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are not required to meet WCAG. To start learning about WCAG, see the <a href="https://www.w3.org/WAI/intro/wcag">WCAG Overview</a>. For important information about techniques, see the <a class="understanding" href="../Understanding/understanding-techniques">Understanding Techniques for WCAG Success Criteria</a> section of Understanding WCAG.</p>
<p>Techniques are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are <strong>not required</strong> to meet WCAG. Content can satisfy the normative requirements of WCAG even if it does not use any of the documented techniques.</p>
<p>Failure examples fail particular WCAG success criteria in isolation, but content can still pass those criteria if it includes additional content or functionality that <strong>does</strong> satisfy the normative requirements.</p>
<p>To start learning about WCAG, see the <a href="https://www.w3.org/WAI/intro/wcag">WCAG Overview</a>. For important information about techniques, see the <a class="understanding" href="../Understanding/understanding-techniques">Understanding Techniques for WCAG Success Criteria</a> section of Understanding WCAG.</p>
</div>
</aside>
<section id="aboutwcag">
Expand Down
4 changes: 3 additions & 1 deletion techniques/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,9 @@ <h1 id="title" class="title p-name">Techniques for WCAG {{ versionDecimal }}</h1
<aside class="box">
<header class="box-h ">Summary</header>
<div class="box-i">
<p><em>Techniques</em> are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are not required to meet WCAG. For information, see <a href="about">About WCAG Techniques</a>.</p>
<p>Techniques are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are <strong>not required</strong> to meet WCAG. Content can satisfy the normative requirements of WCAG even if it does not use any of the documented techniques.</p>
<p>Failure examples fail particular WCAG success criteria in isolation, but content can still pass those criteria if it includes additional content or functionality that <strong>does</strong> satisfy the normative requirements.</p>
<p>For information, see <a href="about">About WCAG Techniques</a>.</p>
</div>
</aside>

Expand Down
Loading