Fluxglass

Accessibility and fallbacks

The progressive-enhancement and user-preference contract.

Fluxglass is decorative. Keep controls and text as ordinary semantic content inside the surface; the runtime never makes that content aria-hidden.

Preference handling

  • Reduced transparency selects the opaque, system-readable CSS fallback.
  • Forced colors uses Canvas and CanvasText and removes decorative shadowing.
  • Reduced motion starts the performance governor at a conservative tier.
  • The no-effect renderer is available when an application wants to disable decoration entirely.

Browser behavior

Capability detection runs lazily against the element's owning window. Imports are SSR-safe. A browser that cannot render the optical SVG path still receives usable content and a visible CSS surface; the effect is never required to understand or operate the page.

Applications remain responsible for semantic HTML, keyboard behavior, focus styles, contrast of their content, and testing the complete composition in their supported browser matrix.

Vanilla JavaScript

Create and own a Fluxglass DOM controller directly.

Performance

Scheduling, adaptive quality, bundle budgets, and benchmark evidence.

On this page

Preference handlingBrowser behavior