Advisory Techniques — Going Beyond WCAG Minimum Requirements

In this tutorial, you will learn about Advisory Techniques. We cover key concepts, practical examples, and best practices to help you master this topic.

WCAG advisory techniques are recommended practices that improve Accessibility beyond success criteria requirements, addressing edge cases and enhancing user experience for people with specific disabilities.

What You'll Learn

You will learn what advisory techniques are, how they differ from sufficient techniques, and how to implement common advisory techniques to improve your site's accessibility.

Why It Matters

Sufficient techniques help you meet the minimum. Advisory techniques help you exceed it. Going beyond the minimum creates better experiences for users with disabilities and differentiates your product.

Real-World Use

DodaTech implements advisory techniques as part of its accessibility standard. Durga Antivirus Pro includes advisory techniques like providing keyboard shortcuts for power users and supporting high contrast mode.

flowchart TD
  A[Advisory Techniques] --> B[Not required for conformance]
  A --> C[Improve user experience]
  A --> D[Address edge cases]
  B --> E[Go beyond success criteria]
  C --> F[Faster task completion]
  C --> G[Less frustration]
  D --> H[Rare but impactful scenarios]

Advisory vs Sufficient

Common Advisory Techniques

Providing Keyboard Shortcuts

Keyboard shortcuts help power users complete tasks faster. They are not required by WCAG beyond the basic keyboard access requirement.

<!-- Advisory: keyboard shortcut for search -->
<script>
document.addEventListener('keydown', (e) => {
  if ((e.ctrlKey || e.metaKey) && e.key === 'k') {
    e.preventDefault();
    document.getElementById('search').focus();
  }
});
</script>

Supporting High Contrast Mode

Windows High Contrast Mode is used by some users with low vision. Supporting it ensures your interface remains usable.

@media (prefers-contrast: high) {
  :root {
    --text: #000000;
    --background: #ffffff;
    --primary: #0000ff;
  }
  .card {
    border: 2px solid currentColor;
  }
}

Providing Skip Links in Multiple Locations

While one skip link meets 2.4.1, providing multiple skip links for different sections improves navigation efficiency.

Using Icons with Text Labels

Icons paired with text labels help users with cognitive disabilities and users who are not familiar with icon conventions.

<!-- Advisory: icon with text label -->
<button onclick="deleteItem()">
  <span aria-hidden="true">&#128465;</span> Delete item
</button>

Grouping Related Form Fields

Using fieldset and legend for related form fields helps users with cognitive disabilities understand form structure.

<fieldset>
  <legend>Scan Settings</legend>
  <label><input type="checkbox" name="quick"> Quick scan</label>
  <label><input type="checkbox" name="full"> Full system scan</label>
</fieldset>

Providing Estimated Reading Time

Reading time helps users with cognitive disabilities plan their attention span.

<p>Reading time: 5 minutes</p>

When to Implement Advisory Techniques

After meeting all applicable success criteria at your target level. Prioritize advisory techniques that address your users' needs. Implement those with high impact and low effort first.

Common Mistakes

1. Implementing Advisory Instead of Sufficient

Advisory techniques do not substitute for sufficient techniques. Meet the criteria first, then enhance.

2. Ignoring All Advisory Techniques

Advisory techniques differentiate your product. Ignoring them means missing opportunities to improve user experience.

3. Prioritizing Advisory Over Essential Fixes

Fix all Level A and AA violations before adding advisory enhancements. The foundation must be solid.

4. Not Testing Advisory Techniques

Advisory techniques should still be tested. A poorly implemented advisory technique can create barriers.

5. Assuming All Advisory Techniques Are Valuable

Evaluate each advisory technique for your specific users. Not all techniques are equally valuable in all contexts.

6. Forgetting to Document Advisory Techniques

Document which advisory techniques you implemented. This supports your accessibility story.

7. Never Revisiting Advisory Techniques

As your product evolves, new advisory techniques may become relevant. Review periodically.

Practice Questions

1. What is the difference between sufficient and advisory techniques?

Sufficient techniques are required for conformance. Advisory techniques are recommended but optional.

2. When should you implement advisory techniques?

After meeting all applicable success criteria at your target conformance level.

3. Is providing keyboard shortcuts a sufficient or advisory technique?

Advisory. WCAG requires keyboard access to all functionality but additional shortcuts are optional enhancements.

4. What is an example of an advisory technique for form accessibility?

Grouping related fields with fieldset and legend to help users understand form structure.

5. Challenge: Review your website and identify three advisory techniques you could implement. Estimate the effort for each and prioritize.

FAQ

Mini Project

Create a prioritized list of advisory techniques for your project. Group them into high impact / low effort, high impact / high effort, low impact / low effort, and low impact / high effort.

What's Next

Learn about Common Failures to understand what patterns violate WCAG criteria. Then explore Understanding Documents for authoritative guidance.