Here's my inventory, top row only.
all speak except eject and f17 f18 and f19
js
On Dec 2, 2008, at 1:17 PM, David Poehlman wrote:
I don't doubt you but my findings are that on the wired aluminum
keyboard,
the function keys do not speak except for f16 I think it is.
Also, the three most right keys on the row just above the numeric
key pad
do not speak.
----- Original Message -----
From: "Scott Howell" <[EMAIL PROTECTED]>
To: "General discussions on all topics relating to the use of Mac OS
X by
theblind" <[email protected]>
Sent: Tuesday, December 02, 2008 12:34 PM
Subject: Re: Problem with new aluminum Keyboards. Possible Defect?
Well start keyboard practice and press all the function keys and see
what you get. THey are called f1 through f16. I'm not saying there is
or is not a bug, I'm just pointing out to the original message that
the keys work for me.
On Dec 2, 2008, at 8:13 AM, David Poehlman wrote:
This is not a defect unless a lot of non vo stuff not speaking is a
defect
which I believe is a problem depending on how you look at it. I am
not
aware that they are called as fn numbers though.
----- Original Message -----
From: "Scott Howell" <[EMAIL PROTECTED]>
To: "General discussions on all topics relating to the use of Mac OS
X by
theblind" <[email protected]>
Sent: Tuesday, December 02, 2008 5:38 AM
Subject: Re: Problem with new aluminum Keyboards. Possible Defect?
I just tried this and I get up to f16 with no problems. Now I haven't
got a set of eyes here, but I didn't know there was a f17 or 18.
After
f12, there is the eject key and once you get to the row of keys above
the number pad, you have f16, but for the life of me I can't recall
what the other three keys are.
On Dec 2, 2008, at 4:09 AM, Alex Jurgensen wrote:
Hi,
Just wanted to let you know that I was in a local Apple retailer
today and turned on Keyboard help to play with the new IMac
keyboards. I love them by the way. Well, I noticed that the "f17",
"f18", and "f19" keys are not spoken by Voiceover.
I just wanted to let you know this. Can this be fixed for 10.5.6?
Thanks for listening,
Alex,
Scott Howell
[EMAIL PROTECTED]
Scott Howell
[EMAIL PROTECTED]
