Category: WCAG Principles and Conformance

Advisory Techniques

Simply put

Advisory techniques are suggested ways to make web content more accessible that go beyond the minimum requirements needed to meet the Web Content Accessibility Guidelines (WCAG). They are not required for conformance, but they are often very helpful to some users and may sometimes be the only way certain users can access content. Following them can improve the overall accessibility experience even though they are optional.

Formal definition

In the W3C's WCAG documentation, advisory techniques are one category of techniques described in the Understanding documents, distinguished from sufficient techniques and common failures. Unlike sufficient techniques, advisory techniques are not sufficient to meet a success criterion and are not required for conformance at any level (A, AA, or AAA); they are non-normative suggestions that go beyond what individual success criteria require. They are documented because they can offer meaningful accessibility benefits, may address usability considerations not fully captured by testable success criteria, and in some cases represent the only means by which particular users can access content. Implementers should treat advisory techniques as recommended enhancements rather than compliance obligations, and should note that conformance is defined by satisfying success criteria, not by adopting any specific set of techniques.

Why it matters

Advisory techniques matter because WCAG conformance is defined by satisfying testable success criteria, and those criteria cannot capture every barrier a real user may encounter. Advisory techniques fill part of that gap. They are documented by the W3C precisely because they can be very helpful to some users, and in some cases they may be the only way that particular users can access content. Treating accessibility as a matter of meeting the minimum bar alone can leave usability gaps that harm people even when a page technically conforms.

For compliance officers and accessibility teams, the distinction is important to keep straight: adopting advisory techniques is not required for conformance at any level (A, AA, or AAA), so an implementer should not be penalized in a conformance evaluation for skipping them, nor should adopting them be mistaken for a substitute for meeting the applicable success criteria. At the same time, ignoring them entirely can produce experiences that satisfy the letter of the guidelines while still falling short for some users. Because conformance does not by itself guarantee an accessible experience for everyone, advisory techniques are one of the practical tools for closing that distance.

This entry describes how the W3C categorizes techniques within its non-normative supporting documentation and is not legal advice. Whether any particular measure is required in a given context depends on applicable law, regulation, and case law, which evolve over time; consult qualified legal counsel for questions about specific obligations.

Who it's relevant to

Accessibility engineers and developers

Advisory techniques give developers concrete, optional ways to improve the experience beyond the minimum success criteria. Knowing which techniques are advisory versus sufficient helps teams prioritize work and avoid mistaking optional enhancements for conformance requirements.

UX and content designers

Because advisory techniques often address usability considerations that testable success criteria do not fully capture, they are useful reference points for designers aiming to serve a broader range of users. They can inform design decisions that make content more usable even where no success criterion mandates a specific approach.

Compliance officers and accessibility program leads

Program leads need to keep the categories distinct: advisory techniques are not required for conformance at any level, so they should not be counted against a conformance evaluation, but they also should not be presented as evidence of conformance. This distinction helps set accurate expectations in accessibility policies and audits.

Legal counsel

Counsel evaluating accessibility posture should understand that advisory techniques are non-normative suggestions and are not part of the testable conformance requirements. Whether adopting or omitting any specific measure carries legal significance depends on applicable law and case law rather than on the technique category itself, and this material is not a substitute for legal advice.

Inside Advisory Techniques

Advisory Techniques

A category of techniques documented by the W3C in supporting materials for WCAG that go beyond what is strictly required to satisfy a success criterion. They describe ways to improve accessibility that authors are encouraged, but not obligated, to implement for conformance.

Relationship to Success Criteria

Unlike sufficient techniques, advisory techniques are not tied to meeting a specific success criterion at a given conformance level. Failing to implement an advisory technique does not, by itself, cause a failure of WCAG conformance.

Non-Normative Status

Advisory techniques are informative rather than normative. The normative requirements of WCAG are the guidelines, success criteria, and conformance requirements themselves; techniques are guidance published to help authors meet those requirements.

Purpose and Value

They often address usability enhancements, accessibility for user groups or scenarios not fully covered by the testable success criteria, or improvements that are difficult to test objectively. They can help move toward a more usable experience beyond minimum conformance.

Distinction from Sufficient and Failure Techniques

W3C technique documentation commonly separates sufficient techniques (one way to meet a criterion), failure techniques (patterns known to cause failures), and advisory techniques (recommended but optional improvements).

Common questions

Answers to the questions practitioners most commonly ask about Advisory Techniques.

Are advisory techniques required to conform to WCAG?

No. Advisory techniques are not required for conformance. WCAG success criteria are met through sufficient techniques (or any method that satisfies the criterion), and advisory techniques are offered by the W3C as optional suggestions that go beyond what a success criterion strictly requires. Implementing them can improve accessibility for some users, but omitting them does not, by itself, mean a page fails WCAG.

Does using advisory techniques guarantee an accessible or legally compliant experience?

No. Advisory techniques are one input into accessibility, not a guarantee. Meeting or exceeding WCAG techniques does not ensure an accessible experience for every user, and it does not guarantee immunity from legal claims. Automated checks detect only a portion of issues, so manual and assistive technology testing remain necessary. This is general information and not legal advice; consult qualified counsel for questions about compliance.

How do advisory techniques differ from sufficient techniques in WCAG?

Sufficient techniques are documented ways the W3C indicates are enough to satisfy a given success criterion, while advisory techniques are additional, optional approaches that can enhance accessibility beyond the criterion's minimum. When evaluating conformance, focus on whether the success criterion is met; treat advisory techniques as opportunities for further improvement rather than pass/fail items.

When should a team consider adopting advisory techniques?

Teams commonly consider advisory techniques when they want to improve usability for specific user groups, address feedback from assistive technology users, or go beyond a baseline conformance target such as WCAG AA. They can be prioritized where they offer meaningful benefit to real users, balanced against other accessibility work and available resources.

Where can teams find the advisory techniques associated with a success criterion?

The W3C publishes techniques alongside each success criterion in its supporting documentation for WCAG, grouping them into sufficient, advisory, and failure categories. Reviewing the 'Understanding' material and technique listings for a given criterion helps teams distinguish which methods are advisory from those the W3C treats as sufficient.

How should advisory techniques factor into accessibility testing and audits?

Because advisory techniques are optional, they are generally not scored as conformance failures in an audit. They can, however, be captured as recommendations or enhancement opportunities. Since automated tools catch only part of the picture, pairing them with manual review and assistive technology testing is the more reliable way to identify both conformance gaps and areas where advisory techniques would help.

Common misconceptions

Implementing advisory techniques is required to conform to WCAG.

Advisory techniques are optional. WCAG conformance is determined by meeting the applicable success criteria; not implementing an advisory technique does not cause a conformance failure. They are encouraged enhancements rather than requirements.

Ignoring advisory techniques means an experience is fully accessible as long as success criteria are met.

Meeting success criteria does not guarantee an accessible or usable experience for all users. Advisory techniques often address gaps that the testable criteria do not fully cover, so they may meaningfully improve real-world usability with assistive technology even though they are not mandatory.

Advisory techniques are part of the normative WCAG standard.

Techniques, including advisory ones, are informative supporting material published by the W3C, not normative requirements. The normative content is the guidelines, success criteria, and conformance requirements.

Best practices

Treat advisory techniques as opportunities to improve usability beyond minimum conformance, not as a checklist for passing WCAG.

First confirm that applicable success criteria are met using sufficient techniques, then consider relevant advisory techniques for additional user benefit.

Prioritize advisory techniques that address the needs of the user groups and scenarios most relevant to your product or audience.

Combine any technique work with manual and assistive technology testing, since automated checks and technique lists alone detect only a portion of real accessibility issues.

Consult current W3C technique documentation to distinguish advisory techniques from sufficient and failure techniques, and to confirm current guidance.

Document which advisory techniques were adopted and why, but do not represent their implementation as guaranteeing legal compliance; consult qualified legal counsel for compliance questions.