Demo Data from EDBT 2026 / reviewers in the wild / expert
Shubhi Jain
dblp:342/3583
· DBLP profile ↗
1ranked-venue papers
1as first author
1since 2021 · last 2025
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Human-computer interaction and pervasive computing
1 paper |
Accessibility and assistive technology · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Software testing · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Accessibility and assistive technology
screen reader accessibility |
0.9 | 1 | 2025 | Automated Detection of Web Application Navigation Barriers for Screen Reader Users · ASE 2025 |
Software testing › automated testing
automated accessibility testing |
0.9 | 1 | 2025 | Automated Detection of Web Application Navigation Barriers for Screen Reader Users · ASE 2025 |
Accessibility and assistive technology
web accessibility |
0.3 | 1 | 2025 | Automated Detection of Web Application Navigation Barriers for Screen Reader Users · ASE 2025 |
Methods — techniques the papers use, named apart from their topics
static rule-based analysis · 1.7screen reader simulation · 1.7
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Automated Detection of Web Application Navigation Barriers for Screen Reader UsersabstractAn estimated 43.3 million people worldwide live with blindness and rely on screen readers (SRs) to access the web. To support accessible development, software teams often rely on automated tools like WAVE and Lighthouse to detect accessibility issues. However, these tools primarily rely on static rule-based analysis and are largely limited to detecting labeling errors relevant to screen reader users. They fail to capture dynamic accessibility issues—specifically, whether user interface (UI) elements can be located and activated using a screen reader, which is essential for accessing core webpage functionality. To address this gap, we present A1 1yNavigator, an automated accessibility testing tool that simulates screen reader navigation to detect UI elements that cannot be either (1) located or (2) activated via the screen reader. A11yNavigator leverages NVDA, one of the most widely used screen readers, and supports three common navigation strategies: Tab, Arrow, and quick Navigation keys. We evaluate A1 1yNavigator across 26 real-world websites and demonstrate its effectiveness in uncovering issues missed by existing tools. Our results highlight its high precision and recall in detecting barriers that go beyond static analysis. Shubhi Jain, Syed Fatiul Huq, Ziyao He, Sam Malek |
ASE | 1 |