back to CanAdapt home

Revised Diagram WCAG Extension model

Diagram of how WCAG extensions could relate to the current WCAG 2 Integration. Description follows.

Diagram of how WCAG extensions could relate to the current WCAG 2 Integration. The task forces, Mobile, Cognitive, and Low Vision would develop guidelines, success criteria and techniques separately, and then integrate them to resolve conflicts and overlaps and then integrate them into the singular WCAG extension. The techniques and Understanding documents would be collected in a non normative document as techniques for the extension, and some of them can be referenced from WCAG 2 where the techniques might apply to an existing Success criteria. WCAG 2 will never change, so the extension circle is not required to meet WCAG 2 but if some jurisdiction requires "WCAG2 + Extension", then it would be required in addition to WCAG. That is why it is in the normative box... Normative means it will go through a formal acceptance procedure which is very rigorous. Once something is declared normative it is very hard to change... that would be any Guidelines and Success Criteria that the task forces make, and are approved. Techniques and Understanding documents are non-normative, and can be updated fairly easily.

Previous diagram (deprecated)

Diagram of how WCAG extensions could relate to the current WCAG 2 Integration. Description follows.

Diagram of how WCAG extensions could relate to the current WCAG 2 Integration. The task forces, Mobile, Cognitive, and Low Vision would develop guidelines, success criteria and techniques separately, and then integrate them to resolve conflicts and overlaps and then integrate them into the singular WCAG extension. The techniques would be collected in a non normative document as techniques for the extension, and some of them can be referenced from WCAG 2 where the techniques might apply to an existing Success criteria.