Sarcouncil Journal of Engineering and Computer Sciences

Abstract: Static accessibility linters identify violations in source code but fail to detect critical runtime issues. These include focus trap behaviors, misconfigured ARIA live regions, and theme-dependent contrast failures that only emerge during application execution. This article presents a comprehensive testing strategy extending beyond traditional static analysis. The framework incorporates automated screen reader sessions, dynamic contrast analyzers for multiple theme variations, and specialized pixel-diff tools for right-to-left layouts directly into CI/CD workflows. A pilot implementation across six micro-frontend applications identified 37 critical violations previously undetected by static tools, with an average remediation time of 2.3 days per issue. The article provides actionable resources including pipeline configuration scripts, build-blocking thresholds, and stakeholder reporting templates. By treating accessibility as a first-class citizen in automated testing, teams can ensure WCAG compliance while maintaining rapid deployment cycles.