From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: Roku accessibility (was Re: Youtube TV Site?)
Date: Thu, 22 Jun 2017 22:52:56 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1706222249040.5243@server2.shellworld.net> (raw)
In-Reply-To: <CAO2sX3055BxsF4kqCph7K+neTJN6kETMPD-BKAFXx8O3xOUTzg@mail.gmail.com>
There is no such thing as most developers. Regardless those doing
business in global jurisdictions where wacg 2.0 is incorporated into
legal requirements might find themselves in trouble.
Now, if a web designer remembers what the word cascading style sheets
means, your inability to point might not reflect what i s possible in a
truly configured low graphics environment.
Or so that has been my personal experience.
I can say absolutely firmly that personal applies to me...which is the
case for each individual.
Karen
On Fri, 23 Jun 2017, Linux for blind general discussion wrote:
> Considering how hit or miss websites are when it comes to ease of
> blind use even in a browser as mainstream and feature rich(arguably to
> the point of excess) as Firefox, I'm inclined to believe most
> webmasters have made no effort to ensure accessibility and that when a
> website is fully accessible, it's as often by accident as by design. I
> doubt the average creator of webpages even knows that browsers like
> elinks and lynx even exist or even takes the time to ensure there
> pages load as intended in mainstream graphical browsers other than the
> one they use themselves.
>
> That said, from what I've tried, I'd have to say currently available
> console web browsers leave much to be desired, with even sites that
> have never given me problems in Firefox sometimes being unusable in
> text-mode browsers assuming I can even figure out how to point the
> text-mode browser at a given URl. It's a real shame that even the best
> text browsers seem so limited compared to their graphical cousins,
> especially since Firefox is the only reason I ever launch an Xsession.
>
> --
> Sincerely,
>
> Jeffery Wright
> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
> Former Secretary, Student Government Association, College of the Albemarle.
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
next prev parent 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
` 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
` Linux for blind general discussion [this message]
` 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=Pine.LNX.4.64.1706222249040.5243@server2.shellworld.net \
--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).