git404hub

what is widget-parity fr?

balyakin/widget-parity — explained in plain English

Analysis updated 2026-07-25

1TypeScriptAudience · developerComplexity · 3/5Setup · moderate

tl;dr

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.

vibe map

mindmap
  root((repo))
    What it does
      Cross-browser testing
      Interaction checks
      Accessibility testing
    Widget catalog
      Button
      Checkbox
      Slider
      Combobox
    Outputs
      JSON report
      HTML report
      CI compatible
    Use cases
      Storybook components
      UI component libraries
      Regression testing
    Limitations
      No touch input
      No closed shadow DOM
      Manual configuration

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Verify a button widget behaves identically in Chrome, Firefox, and Safari.

VIBE 2

Test that keyboard and mouse interactions work correctly in Storybook components.

VIBE 3

Generate CI-compatible reports to catch widget regressions across browser engines.

what's the stack?

TypeScriptPlaywrightStorybookJSONHTML

how it stacks up fr

balyakin/widget-parity0xkinno/neuralvault0xmayurrr/ai-contractauditor
Stars111
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatehardeasy
Complexity3/54/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires a configuration file specifying component URLs and widget patterns, plus a Storybook instance or hosted web page to test against.

in plain english

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.

prompts (copy fr)

prompt 1
Write a WidgetParity config file to test a checkbox component hosted in Storybook, checking keyboard space-to-toggle and click interactions.
prompt 2
Create a WidgetParity configuration for testing a combobox widget at a public URL, verifying focus management and arrow-key navigation across browsers.
prompt 3
Set up a WidgetParity test for a slider component in Storybook, checking pointer drag and keyboard arrow interactions across Chromium, Firefox, and WebKit.
prompt 4
Generate a CI pipeline step that runs WidgetParity tests and publishes the HTML report as an artifact on every pull request.

Frequently asked questions

what is widget-parity fr?

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.

What language is widget-parity written in?

Mainly TypeScript. The stack also includes TypeScript, Playwright, Storybook.

How hard is widget-parity to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is widget-parity for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.