Focus: Understanding user needs, defining clear workflows, establishing accessible requirements, and designing intuitive user experiences from the earliest stages of a project.
Responsibilities
- Integrate accessibility into feature requirements and acceptance criteria.
- Specify accessibility expectations for forms, navigation, content structure, and components.
- Design and develop BI dashboards and reports to meet WCAG 2.1 A/AA standards.
- Account for diverse user needs, including those using assistive technologies.
- Document functional and non‑functional accessibility requirements (e.g., keyboard operation).
- Coordinate with designers, developers, and QA teams to make sure accessibility requirements are testable.
- Verify that vendors and third-party tools meet WCAG 2.1 A/AA standards.
Support project teams by clarifying which roles are responsible for which WCAG criteria.

Relevant WCAG 2.1 new success criteria
User Experience (UX) & Business Analysis (BA) roles shape the structure, interaction patterns, and requirements for every feature. Because of this, all WCAG 2.1 criteria are relevant to these roles (including all WCAG 2.1 new success criteria). UX/BA roles make sure accessibility requirements appear early in planning and help teams understand which criteria apply to their work and how to implement them correctly in designs and workflows.
Testing tools for early validation
All roles are responsible for quality assurance and UX/BA roles often validate accessible design at the start to prevent rework. Many tools are available to test your solution/work including color contrast checkers, screen reader software, and sometimes built-in accessibility verification.
Note: While automated accessibility testing tools are a great resource, they do not guarantee WCAG 2.1 compliance. Manual testing is still required to ensure content meets WCAG 2.1 A/AA standards.
Requirements for contrast ratios
- Normal text: 4:5:1
- Large text (minimum of 14pt bold or 18pt): 3:1
- Non-text elements (graphics, user interface components): 3:1
Tools
Screen readers allow blind and visually impaired users to navigate digital content using speech output. Testing with a screen reader helps teams understand how content is announced, how navigation flows, and whether interactive elements are labeled correctly.
Tools
- NVDA (Non-Visual Desktop Access – Free screen reader for Windows that is widely used in accessibility testing. To get this downloaded, please submit a general service ticket for the service desk to assist.
Keyboard-only testing helps ensure that all interactive elements—such as buttons, menus, forms, and multimedia—can be operated without a mouse.
Tools
- WebAIM Keyboard Accessibility Guide – Outlines essential keyboard commands, testing steps, and common problem areas.
