Amazon is definitely aware of Linux. They have apps running on Android
and even platforms that use Android as their OS. They support Linux in
AWS including their own flavor of Linux. I'm sure their are some staff
at Amazon who don't know about Linux, but that doesn't mean the company
is unaware of or doesn't care about Linux.
BTW, there is still a legal question as to whether a web site which
offers products or services to the public needs to be accessible. The
ADA doesn't have companion guidelines on what it means for a site to be
accessible and Domino's is going to court to claim that the ADA doesn't
require them to make their site or apps accessible. I think the ADA does
apply to public web sites, and I think Domino's will lose, but that
doesn't mean it isn't still an open legal question.
On 8/24/19 2:11 PM, Linux for blind general discussion wrote:
1. My comment regarding Linux is based on direct communications with
Amazon staff, who have confessed not to have heard of it,and who
have no direct contact with their so called accessibility team when
problems arise.
2. them properly compiled elinks and links function with java script.
3. Access is tied to interaction which is why even later editions of
lynx can manage some scripting, submit buttons for example.
4. since adaptive technology is often a substitution for the persons
eyes, hands, brain, and the like, what gives you the right to state
that technology choices are not tied to physical mandates? How does
your stance differ from those who claim that access need not exist at
all, or that all those sharing a label are the same?
5. the names of access or other individuals at amazon confirming your
assumption here? the legal stance is that if a site serves the
public, an individual can expect equal public access...which is why
alternative doors are to exist in the first place.
How do you know what low graphics can or cannot do if you do not
follow their development? This is about keyboard response which
exists in graphical browsers like elinks and links.
On Fri, 23 Aug 2019, Linux for blind general discussion wrote:
I don't believe for a minute that the accessibility staff at Amazon
has either forgotten or stopped caring about Linux accessibility.
Realistically though, it is possible that they have stopped worrying
about the very small number of people who still use text-based
browsers and expect them to work for shopping, banking and other
modern internet tasks. The thing is Linux accessibility in 2019 !=
lynx/links/elinks accessibility. In fact, this hasn't been the case
since about 2008 or so
.
Unfortunately, text-based browsers have not kept up with the rest of
the internet, and can't be expected to work well for most websites
without a major overhaul, especially since they don't even support
the latest HTML5 standards, nor do they support accessibility
standards that have been in place for years. Even w3m doesn't fully
support the w3c's own standards.
Yes, I can see why some people may want these light-weight and fast
browsers to work with Amazon, and yes, they should be made aware of
the problems that people are having. But to say that Amazon doesn't
care about Linux accessibility because their site doesn't work with a
text-based browser is at best a gross exageration, and is at worst a
grave disservice to those of us who use Linux and a screen reader at
the same time.
Imetumwa kutoka miti
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list
--
Christopher (CJ)
Chaltain at Gmail
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list