Hey all,
I'm a blind system admin using a screenreader which allows me to interface with my computer, phone, etc.
Recently I deployed 3CX in a test environment to see how well this would work as a PBX system for us, and was happy to see that the setup on a Debian server was really straightforward.
Also, I found that the web interface works relatively well with my screenreader, however a major show stopper right now is that any toggles that can be used to turn a feature / function on or off are not being announced as such by the screenreader, and the current state of the toggle is also not being announced.
This is especially problematic in areas such as the Anti Hacking page, where several important security features can be turned on or off. With the current situation, there's no way for me to figure out whether a specific feature, such as the distributed IP blacklist or PCI-compliant TLS is enabled which is quite concerning.
With this in mind, I kindly would like to ask the 3CX development team to please consider fixing this in an update, as sadly as far as I can tell this makes the software pretty much unusable for users relying on screenreader software.
Basic accessibility of such products will soon become a legal requirement in the EU for businesses wanting to deploy such products, and it would be wonderful if 3CX could gain a headstart on this front.
There are other 3CX-related tools which don't seem to be all that accessible currently such as the 3CX iOS app as can be seen here: https://www.3cx.com/community/tags/accessibility/.
However, in most cases good workarounds do exist, such as using another, more accessible SIP client app.
As far as I can tell such a workaround does not exist for my particular issue, however, and so it would be really great to have this addressed.
Thanks!
Robin
I'm a blind system admin using a screenreader which allows me to interface with my computer, phone, etc.
Recently I deployed 3CX in a test environment to see how well this would work as a PBX system for us, and was happy to see that the setup on a Debian server was really straightforward.
Also, I found that the web interface works relatively well with my screenreader, however a major show stopper right now is that any toggles that can be used to turn a feature / function on or off are not being announced as such by the screenreader, and the current state of the toggle is also not being announced.
This is especially problematic in areas such as the Anti Hacking page, where several important security features can be turned on or off. With the current situation, there's no way for me to figure out whether a specific feature, such as the distributed IP blacklist or PCI-compliant TLS is enabled which is quite concerning.
With this in mind, I kindly would like to ask the 3CX development team to please consider fixing this in an update, as sadly as far as I can tell this makes the software pretty much unusable for users relying on screenreader software.
Basic accessibility of such products will soon become a legal requirement in the EU for businesses wanting to deploy such products, and it would be wonderful if 3CX could gain a headstart on this front.
There are other 3CX-related tools which don't seem to be all that accessible currently such as the 3CX iOS app as can be seen here: https://www.3cx.com/community/tags/accessibility/.
However, in most cases good workarounds do exist, such as using another, more accessible SIP client app.
As far as I can tell such a workaround does not exist for my particular issue, however, and so it would be really great to have this addressed.
Thanks!
Robin
