Analysis updated 2026-07-25
Verify a button widget behaves identically in Chrome, Firefox, and Safari.
Test that keyboard and mouse interactions work correctly in Storybook components.
Generate CI-compatible reports to catch widget regressions across browser engines.
| balyakin/widget-parity | 0xkinno/neuralvault | 0xmayurrr/ai-contractauditor | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | hard | easy |
| Complexity | 3/5 | 4/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a configuration file specifying component URLs and widget patterns, plus a Storybook instance or hosted web page to test against.
WidgetParity is a testing tool that checks whether web components, like buttons and checkboxes, behave the same way across the three major browser engines: Chromium, Firefox, and WebKit. It runs automated checks on keyboard input, pointer interactions, focus management, form behavior, and accessibility attributes. After running, it produces a report in several formats including JSON, HTML, and files compatible with CI pipelines. The tool is designed to work with components hosted in Storybook or at specific web addresses. You set up a configuration file telling it which component to test and which interaction pattern to apply, such as a button or a slider. It then runs a series of rules against that component and reports any findings. For example, it can detect when a button incorrectly activates after you press it, move the mouse outside, and then release, which is a broken behavior. The project positions itself as a complement to other testing methods rather than a replacement. Tools like axe scan the HTML structure for accessibility issues but cannot simulate multi-step interactions. Visual regression tools catch pixel-level changes but cannot verify that focus moves correctly or that form semantics work. Handwritten test scripts offer flexibility but require ongoing maintenance. WidgetParity targets the specific contract of how a widget should respond to user input. The current version is labeled experimental (v0.1) and comes with clear limitations. It cannot test touch or multi-touch input, inspect closed shadow roots, measure rendering performance, crawl pages automatically, or infer component patterns on its own. Results are also not an official accessibility certification. The tool requires explicit configuration and does not guess what a component is supposed to do. The v0.1 catalog covers ten common widget patterns: button, checkbox, radio group, switch, textbox, slider, combobox, tabs, menu, and dialog. Security is handled carefully, with fresh browser contexts per scenario and reports that strip out sensitive data like credentials, cookies, and raw user input.
A testing tool that checks whether web components like buttons and sliders behave consistently across Chromium, Firefox, and WebKit browsers by simulating real user interactions.
Mainly TypeScript. The stack also includes TypeScript, Playwright, Storybook.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.