Customer story · Accessibility
An accessibility firm's Call button has to pass its own audit
EnableUser tests the websites and apps of Indian brokers, fund managers and advisers against WCAG, the SEBI accessibility requirements and IS 17802. Anything on its own site, including a call widget, is looked at by the people who write those audit reports.
Published · Written by the CallCeptor team
Their buyers are our buyers
EnableUser's home page lists more than a hundred Indian financial firms it works with, from stock brokers and portfolio managers to AIFs and rating agencies. Those are the firms CallCeptor is built for. So EnableUser's visitors are exactly the people who will one day click a Call button on a broker's website and find out whether it works for them.
Its contact page opens with “whether you are addressing an immediate audit failure or planning a long-term compliance strategy”. The first of those is a phone call, not a form.
“People who visit our site often want to talk before they decide anything. CallCeptor gave them a way to do that straight from the page, without hunting for a phone number or waiting for an email reply. It was simple to set up, and it fits the way we already work.”
Four reasons to call, four desks
EnableUser's contact form already sorts people into four subjects. The Call button uses the same split, so a caller reaches the right team without a switchboard.
| Subject on their form | Who is calling | Desk | How it rings |
|---|---|---|---|
| Audit Request | A firm that needs a WCAG or SEBI accessibility audit, sometimes because it has just failed one. | Audits | The caller usually has a deadline. Ringing every free auditor at once means the first person available answers. |
| Platform Demo | An engineering or product lead looking at the audit engine, CI checks or the Figma and IDE plugins. | Platform | A technical caller wants someone who knows the product, so the call goes to the agent tagged for the platform first. |
| Partnership | Agencies, consultancies and resellers. | Partnerships | Low volume, high value. A missed call here becomes a callback request with the caller's number. |
| General Inquiry | Everyone else, including existing clients who don't know who to ask. | Front desk | The visitor can still pick a specific desk from the call panel if they know what they need. |
Desks, ring order and callbacks are standard CallCeptor settings. See how to route website calls by page.
The bar
What the Call button does for keyboard and screen-reader users
A firm that sells accessibility audits can't have a widget on its site that a screen-reader user can't operate. This is what CallCeptor's button and call panel do today, taken from the widget's code.
A real button with a spoken name
The Call button is a <button> with a text label that screen readers read out ("Call us" unless the site changes it).
Visible keyboard focus
Tabbing to the button draws a focus ring in the site's brand colour.
The panel says what it is
The call panel is marked as a dialog and carries the site's own title.
Call status is announced
Ringing, connected, reconnecting and ended are written to a live region, so a screen reader speaks each change.
Choices and errors are labelled
Picking a desk is a radio group. A missing name or number is flagged on the field itself, with the error tied to it.
Mute says whether it's on
The mute control reports its pressed state, not only a changed icon.
Not done yet
The widget has not had an independent WCAG 2.2 audit. Until it has, we don't claim conformance to any level. When the audit is done, the report will be linked from this page, issues and all.