Skip Menu |

This queue is for tickets about the Tcl-pTk CPAN distribution.

Report information
The Basics
Id: 125987
Status: stalled
Priority: 0/
Queue: Tcl-pTk

People
Owner: Nobody in particular
Requestors: kellyobrein77 [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: [macOS] Widgets do not accept speech-to-text input
Date: Thu, 2 Aug 2018 16:37:10 +0100
To: bug-Tcl-pTk [...] rt.cpan.org
From: "Kelly O'brein" <kellyobrein77 [...] gmail.com>
On my macOS (HighSierra), tcl 8.5, it seems that no widget (Entry as well as Text) is able to accept the standard speech-to-text input it comes along with macOS. As STT is quite a common feature nowadays, it would be great if Tcl::pTk (or Tcl: I am not aware which is responsible for this incompatibility) would accept it too.
On Thu Aug 02 10:37:22 2018, kellyobrein77@gmail.com wrote:
Show quoted text
> On my macOS (HighSierra), tcl 8.5, it seems that no widget (Entry as well
> as Text) is able to accept the standard speech-to-text input it comes along
> with macOS. As STT is quite a common feature nowadays, it would be great
> if Tcl::pTk (or Tcl: I am not aware which is responsible for this
> incompatibility) would accept it too.

Thanks for opening this. For reference, I'm leaving a link to your post on Stack Overflow (along with my answer containing some initial investigation): 
https://stackoverflow.com/q/50659910/4896937
For reference, this affects Tcl::Tk as well: RT #127873
I've since observed difficulty using dictation even in pure Tcl/Tk examples, so I've opened a ticket: https://core.tcl.tk/tk/tktview/fdbdcc8c3c0d49070107e8160b46d683650baa69
Just an update: I had received a reply from one of the Tk Aqua developers indicating that Tk currently makes no effort to support accessibility features:

Tk has no support for accessibility API's on any platform. It would be a great, if complicated, project for someone to take on.

I responded that, although I am not familiar with the Cocoa API, I am under the impression that supporting dictation should not involve any special accessibility API, and that this was something Cocoa apps using the standard widgets are provided "for free" so that dictation is available to users of existing programs without developer intervention.