Browser compat website checks

Browser compatibility checks compare the public interface across the engines and conditions included in a scan. A missing fallback, unsupported feature or failed resource can change the result between browsers. Coverage is bounded by tested engines, states and viewports. A passing result does not promise support for every historical browser or operating system. State your supported environments explicitly.

Start with the smallest reproducible difference. Inspect console errors, failed requests and computed layout before adding browser-specific workarounds. Prefer progressive enhancement when a feature is optional. Exercise navigation, forms and focus in the environments your audience uses; screenshots cannot prove interaction. Keep exclusions explicit so an untested engine is never reported as a verified pass.

The check pages below describe the exact observable condition, why it matters, practical fixes and the limits of the detector. Open the affected URL and inspect its evidence before making a change. After correction, repeat the scan and verify the result in a browser. The related guide connects these individual checks into a review workflow. Keep deliberate exceptions documented so that a passing automated result is never mistaken for a complete manual assessment.