Can Vite automate accessibility meta tags via transformIndexHtml?

Accessibility Defaults in Vite Templates

Vite provides a lean default template for index.html, which currently lacks built-in accessibility defaults such as the <meta name="viewport"> tag. While developers can manually add these tags, there is no core mechanism to ensure consistent accessibility standards across different project initializations.

Plugin API Constraints

The transformIndexHtml hook allows plugins to programmatically modify the HTML before it is served. However, implementing automatic injections of accessibility attributes or <noscript> fallbacks introduces a design conflict: automatic injection may override intentional developer configurations or conflict with framework-specific viewport management.

Given the current architecture of Vite (v5+), what is the recommended approach for implementing standardized accessibility injections without risking regressions in custom HTML structures? Does the core team intend to introduce optional accessibility presets within the configuration, or should this remain strictly within the community plugin ecosystem?