I agree with that but in all my years of battling
sites I only once ran across someone willing to try using a screen reader
sadly!
----- Original Message -----
Sent: Thursday, August 16, 2018 8:59
AM
Subject: Re: [nvda] Change on Amazon
makes buying options less, possibly inaccessible with screenreaders while on
product page
I don't particularly care if they use a keyboard
themselves. It would be nice if at least one person reviewed the design
using a keyboard, but not just a keyboard, a screen-reader. You can't
evaluate a site from the keyboard without knowing how to use a
screen-reader. But if they don't want to bother doing that, the site
should be tested by blind people while the site is under development.
Gene
----- Original Message
-----
Sent: Thursday, August 16, 2018 9:58 AM
Subject: Re: [nvda] Change on Amazon makes buying options less,
possibly inaccessible with screenreaders while on product page
lol Gene!
keep telling folks that if these designers
would just use these sites with a keyboard they might find out how not user
friendly they are!
----- Original Message -----
Sent: Wednesday, August 15, 2018 2:01
PM
Subject: Re: [nvda] Change on Amazon
makes buying options less, possibly inaccessible with screenreaders while on
product page
Just one more example of what happens when
someone or a corporation, which is bye law a person, so someone, with very
little brain, like Winney the Pu (spelling) still doesn't know after years
of working with advocacy groups to make their site accessible, that you
don't just make changes. You test them with blind users before
implementing them. This is clearly something a sighted person would
see. A screen-reader wouldn't read it automatically. the page
has changed. Perhaps this change could be properly coded using Aria or
JAVA script, I don't have the technical knowledge to know how best to do
it. The person would be placed on the correct control and the text
would be read as well as the control you are on. But no.
Obviously the changes weren't tested, not even with one or two blind
people. Even Winnie The Pu learns faster.
Gene
----- Original Message -----
Sent: Wednesday, August 15, 2018 3:47 PM
Subject: Re: [nvda] Change on Amazon makes buying options less,
possibly inaccessible with screenreaders while on product
page
Ok, that works. Thank you. A stupid workaround, but hopefully
amazon will
change things back, not holding my breath, or the NVDA
developers will
figure out how to work with this kind of
change.
Travis
----- Original Message -----
From: "Danni" <luv2ride67@...>
To:
<nvda@nvda.groups.io>
Sent:
Wednesday, August 15, 2018 12:46 PM
Subject: Re: [nvda] Change on Amazon
makes buying options less, possibly
inaccessible with screenreaders
while on product page
I need to correct 1 thing I said not alt
tab but shift tab gets you to the
buy it now button and it works I've
been doing it for the last 2 days!
to recap it's check submit queery
then spacebar insert then shift tab to buy
now!
----- Original
Message -----
From: "Kwork" <istherelife@...>
To:
<nvda@nvda.groups.io>
Sent:
Tuesday, August 14, 2018 8:13 PM
Subject: Re: [nvda] Change on Amazon
makes buying options less, possibly
inaccessible with screenreaders while
on product page
> Thanks all for your messages and thoughts.
Maybe it's time to open a
> ticket
> now that I know it's not
me.
> Incidentally, I tried it also on the portable ESR Firefox, one
still in
> the
> version 52 series, latest Chrome, and latest
IE, and all are showing the
> no
> numbered heading level. For
me, tabbing around didn't work. I'll try
> Travis's suggestions in a
while.
>
> ----- Original Message -----
> From: "Annette
Moore" <angelgirl52376@...>
>
To: <nvda@nvda.groups.io>
> Sent:
Tuesday, August 14, 2018 7:54 PM
> Subject: Re: [nvda] Change on
Amazon makes buying options less, possibly
> inaccessible with
screenreaders while on product page
>
>
> Thanks, Travis.
I will file this info away because I, too, use Kindle
> Unlimited. I
used it just the other day to grab a book and it worked
> just fine:
the correct buttons showed in the correct places and showed
> as
actual buttons. thank you. I wouldn't have even thought to route the
>
NVDA cursor to the buttton because I'm not as familiar with that as
I
> really need to be. I never used the virtual mouse cursor in
System
> Access when I used it and rarely ever used the JAWS cursor in
JAWS when
> I used that because I didn't really understand how it
worked, but it
> sounds like it's time for me to learn to understand
it. LOL! Thanks again.
>
> Annette
> On 8/14/2018 9:24 PM,
Travis Siegel wrote:
>> The problem exists when using the kindle
unlimited program to get a
>> book. You have to tab to the button
(NVDA sees it as a button), but
>> pressing b doesn't go to it.
However, when I was sitting on it (after
>> finding it via the tab
key), I used nvda-F1 to bring up it's
>> information, and it is
clearly labeled as a button, so no clue why b
>> doesn't navigate
to it. I've also discovered the only for me to click
>> the button
is to use the route command (nvda-numpad minus) to route
>> the
nvda cursor to it, then press nvda-shift-numpad enter. (yes, I
>>
need the shift, without it, it activates an entirely different
page
>> which has ne bearing on what I'm trying to do). No idea why
the shift
>> works and w/o the shift doesn't, but there it is.
That's the only
>> I've managed to get my books into the kindle app
using the web site.
>> Interestingly enough, using safari on the
Iphone doesn't have this
issue.
>>
>>
>>
>>
>
>
>
>
>
>
>
|
