Wave navigation issue with screen reader

#1

hi, I’m having the following accessibility issues with blind users and it could affect employment:

  1. when using wave on ios with the voiceover screen reader, all audio is sent to the ear speaker when wave is opened.
    this will prevent them from hearing the screen reader.
    1.1. one-touch typing is not working with the wave dial pad
  2. the wave web/windows app has no text label for muting, answering and voice note play button
    2.1. when a contact is open there is no text labels for the video call, audio call and chat
#2

Consider purchasing Counterpath’s Bria for sight impaired users. They have a dedicated team just delivering VoIP Softphone as that is their major product line.

#3

thanks the only small down side is when using bria or acrobits with sip configuration wave users can’t send messages to the sip soft-phones
I found that acrobits groundwire, 3CXPhone and Linphone have the least accessible issues when navigation with the screen reader is used.
the cisco 8800 has a built in screen reader for hardware phone.

#4

What if they log into the ucm as the user , do they then have capability to use chat ? I dont have a UCM63xx

#5

the ucm6300 has a wave web
so a work around could be to let them use the wave web for chatting and a sip client like microsip(95% accessible) with the screen reader for audio calls.
but this is only best when using the computer.
also since the wave web is missing many text labels for the elements it will slow them down and as the saying goes time is money lol.
another down side is during meetings in the wave some of the functions can only be activated using the mouse example removing contacts, muting/unmuting.
the audio dialog to select a sound device when a usb headset is used with wave is also a challenge because it has to use the mouse to dismiss it.

#6

Dear users,

Thank you for all your feedback! This is a known feature request and our Wave development team will investigate and consider this improvement in the future release. Thanks for your testing!

Thank you!

#7

consider adding the aria-label attribute to the elements.
it will give a text description to the screen reader user
remember blind users screen reader will not read the mouse hover tool tip.
remember they can navigate best with keyboard

#8

Dear user,

Thank you for your feedback! I have passed your suggestions to our Wave development team for evaluation. We have received such a feature request from several different customers and we will consider it in the future release. Thanks for your testing!

Thank you!

#9
  1. When scheduling a meeting via the web interface
    (Multimedia Meeting>Schedule Meeting)
    The screen reader user (blind/visual impaired) can not access the calendar to set the date and time
    I propose that the data entry field be made editable so manual entry of date and time can be possible without using the calendar.
#10

Dear user,

Thank you for your feedback! This feature request has been reported to our Wave development team for evaluation today. Thanks for your testing!

Thank you!

#11

can audio captchas be added?
currently if a password is entered wrong only a visual captcha is given.

#12

Dear user,

Thank you for your feedback! This feature request will be passed to our development team for evaluation. Thanks for your testing!

Thank you!

#13

dear Tech team
we’re still waiting accessibility improving for wave.
it really help blind people to work in call centers.

dear Curt: glad to communicate with you directly, i sent you a message, waiting your reply if possible.
also will be glad if i could contact all blind users who’re using wave or even try to use it, msg me if you like.

thanks

#14

Dear user,

Thank you for your feedback! Our Wave development team will consider this feature request and our development team will do more research on it before implementing it in the Wave Desktop application. I have already shared all your suggestions with them for evaluation. Thanks for your testing!

Thank you!

#15

I’m working on adding hot-spots to the screen as well to allow the screen reader to use a macro key to perform some function in wave.
yes sir, one work around is to use a sip soft phone which is more accessible than wave for blind workers.
but wave users can’t send chats to the third-party soft phone application and you can’t receive chats in meetings.
I’ve already reported the many issues and possible solution that may/may not be resolved relating to navigation with screen readers to the grandstream support.
you can also inspect the elements and use the screen reader utility to kind of add labels to the elements as a temp work around.

#16

Dear user,

Thank you for sharing these suggestions and feedback with us! This feature is under considration by our Wave Desktop development team now. I will share the conclusion with you once I receive any updates from our development team. Thanks a lot for your patient!

Thank you!

#17
  1. add the missing keyboard shortcuts(wave desktop):
    raise/lower hand and leave meeting.
  2. also add keyboard shortcuts for wave web.
#18

Dear user,

Thank you for your feedback! I have received your feature requests on the feedback platform today and I have shared them with our Wave development. We will consider your feature reuqests in the future release. Thanks for your testing!

Thank you!

#19

In order to improve the wave experience for the screen reader users,
I suggest the
role=“alert”
be added to the elements that give important real time notification.
This include but is not limited to:
mute/un-mute status, hand raise/lowered
without the role=“alert” they will have to manually locate the notification and most times it will go away before being located.

#20

Dear user,

Thank you for your feedback! This feature request has been shared with our Wave development team for evaluation in the future release. Thanks for your testing!

Thank you!