public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Roku accessibility (was Re: Youtube TV Site?)
Date: Thu, 22 Jun 2017 19:28:21 -0400	[thread overview]
Message-ID: <07dd71b8-93f8-5a50-d141-6e60c2f02061@gmail.com> (raw)
In-Reply-To: <8d56c90d-18a7-15ae-fc58-66503327f4be@gmail.com>

I'm not currently aware of any community, forum, e-mail list, Facebook 
group, etc. where blind and visually impaired users can come together to 
discuss Roku device accessibility. I'll look for such a beast further, 
and if I find it, I'll report back on this thread. If not, I'll start 
one, as too many people are under the misconception that Roku devices 
are not accessible at all, or that Roku accessibility is abysmal at 
best, when in fact the voice is my only real complaint. Well, that and 
the 6 apps that I found that didn't speak or didn't speak well. Until I 
have something conclusive or make a list or similar available, I did 
find this.
https://support.roku.com/article/223737947-channel-contact-list
It doesn't have everything, nor does it cover all the channels I've 
mentioned previously that don't have speech, but it's a good start. I 
found contact pages for both Crackle and Pandora on this page, and have 
sent both of them messages regarding the lack of speech in their channel 
apps, including links to
https://support.roku.com/article/231584647-how-do-i-use-audio-guide-
the introduction to the audio guide and how it works, and to
https://sdkdocs.roku.com/display/sdkdoc/roAudioGuide
Audio Guide SDK documentation for channel developers who need the Audio 
Guide to speak custom messages, either because they're using custom 
controls that are unsupported or because they need the Audio Guide to 
speak additional information that is not supported using the default 
functionality of the Audio Guide in relation to the control used. 
Hopefully this will help somewhat.
~Kyle

  reply	other threads:[~ UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Youtube TV Site? Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
           ` Linux for blind general discussion [this message]
             ` Roku accessibility (was Re: Youtube TV Site?) Linux for blind general discussion
               ` Linux for blind general discussion
                 ` Linux for blind general discussion
                   ` Linux for blind general discussion
                     ` Linux for blind general discussion
                       ` Linux for blind general discussion
                         ` Linux for blind general discussion
                 ` Linux for blind general discussion
                   ` Linux for blind general discussion
                   ` Linux for blind general discussion
                     ` Linux for blind general discussion
   ` Youtube TV Site? Linux for blind general discussion

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07dd71b8-93f8-5a50-d141-6e60c2f02061@gmail.com \
    --to=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).