Update README.md

README.md

@@ -14,6 +14,26 @@ A11YBench consists of 60 real-world web projects, encompassing 147 web pages and
 The projects vary substantially in size, from 123 to 43,198 source files and from 3,610 to 1,555,532 lines of code, covering both lightweight documentation sites and large production-grade applications.
 This scale ensures that A11YBench reflects the structural and technical diversity of modern web ecosystems.
 
+## 🔍Dataset Collection
+
+We consider real, actively maintained GitHub repositories implementing production websites using JavaScript or TypeScript, including frameworks such as React, Next.js, Vue, and static site generators. 
+Using GitHub's search with keyword `website` and language filters `JavaScript`, `TypeScript`, we sort by `Best Match` and collect the top 500 repositories for screening. 
+We select repositories showing active maintenance by keeping those with over 100 total pull requests, 10 stars, and at least one commit within the past month. 
+After manual verification of setup documentation and reproducibility.
+
+To ensure reproducibility, we keep only projects that can be successfully built and executed in a local environment. 
+Following prior benchmark practices (e.g., [SWE-bench](https://huggingface.co/datasets/SWE-bench/SWE-bench_Multimodal), we manually follow installation guides, resolve dependencies, and verify successful local deployment. 
+Projects lacking clear setup instructions or exhibiting build or runtime errors are discarded. 
+For each successfully deployed project, we manually inspect the homepage and linked subpages to ensure correct rendering and navigation. 
+Here, we randomly pick 60 deployable and visually functional web projects as our test set.
+
+Next, we identify reproducible test instances suitable for accessibility evaluation. 
+For each project, we select the homepage and several randomly sampled subpages (linked from the homepage), 
+and manually remove any inappropriate pages (such as plain text elements, project documentation, etc).
+Following [prior studies](https://github.com/seal-hub/GenA11y) that highlight the IBM Accessibility Checker as one of the most reliable open-source web accessibility checker tools, we use it to detect accessibility violations and verify consistent results across multiple runs. 
+Pages that trigger checker errors or yield inconsistent outputs are excluded. 
+After filtering, 60 projects with 145 stable and reproducible test pages remain for accessibility repair evaluation.
+
 ## 🚀Dataset Features
 
 ### Dataset Split