HTML & accessibility
Checks disabled, readonly, inert, hidden and ARIA states to identify direct causes of non-interactivity.
WhyUI is a browser developer tool that explains why an element is disabled, hidden, readonly, covered, or otherwise non-interactive using deterministic browser-visible evidence.
Instead of manually inspecting dozens of DOM and CSS properties, WhyUI brings the relevant browser-visible evidence together in one developer-friendly view.
Checks disabled, readonly, inert, hidden and ARIA states to identify direct causes of non-interactivity.
Examines pointer events, visibility, display, opacity, dimensions and other computed browser state.
Walks the element hierarchy to find disabled fieldsets, inert ancestors, hidden containers and blocking parents.
Checks whether another visible layer is intercepting the element at its viewport coordinates.
Surfaces browser constraint-validation states such as required fields, type mismatch and pattern errors.
Tracks relevant DOM mutations so you can see when an element changes from enabled to disabled or back.
A focused workflow designed to keep you in the page while you investigate a UI problem.
Activate WhyUI and pick the UI element you want to understand.
WhyUI inspects HTML, CSS, ancestors, overlays and validation state.
Evidence is grouped into clear confidence levels and reasons.
Use the explanation to locate the relevant condition in your application.
Found an edge case or want to contribute? WhyUI is open source and feedback is welcome.
If WhyUI behaves unexpectedly, include your Edge version, WhyUI version, the type of element, and reproducible steps when opening an issue.
Open a GitHub issue ↗WhyUI is designed as a local-first developer tool. Page analysis is performed in your browser without requiring an account or backend service.
View source ↗