AI Weekly Malaysia

Chris Burnell's page catalogs native HTML features that replace common JavaScript patterns, including the `popover` attribute (with `popovertarget` and `popovertargetaction`) for tooltip/menu-style overlays and the `<dialog>` element for modal boxes. The page was built for HTML Day 2026 and later updated to flag where browser implementations fall short on accessibility. It includes live code snippets showing how to toggle popovers and open/close dialogs with zero JavaScript.

Why: If you're shipping UI components like popovers, modals, or dialogs, you can likely delete custom JS and z-index management by switching to the native `popover` attribute and `<dialog>` element—but you must test accessibility carefully, as the author explicitly warns browser support for some of these features is still incomplete.

Independent developer Théo Ducreux's ValidateHTML project crawled the 5,000 most-visited web domains (per the Tranco list) and found 87.2% have at least one HTML spec violation, with only 2.6% returning zero errors and zero best-practice warnings. Over a third failed accessibility checks—20.4% are missing image alt text and 41.6% lack ARIA labels for page regions—making pages broken for screen readers even when they render fine in Chrome.

Why: If you ship web frontends to EU customers, the 2025 European Accessibility Act turns these accessibility failures into legal liability, not just bad practice. Run an HTML validator and an accessibility audit (e.g., axe, Lighthouse) on your pages before your next release—41.6% of top sites missing ARIA labels means your site probably does too.