Update Violations Nums
Browse files
README.md
CHANGED
|
@@ -25,28 +25,44 @@ 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 |

|
| 34 |
-
**Figure
|
| 35 |
|
| 36 |

|
| 37 |
-
**Figure
|
| 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
|
| 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
|
| 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?
|
|
|
|
| 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 |
+
### Violation Nums
|
| 29 |
+
|
| 30 |
+
|
| 31 |
+

|
| 32 |
+
**Figure 1**: Distribution of violations across 147 webpages.
|
| 33 |
+
|
| 34 |
+
Figure 1 illustrates the distribution of accessibility violations across the 147 webpages in our dataset.
|
| 35 |
+
The results reveal that web accessibility issues are inherently multi-fault in nature.
|
| 36 |
+
Specifically, every webpage in the dataset contains more than one accessibility violation, and **85.03% of webpages exhibit at least 10 violations**.
|
| 37 |
+
Even under more stringent thresholds, a substantial proportion of webpages remain highly problematic: 68.03% of webpages contain more than 20 violations,
|
| 38 |
+
and over half of the webpages (55.78%) still have more than 30 violations.
|
| 39 |
+
|
| 40 |
+
This trend persists for higher violation counts, with 31.29% of webpages containing more than 50 violations and 12.24% of webpages exceeding 100 violations.
|
| 41 |
+
Such a heavily skewed distribution indicates that accessibility defects are not isolated or sporadic, but instead co-occur extensively within individual webpages.
|
| 42 |
+
Consequently, repairing web accessibility in real-world systems typically requires addressing multiple, heterogeneous violations simultaneously,
|
| 43 |
+
rather than fixing a single defect in isolation.
|
| 44 |
+
|
| 45 |
|
| 46 |
### Violation Types
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |

|
| 51 |
+
**Figure 2**: 45 distinct web accessibility violation types in A11YBench.
|
| 52 |
|
| 53 |

|
| 54 |
+
**Figure 3**: Top-15 most frequent web accessibility violation types in A11YBench.
|
| 55 |
|
| 56 |
A11YBench covers 45 distinct accessibility violation types, corresponding to a broad subset of WCAG rules as identified by the IBM Accessibility Checker.
|
| 57 |
These violation types span multiple aspects of web accessibility, including missing or redundant alternative text, insufficient text contrast, improper ARIA usage,
|
| 58 |
non-unique landmark or navigation labels, and missing form or input labels.
|
| 59 |
|
| 60 |
+
As illustrated in Figure 2, the distribution of violation types exhibits a highly skewed, long-tailed pattern.
|
| 61 |
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
|
| 62 |
all detected violations, while many other types occur less frequently. This observation highlights the uneven prevalence of accessibility issues across different
|
| 63 |
WCAG rules in real-world web pages.
|
| 64 |
|
| 65 |
+
As illustrated in Figure 3, we report the top 15 most frequent violation types in the A11YBench. Detailed definitions, detection logic, and corresponding WCAG mappings for each violation type can be found in the
|
|
|
|
| 66 |
[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.
|
| 67 |
|
| 68 |
## 📃How to use it?
|