Meteor isobuild pipeline and frontend framework a11y tooling: where does accessibility auditing belong?

Integration gap between build pipeline and framework linters

Meteor's isobuild pipeline compiles and bundles application code but does not include accessibility auditing as a built-in step. Frontend frameworks integrated with Meteor — Blaze, React, Vue, and Svelte — each provide their own linting ecosystems (eslint-plugin-jsx-a11y for React, vue-eslint-plugin-accessibility for Vue, etc.), yet Meteor's meteor lint command does not invoke them by default. This creates an integration gap where accessibility violations can reach production without a dedicated CI configuration that developers must assemble manually.

Multi-framework enforcement challenge

The absence of a framework-agnostic a11y layer in Meteor means teams adopting multiple frontend technologies within the same codebase cannot rely on a single enforcement mechanism. Community packages that attempted to bridge this gap have not been maintained since Meteor 2.x, and the core team has not published an official accessibility checklist or CI integration guide as of Meteor 3.0.

• Should Meteor's build pipeline expose a standardized hook for accessibility linters to run during meteor lint or meteor build?
• How can a Meteor application using both Blaze and React share a common accessibility regression strategy without duplicating framework-specific tooling?
• Is there a recommended pattern for integrating axe-core runtime audits into Meteor's hot-module-replacement workflow to catch focus-order regressions early?