B
Web Accessibility Auto-Scroll Auditor
4.05
Derivation Chain
Step 1
Recognition of auto-scroll issues in web accessibility
→
Step 2
Web accessibility compliance tools
→
Step 3
Accessibility violation detection and fix guide specifically for auto-scroll and moving content
Problem
After the expansion of mandatory web accessibility requirements under the Anti-Discrimination Against and Remedies for Persons with Disabilities Act in 2025, SMEs and shopping malls must obtain web accessibility certification. However, moving content such as auto-scrolling banners, auto-playing videos, and infinite scroll feeds accounts for about 25% of all accessibility errors, violating WCAG 2.2 Level AA. Existing accessibility testing tools (WAVE, Lighthouse) cannot accurately detect these dynamic content violations, and professional consulting costs 2 to 5 million KRW (approx. $1,500 to $3,750) per case.
Solution
When a URL is entered, the page is rendered using Puppeteer/Playwright to automatically detect moving content such as auto-scroll, auto-play, flashing, and infinite scroll, and report WCAG 2.2 violations. For each violation, it provides framework-specific (React/Vue/WordPress) code fix examples and priority scores, and tracks certification readiness through re-testing after fixes.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (77%)
Data Availability
22.5/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (61/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Backend [medium]
Frontend [low]
Infrastructure [low]