Narrow container
240px inline space
Stack gradient, shadow, border radius, and glass blur into one component, then use Chaos Mode to expose overflow, contrast, RTL, text-scaling, and focus risks before you ship.
.my-element {
background: linear-gradient(135deg, #4f46e5 0%, #ec4899 100%);
box-shadow: 0px 18px 40px -12px rgba(79, 70, 229, 0.45);
border-radius: 28px 28px 28px 28px;
border: 1px solid rgba(255, 255, 255, 0.35);
}Tip: press Space to randomize the entire combo.
Chaos Mode
Six hostile-context previews run entirely in your browser. Results are best-effort signals, not a replacement for testing in your product.
240px inline space
A hostile long token
English content forced into RTL
Text scaling simulation, not browser zoom
Painted on a near-black parent
Press Tab to inspect focus readiness
No measured overflow at 240px
Long token stays contained
Forced RTL content stays contained
Scaled text stays contained
Component bounds remain stable
6.29:1 and 3.53:1 vs white
Not present in the generated combo; supplied by the optional patch
Current combo output adds no animation
Copy this separately when you want safer wrapping, visible keyboard focus, forced-colors support, and reduced motion. It does not change the main export.
.my-element {
max-inline-size: 100%;
overflow-wrap: anywhere;
isolation: isolate;
}
.my-element:focus-visible {
outline: 3px solid currentColor;
outline-offset: 3px;
}
@media (forced-colors: active) {
.my-element {
border: 1px solid CanvasText;
}
}
@media (prefers-reduced-motion: reduce) {
.my-element {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
scroll-behavior: auto !important;
}
}Instead of copying five separate snippets from five different tools, you get one finished, ready-to-paste component combining all the effects together.
Yes — use the export format tabs above the code block to switch between raw CSS, Tailwind arbitrary values, and a styled-components snippet.
It combines browser-measured overflow checks in six hostile contexts with a WCAG contrast estimate for both gradient endpoints, plus focus and motion readiness checks. Treat it as an early warning system, then test the component in your real interface.
No. It is a separate, optional snippet you can copy when you want safer text wrapping, keyboard focus, forced-colors support, and reduced-motion behavior.