Overview
The New York State Workers’ Compensation Board partnered with New York State Information Technology Services (ITS) to convert the RFA-1LC from a paper/PDF-based process into a fully digital eForm.
This transition introduced significant accessibility risk. Without proper implementation, users relying on assistive technologies could be blocked from completing a required form, creating compliance concerns under WCAG 2.1 AA and ADA accessibility standards.
I served as the Lead Accessibility Tester and Accessibility Subject Matter Expert (SME) for my unit, responsible for validating accessibility compliance, documenting defects, and coordinating remediation efforts prior to release.
The project required extensive manual and automated accessibility testing across multiple user paths, assistive technologies, browsers, and authentication scenarios.
Challenge
The transition from paper/PDF workflows to a dynamic eForm introduced several accessibility and usability challenges:
- Accessibility requirements were not fully defined during initial development
- Multiple user roles and login types created inconsistent experiences
- Dynamic form behavior required accessible announcements and interaction handling
- Accessibility defects could block users from completing required workflows
- Testing needed to account for numerous permutations across tools, browsers, and user paths
- No established internal accessibility testing framework existed for the project
Goals
- Ensure the eForm met WCAG 2.1 AA accessibility standards
- Validate accessibility across all user roles and workflows
- Identify and document accessibility defects prior to launch
- Provide actionable remediation guidance to developers
- Establish repeatable accessibility testing processes
- Improve long-term internal accessibility testing capability
Approach
1. Accessibility Testing Strategy & Tool Coverage
Developed a structured accessibility testing process combining both manual and automated validation methods.
Testing simulated real-world experiences across assistive technologies to ensure issues were not only identified, but validated in the context of actual user interaction.
Accessibility Testing Tools
Screen Readers
- NVDA
- JAWS Inspect
Speech Input Testing
- Dragon NaturallySpeaking
Accessibility Evaluation
- WAVE
Manual Validation
- Keyboard-only navigation
- Focus order validation
- Tab flow testing
- Interaction testing
Cross-Browser & Device Testing
- Bitbar
This multi-tool testing approach ensured accessibility behavior remained consistent across environments and assistive technologies.
2. Testing Scope & Workflow Complexity
Accessibility testing was structured around JIRA user stories to ensure complete workflow coverage and traceability.
Testing Scope Included
- 8 core user stories
- 12 unique entry points
- 3 user login types with different workflows and permissions
This resulted in dozens of testing permutations across:
- Assistive technologies
- User roles
- Browsers
- Entry paths
- Devices and environments
Each scenario was tested across multiple accessibility tools to validate real-world usability.
3. Accessibility Leadership & Standards Implementation
The eForm was not initially developed with accessibility requirements fully integrated. As a result, I led the effort to define, interpret, and apply accessibility standards throughout testing and remediation.
Responsibilities Included
- Interpreting WCAG 2.1 AA requirements
- Translating accessibility standards into developer-ready fixes
- Identifying missing accessibility components
- Assigning severity and priority levels based on user impact
- Providing remediation guidance for ITS developers
- Acting as a bridge between accessibility standards and technical implementation
Accessibility Requirements Defined
- Programmatically associated form labels and inputs
- Logical focus order and keyboard navigation support
- Accessible error messaging and validation
- Screen reader announcements for dynamic content updates
- Appropriate use of ARIA attributes
- Semantic heading and landmark structure
- Color contrast and visual accessibility compliance
This ensured accessibility requirements were clearly defined, understood, and implemented consistently.
4. Defect Identification & Documentation
Identified and documented 30+ accessibility defects during initial testing.
Each defect included:
- User login and testing scenario
- Associated JIRA story
- Testing tool used
- Screenshots and/or video evidence
- Detailed issue description
- Mapped WCAG success criterion
- Clear remediation recommendation
All defects were tracked in a centralized dashboard to improve:
- Visibility
- Accountability
- Prioritization
- Remediation tracking
Common Issues Identified
- Missing or incorrect form labels
- Keyboard navigation and focus management issues
- Error messages not announced to assistive technologies
- Dynamic content updates not communicated properly
- Inconsistent heading structures
- Color contrast and visual clarity issues
5. Collaboration & Remediation Support
Worked closely with ITS developers and testers throughout remediation and retesting efforts.
Responsibilities Included
- Reviewing and clarifying accessibility defects
- Explaining WCAG requirements in practical implementation terms
- Recommending remediation approaches
- Validating fixes through iterative testing cycles
This collaborative process ensured accessibility solutions were implemented correctly and consistently.
6. Retesting & Quality Assurance
Following remediation, conducted full regression testing across:
- Accessibility tools
- User roles
- Entry points
- Browsers and environments
Validated resolved defects, identified remaining issues, and documented additional findings where necessary.
Team Training & Knowledge Transfer
Additionally:
- Trained staff on accessibility tools and testing methods
- Supported long-term internal accessibility QA capability
- Helped establish repeatable accessibility testing processes for future projects
Results
- Identified and helped resolve 30+ accessibility defects prior to launch
- Ensured alignment with WCAG 2.1 AA and NYS accessibility standards
- Prevented inaccessible functionality from reaching production
- Established a repeatable accessibility testing and documentation framework
- Improved visibility and prioritization through structured defect tracking
- Increased team accessibility knowledge and testing capacity
- Strengthened collaboration between business and ITS teams
My Role
Lead on accessibility testing, standards implementation, defect documentation, and remediation coordination.
Responsibilities included:
- Leading end-to-end accessibility validation across all workflows
- Serving as the primary accessibility SME for the project
- Defining accessibility requirements where none previously existed
- Conducting testing using screen readers, keyboard navigation, speech input, and automated tools
- Documenting defects and assigning severity based on WCAG impact
- Coordinating remediation efforts with ITS developers
- Training staff on accessibility testing processes and tools
- Supporting long-term accessibility governance and QA processes
Tools & Technologies
- NVDA
- JAWS Inspect
- Dragon NaturallySpeaking
- WAVE
- Keyboard-only accessibility testing
- Bitbar
- JIRA
- WCAG 2.1 AA standards
- ARIA implementation guidance
Key Takeaways
Accessibility must be intentionally integrated throughout development, not retrofitted after implementation.
This project demonstrates my ability to:
- Lead accessibility testing efforts within complex enterprise environments
- Translate WCAG standards into actionable technical requirements
- Coordinate remediation and QA efforts across technical and business teams
- Build structured accessibility testing and documentation processes
- Advocate for inclusive, user-centered digital experiences