LLM4APR commited on
Commit
e63120f
·
verified ·
1 Parent(s): fa9ff9d

update dataset metric

Browse files
Files changed (1) hide show
  1. README.md +29 -3
README.md CHANGED
@@ -10,18 +10,44 @@ tags:
10
  **A Benchmark for Web Accessibility Repair**
11
 
12
  ## 😃Dataset Summary
13
- A11YBench consists of 60 real-world web projects, encompassing 145 web pages and 8,874 accessibility violations detected by the IBM Accessibility Checker (4.0.6).
14
  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.
15
  This scale ensures that A11YBench reflects the structural and technical diversity of modern web ecosystems.
16
 
17
  ## 🚀Dataset Features
18
 
 
 
19
  Real-world accessibility violations extracted from popular open-source web repositories.
20
  Multi-domain coverage including UI libraries, developer tools, cloud platforms, documentation sites, and more.
21
 
22
  Two configurations:
23
- A11YBench-Lite – small, quick-to-run subset (10 repos).
24
- A11YBench-Full – complete benchmark with all collected repositories.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
25
 
26
  ## 📃How to use it?
27
 
 
10
  **A Benchmark for Web Accessibility Repair**
11
 
12
  ## 😃Dataset Summary
13
+ A11YBench consists of 60 real-world web projects, encompassing 147 web pages and 8,886 accessibility violations detected by the [IBM Accessibility Checker](https://github.com/IBMa/equal-access/tree/4.0.9) using [Check Rule 2025.09.03](https://github.com/IBMa/equal-access/tree/main-4.x/rule-server/src/static/archives/2025.09.03).
14
  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.
15
  This scale ensures that A11YBench reflects the structural and technical diversity of modern web ecosystems.
16
 
17
  ## 🚀Dataset Features
18
 
19
+ ### Dataset Split
20
+
21
  Real-world accessibility violations extracted from popular open-source web repositories.
22
  Multi-domain coverage including UI libraries, developer tools, cloud platforms, documentation sites, and more.
23
 
24
  Two configurations:
25
+ A11YBench-Lite (Repo No. 1-10) – small, quick-to-run subset (10 repos).
26
+ A11YBench-Full (Repo No. 1-60) – complete benchmark with all collected repositories.
27
+
28
+
29
+ ### Violation Types
30
+
31
+
32
+
33
+ ![All 45 violation types](https://cdn-uploads.huggingface.co/production/uploads/64648f5802f8858f2128d179/1Xs_P1h8O8LRRlDVNoCwb.png)
34
+ **Figure 1**: 45 distinct web accessibility violation types in A11YBench.
35
+
36
+ ![Top-15 violation types](https://cdn-uploads.huggingface.co/production/uploads/64648f5802f8858f2128d179/73ud4A-KRsHcmT5QsvGRL.png)
37
+ **Figure 2**: Top-15 most frequent web accessibility violation types in A11YBench.
38
+
39
+ A11YBench covers 45 distinct accessibility violation types, corresponding to a broad subset of WCAG rules as identified by the IBM Accessibility Checker.
40
+ These violation types span multiple aspects of web accessibility, including missing or redundant alternative text, insufficient text contrast, improper ARIA usage,
41
+ non-unique landmark or navigation labels, and missing form or input labels.
42
+
43
+ As illustrated in Figure 1, the distribution of violation types exhibits a highly skewed, long-tailed pattern.
44
+ A small number of violation types—such as aria_content_in_landmark, svg_graphics_labelled, and text_contrast_sufficient—account for a substantial proportion of
45
+ all detected violations, while many other types occur less frequently. This observation highlights the uneven prevalence of accessibility issues across different
46
+ WCAG rules in real-world web pages.
47
+
48
+ As illustrated in Figure 2, we report the top 15 most frequent violation types in the A11YBench, while the complete distribution of all 45 violation types is
49
+ provided in the supplementary material. Detailed definitions, detection logic, and corresponding WCAG mappings for each violation type can be found in the
50
+ [IBM Accessibility Checker rule set](https://github.com/IBMa/equal-access/tree/main-4.x/rule-server), which we adopt as the authoritative reference for violation semantics.
51
 
52
  ## 📃How to use it?
53