original text

3.20 Avoid Using Deprecated or Proprietary Code

The Web is full of dead, often proprietary code, created using standards that have been superseded or by groups that aren't recognized. By following recognized coding standards, you ensure that your code will be rendered properly by browsers (and reduce the potential for added emissions occurring from unmaintained rendering processes).

Success Criterion - Deprecated Code
Exclude deprecated formats and standards, the only exception being if consumer support demands maintaining older standards to provide a functional product.

Success Criterion - Outdated Code (Machine Testable)
Don't use an older standard if a newer recommendation will do the same job as / or more effectively.

Suggested text

3.20 Avoid Using Deprecated or Outdated Web Standards

The web is full of outdated or deprecated formats and web standards that have been superseded. By adhering to up-to-date and widely recognized formats and web standards, developers can ensure better compatibility, user experience, and lower environmental impact.

Success Criterion – Deprecated or Outdated Formats or Web Standards (Machine Testable)
Avoid the use of deprecated or outdated formats and web standards. Always adopt modern, widely recognized standards that offer equivalent or improved functionality. Exceptions may be allowed only when consumer needs require maintaining older formats to ensure product functionality, unless they do not negatively impact accessibility.

reasons

• Removed "Proprietary Code" since the section doesn't mention proprietary code specifically.
• Merge the criteria in a single criterion. Merging eliminates confusion about the difference between "Deprecated" and "Outdated" which overlaps in the idea. Opportunity to use "unless they do not negatively impact accessibility" only once.