CRM Upgrade and a Screen Reader User in the Call Center
A financial services company is migrating 240 call-center agents from a desktop CRM to a browser-based system in eight weeks. One agent, a 34-year-old customer service representative who is blind, uses JAWS 2024 with a Windows laptop and a refreshable braille display. The new CRM’s vendor claims “WCAG 2.1 AA compliance,” but the pilot shows unlabeled icon buttons, a custom date picker that traps focus, and live-chat alerts that are not announced. The vendor says it will fix issues in a future release. The company’s IT team proposes giving the agent a 22-inch monitor and a screen magnifier instead, because “the screen reader is causing the compatibility problem.” The agent’s productivity standard is 18 calls per shift; the team average is 21. The accommodation budget is $3,000, and the agent already has JAWS and a braille display. Training on the new CRM starts in four weeks.
1. Identify the assistive technology and adaptive strategy issues in this scenario, and evaluate IT’s proposed magnifier solution.
Read the worked answer
Model answer
The assistive technology is the JAWS screen reader plus the refreshable braille display; the adaptive strategy is the agent’s way of using keyboard commands, braille, and speech to complete CRM tasks. The pilot problems-unlabeled icon buttons, a focus-trapping date picker, and unannounced live-chat alerts-are application accessibility failures, not screen-reader failures. A screen reader can only announce what the browser and app expose; if a button has no accessible name or focus is trapped, JAWS cannot compensate.
IT’s 22-inch monitor and magnifier proposal is a category error. Magnification is a low-vision strategy; it does not make a blind user’s workflow accessible. Offering it could be appropriate as an option for an employee with low vision, but here it avoids the real issue and may signal that the company is not taking the accommodation request seriously. The company should do a functional assessment with the agent, test the CRM with JAWS and keyboard-only use, and document the barriers. The $3,000 budget is better spent on accessibility testing, JAWS updates if needed, braille display compatibility, and training-not on a magnifier that does not address the barrier. The agent should be involved in selecting any solution.
2. What should the company require from the vendor, and what interim steps should it take before training begins?
Read the worked answer
Model answer
The company should require the vendor to provide a current Accessibility Conformance Report (ACR/VPAT) for the CRM, not a marketing claim. The contract or purchase order should include accessibility acceptance criteria: WCAG 2.1 AA conformance for the agent-facing workflows, keyboard operability, accessible names, focus management, status announcements, and compatibility with JAWS/NVDA. Require the vendor to fix the three pilot blockers before go-live and to provide a dated remediation plan for remaining defects. If the vendor cannot meet the criteria, the company should consider a different product or a contract remedy.
Interim steps before training:
- Keep the agent on the legacy CRM, or a documented equivalent workflow, until the new CRM passes critical tests.
- Run a focused test with the agent on the highest-volume tasks: lookup, notes, transfer, and chat alerts.
- Make training materials accessible and offer one-to-one training rather than a crowded group session.
- Assign an accommodation coordinator and a feedback channel.
- Do not force the agent to use a workaround that lowers quality or makes the job harder.
The goal is equal access to the essential functions, not a good-faith gesture.
3. How should the company measure whether the accommodation is effective without using the team average as the only benchmark?
Read the worked answer
Model answer
Effectiveness should be judged against the agent’s essential job functions and her own baseline, not against a team average that may reflect an inaccessible tool. Useful measures include: call handling and task completion with the new CRM, error rate and rework, quality scores, time to complete key workflows, attendance and fatigue, and the agent’s own rating of usability and accommodation fit. The company should compare pre- and post-migration performance and check whether any gap is caused by the tool rather than by the employee.
The team average of 21 calls per shift is not a fair benchmark if the new CRM creates barriers; using it alone could turn a tool defect into a performance problem. A better process is an individualized accommodation review with the agent, the manager, IT, and HR. Set interim targets that reflect the accessible workflow, review after four to six weeks, and adjust. If the agent’s productivity is lower because of the CRM, the remedy is remediation or an alternative workflow, not discipline. The company should also track whether the vendor fixes the defects on schedule. The accommodation is effective when the agent can perform the essential functions with dignity and comparable quality-not when she matches an arbitrary average.