Current Location ：
Accessibility in Business Phone Systems: Designing for Everyone
Accessibility in voice systems is rarely a deliberate exclusion. It is usually a by-product of choices made for other reasons: a handset chosen for cost, an automated menu chosen for efficiency, a visual interface chosen because it looked modern. Each choice is reasonable on its own, and together they can make it harder for some staff and callers to use a system that everyone else takes for granted. The good news is that most accessibility problems in voice are cheap to fix at design time and expensive to fix afterwards, which makes this a planning topic rather than a remediation topic. This article covers device and interface considerations, what to watch for in automation, and how to keep a usable route to a person.
Think About Two Different Populations
There are staff who use the system every day and callers who use it once. They need different things. Staff need devices and interfaces they can operate comfortably for hours. Callers need a path through the system that does not assume abilities the caller may not have. Designing for one group and assuming it covers the other is how systems end up accessible internally and hostile externally, or the reverse.
Device and Interface Considerations
| Consideration | Design response | What it addresses |
|---|---|---|
| Audio output | Support for headsets, hearing-aid compatible handsets, and adjustable volume | Staff and callers with hearing loss or in noisy environments |
| Visual signalling | Clear, high-contrast call state indication that does not rely on colour alone | Callers and staff with colour vision differences |
| Input method | Options that do not require precise touch on small targets | Staff with motor or dexterity limitations |
| Amplification | Handsets and devices with adjustable receive gain | Age-related and situational hearing differences |
| Notification | Both audible and visible alerting where practical | Environments where one channel is unusable |
Where Automation Creates Barriers
Automated menus are the most common source of accessibility problems in the voice channel, because they add requirements the telephone never used to have: understand a spoken list, respond within a timeout, and do it by voice. Each of those is a barrier for somebody. The mitigation is not to abandon automation; it is to keep the alternatives visible and usable.
- Keep a clearly signposted route to a person, and do not remove it to improve containment numbers
- Allow responses by keypad as well as by speech, without making the keypad option harder to reach
- Allow generous response time before a menu advances or repeats
- Keep menus short and the language plain, without internal jargon
- Repeat information on request and confirm what the system understood before acting on it
- Test the menu by phone from outside the organisation, in a noisy environment, with someone unfamiliar with it
Involve the People Affected
The most reliable way to find accessibility problems is to ask the people who experience them. A short review with staff who use assistive technology, or with representatives of the populations you serve, will find more in an hour than a specification review will find in a week. It also changes the conversation from compliance to usability, which tends to produce better designs and fewer arguments.
Documentation and Procurement
Two practical habits make accessibility durable. First, include accessibility requirements in procurement so device choices are made against a stated standard rather than rediscovered later. Second, document the accessibility-relevant configuration of the system alongside the rest of the design, so a future change does not silently remove an accommodation that someone depends on.
Redstone Approach
Redstone supports accessible voice design on the REX IP-PBX platform and across the NRP handset range. Our teams can review handset selection against accessibility requirements, design IVR structure that keeps usable routes to a person, and document accessibility-relevant configuration so it survives later changes. Specific device capabilities and configuration options are confirmed in writing against the products installed and the standards that apply to your organisation and region.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
