2.29 Regularly test and maintain compatibility

Produce a regularly updated compatibility policy that details support levels, scenarios tested against, and technology used to benefit users.

Criteria

Compatibility policy: Machine-testable
Establish and maintain a compatibility policy which covers current and obsolete devices and software versions, listing the supported device brands, operating systems, and browsers (including versions). Update this regularly in line with new releases.
Maintaining compatibility: Machine-testable
Avoid planned obsolescence. Strive to maintain compatibility for as long as possible and communicate clearly whether an update is evolutionary, as in large updates that can significantly reduce performance, or corrective, as in smaller updates that fix bugs or improve security.
Frequent testing: Machine-testable
Test performance in various scenarios to ensure compatibility. Testing should cover weak, unstable, restricted, or slow connections, old browsers, and devices older than five years.
Mobile friendly: Human-testable
Use device-adaptable methods such as responsive design and prototype interfaces to support progressive enhancement and content prioritization.
Progressive Web Applications (PWAs): Machine-testable
Use a PWA over a native mobile application if it meets sustainability, interoperability, and compatibility criteria.

Benefits

Accessibility
Incorporating accessibility into early prototypes ensures it remains a priority throughout the lifecycle. Broken code can also impact assistive technologies, such as screen readers, and how they describe content to individuals with visual disabilities. Semantic code can help to deliver an equal, error-free experience to all.
Conversion
Delivering products and services that last longer and enjoy longer-lasting compatibility can increase conversion rates, due to the lower abandonment rates and a broader audience that is able to use a barrier-free version of the product or service.
Economic
Saving time and improving quality results in cost reductions, because increased stability reduces the need for refactoring. Users benefit from greater trust and potentially lower costs and maintenance fees as upgrades may not be required as frequently.
Environment
Avoiding incompatibility issues can significantly reduce e-waste, with planned obsolescence being is one of the biggest contributors to e-waste worldwide.Extending lifespans and improving compatibility within your service plan can improve sustainability and slow the upgrade cycle otherwise driven by sluggish digital experiences.
Performance
Deploying incompatible code has an energy cost. When code is non-standard, deprecated or does not work on a device, it can take additional time to render because it is usually not optimized for the environment. This puts pressure on the CPU and wastes battery. Using modern web standards will help your service run reliably in modern browsers.
Social Equity
Enhancing compatibility and longevity helps to reduce the digital divide. This can be significant in relation to income inequality, infrastructure robustness, or accessibility, for example. Broader support can therefore open your work to new markets, or extend the viability of existing access. Similarly, because progressive web applications use established web standards, they are available to more people than more cost-prohibitive closed systems.

GRI

Materials: High
Energy: High
Water: High
Emissions: High

View the Guideline

2.29 Regularly test and maintain compatibility

Criteria

Benefits

GRI

Tags