From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id v5N05RUo017961 for ; Thu, 22 Jun 2017 20:05:27 -0400 Received: by smtp.corp.redhat.com (Postfix) id 1C28D1964E; Fri, 23 Jun 2017 00:05:27 +0000 (UTC) Received: from mx1.redhat.com (ext-mx07.extmail.prod.ext.phx2.redhat.com [10.5.110.31]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 15C2D63F7C for ; Fri, 23 Jun 2017 00:05:25 +0000 (UTC) Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com [209.85.220.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 827A7C04D2B7 for ; Fri, 23 Jun 2017 00:05:24 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 827A7C04D2B7 Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=kyle4jesus@gmail.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 827A7C04D2B7 Authentication-Results: mx1.redhat.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Q6gBXDWM" Received: by mail-qk0-f174.google.com with SMTP id r62so24887974qkf.0 for ; Thu, 22 Jun 2017 17:05:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=MvyL3hNm1rQu8BbPjnT6qiJOchQHmSBdd4ncdbsZ/Oo=; b=Q6gBXDWMYISCPu/x2xFoWj02GlhbSQIfuXA/XsT+7rpSAspfO3+Yc0XgRqZrVwVuII VsC8LSu2rzgesDEzqCM3O+ajzE0F45ZGZo6id3Ox8pdAqZtd0XAyxW9h6OApvbbY1tx0 i7ehnK0RgpTTQlnRVkLBGnHgj6S/RgraDcFdFiGo1fXJX9aQTmUAdsg0u44S4OPQVIZU UNs3GiAwCqfBRSkbvTe05K8bHWGb6k1IeLjN/VC1SWktdqtSYedA3Vh/Sz35V2wH1r4w LL+/Ge1HgGlJL9Lq/pxaDWYlyaGBI6D8hMYsIRyM4U05YPkmV8INe8xpu6/ybpMpOyZP 6Etw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=MvyL3hNm1rQu8BbPjnT6qiJOchQHmSBdd4ncdbsZ/Oo=; b=iiGECcJLx8XHcpsg/s5xeh6p3sLHHBOBFIVCnSrHcevZjh8G1w8BJEQQEL0EqL4Hdz mAYSHXI+wRl/E0pRnKD1qHWm3QPxTgn8NeIOV4O0bw2yROGM4hIzgqwjrBBmNavEFHth y65Kh4Q4l5yGiXnw6cxmdrJE72Wr/5F8dlecVFSE3ARA9Og7DV5tUp1SQPP/+xo5Mrp8 2LaKmXMtc8DIkJac/Xie7ObzIgnV4yrXBpuYWo7SlimfSc46Tjh0y4k0fXx7Hid8yY0f 8wekWI8qAHEph0ZZyUtpeewL7vEaMq6ymw0QSS8m/29+3JV4MQBOcgvtPCv8Y+sBY3cj qZmA== X-Gm-Message-State: AKS2vOyMczvrvQCkc73ONDE8JdUJOu/Cc/Lh/7n5jq7B4oSJQxo/9EXL /WPGeLu4+p7Hv8gZ X-Received: by 10.55.188.71 with SMTP id m68mr6272174qkf.169.1498176323489; Thu, 22 Jun 2017 17:05:23 -0700 (PDT) Received: from ?IPv6:2606:a000:111a:8069::89c? ([2606:a000:111a:8069::89c]) by smtp.googlemail.com with ESMTPSA id q90sm2133646qki.11.2017.06.22.17.05.21 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Jun 2017 17:05:22 -0700 (PDT) Subject: Re: Roku accessibility (was Re: Youtube TV Site?) To: blinux-list@redhat.com References: <636719be-33d7-280d-5265-0d11edc8d1e8@gmail.com> <6663c492-e248-ae6f-ad4e-182ea2b7c4c8@gmail.com> <8d56c90d-18a7-15ae-fc58-66503327f4be@gmail.com> <07dd71b8-93f8-5a50-d141-6e60c2f02061@gmail.com> Message-ID: <5aa3a21c-bed3-594f-a239-bbc800cb74d6@gmail.com> Date: Thu, 22 Jun 2017 20:05:20 -0400 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Fri, 23 Jun 2017 00:05:24 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Fri, 23 Jun 2017 00:05:24 +0000 (UTC) for IP:'209.85.220.174' DOMAIN:'mail-qk0-f174.google.com' HELO:'mail-qk0-f174.google.com' FROM:'kyle4jesus@gmail.com' RCPT:'' X-RedHat-Spam-Score: 0.27 (BAYES_50, DCC_REPUT_00_12, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_PASS) 209.85.220.174 mail-qk0-f174.google.com 209.85.220.174 mail-qk0-f174.google.com X-Scanned-By: MIMEDefang 2.78 on 10.5.110.31 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-loop: blinux-list@redhat.com From: Linux for blind general discussion X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: blinux-list@redhat.com List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 00:05:27 -0000 Well, I should note that text based browsers are usually no longer considered when trying to develop accessible websites, so your mileage will vary greatly when using a text-based browser, even when a site can be accessed with no trouble using Firefox, Seamonkey or Chromium. For example, whereas you had problems accessing the links I posted earlier, I had no trouble at all accessing them in Firefox. I would copy and paste the information from the channel contact list I posted, but this relies on having a link to the contact or support page for each channel listed, and once you get there, even if I was to be able to copy and paste each link, the contact or support page will likely be unfriendly to text only browsers, as they don't adhere to current HTML standards. Sorry for the trouble, it's just the way even the w3c handles things now as far as I can tell. After doing a rather thorough search for Roku accessibility groups or blind Roku users, I find only a single post on a blind tech list that refers to what would appear to be an early model Streaming Stick available at Walmart last year. So I'll likely start an e-mail list or similar. Thoughts are welcome, i.e. should this be specific to Roku devices for the most part, or should it cover all accessible TV devices including the latest cable box offerings? In answering this question, it is important to note that the Chromecast and Android TV devices are on topic on the eyes-free Android list, and the Apple TV is on topic on AppleVis. About the only thing I can think of at this point that isn't covered elsewhere is the Amazon Fire TV line, including the Fire TV Stick, the Fire TV box and the up and coming Fire TV with Alexa, the one that's a complete TV that is said to be released in the coming months, not the device that connects to an existing TV. Of course there are also the LG and Samsung TV's that have accessibility built into their high end models, and they are also not covered anywhere as far as I know, although they have varying levels of accessibility and different methods of accessing screen reader/audible guide features. In any case, if a general accessible TV list is most desirable, then a general accessible TV list it will be, although that will quickly go all over the map, so may be harder to manage, since too many devices with too much variation in features and methods of access could become problematic. The next question would be the format. Is it to be an e-mail list, a forum, a group on a social media platform, ...? What type of moderation, if any, do we want? Should it be a strictly on topic list or group, or should it be very loose and relaxed? Just some starter thoughts. Feel free to answer any questions or ask questions of your own. ~Kyle