Re: Safari 4.x critically broken yet again

2009-07-07 Thread Alex Jurgensen
Hi,
Dear accessibility team:

I have included the following code below. The issues are that in  
Webkit the radio buttons read properly in my opinion. The same code in  
Safari does not. There are also issues with the dropdown box that does  
not work in either Safari or Webkit.

I provide this as VoiceOver feedback in the hope that we can build a  
better screen reader together.

Below my code is a previous e-mail explaining the problem with the  
dropdown menus and yet another message which contains a description of  
a problem I found with input fields.

Code:


html
head
title Accessibility example/title
/head
body
form action=accessibility.cgi method=post
input name=service type=hidden value=Contrast


Service: labelinput checked= name=ca-sfu-icat-accessibilityOn  
type=radio value=onOn/label  labelinput checked=true  
name=ca-sfu-icat-accessibilityOn type=radio value=offOff/label
span class=ca-sfu-icat-accessibilitySettings id=ca-sfu-icat- 
accessibilityContrastSettingslabel for=ca-sfu-icat- 
accessibilityContrastLevelContrast Level:/labelselect id=ca-sfu- 
icat-accessibilityContrastLevel  
name=caSfuIcatAccessibilityLeveloption value=iC1High (White on  
Black)/optionoption value=C2Semi-contrast (Greyskale)/option/ 
select/spanbr
input id=ca-sfu-icat-accessibilityServiceUpdate name=save  
type=submit value=update
/form
/body
/html

END of Code

Thanks again,
Alex,


Begin E-mail 1:
On 6-Jul-09, at 7:38 AM, Alex Jurgensen wrote:

 Hi,
 Dear Accessibility:

 I really appreciate your speedy response on the issue I reported  
 recently where form elements such as input tags were not properly  
 associated with their labels. I will stress, however, that support  
 of the title attribute as done in Safari 4.x brings greater web  
 design flexibility with regards to accessibility. However, fallback  
 mechanisms would be helpful for older sites.

 Unfortunately, I must report the same issue is now occurring with  
 Drop Down Menus. Consider the code:

 CODE:

 html
 head
 title
 Dropdown Sample
 /title
 /head
 body
 label for=dropdownChoose your province:/label
 select id=dropdown name=myProvince
 option value=bcBritish Columbia/option
 option value=abAlberta/option
 /select
 /body
 /html

 The dropdown's label should be Choose Your Province, but instead  
 no label is returned.

 Regards,
 Alex,

END of E-mail 1

Begin E-mail 2:


On 27-Jun-09, at 4:44 PM, Alex Jurgensen wrote:
 Hi,
 Dear Accessibility:

 This shouldn't be a problem to fix in the current release of Leopard  
 10.5.7. It was working prior to the Webkit Nightly builds of two  
 months ago or so, and the Safari 4.x series. I feel that it is worth  
 fixing in Leopard as many of the blind community are still on PPC  
 machines and won't be making the switch to SL.

 Regards,
 Alex,


 On 26-Jun-09, at 3:39 PM, Accessibility wrote:

 Hi Alex:

 Thank you for reporting this. We're not aware of a work-around for  
 the current release, but will do our best to address it in Snow  
 Leopard.


 On Jun 25, 2009, at 12:14 PM, Alex Jurgensen wrote:

 Hi,
 Dear accessibility team et al:

 I am the web accessibility consultant for my organization.

 One of the developers brought it to my attention that VoiceOver  
 and Safari 4.x have problems associating labels with elements in  
 forms, particularly the text input fields. Further research  
 revealed that about 90% of the site which was nearly all  
 accessible has been lost because the text fields all lost their  
 labels with Voiceover.

 Text cases also revealed that VoiceOver requires a title  
 attribute in a text input field to label it, such as on 
 http://labs.google.com/accessible/ 
  . I can appreciate why this is done, because it gives better  
 customizing of field labels, but unfortunately, when none is  
 present, VO does not fall back to labels as expected.

 Is there anything I can do to remedy this?

 Regards,
 Alex,

 END of E-mail 2

Regards,
Alex,



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MacVisionaries group.
To post to this group, send email to macvisionaries@googlegroups.com
To unsubscribe from this group, send email to 
macvisionaries+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/macvisionaries?hl=en
-~--~~~~--~~--~--~---



Re: Safari 4.x critically broken yet again

2009-07-07 Thread Michael Huckabay
Hi elix. Yes sifarey is quite broken. Till it is fixed I'm using  
webkit. It seam's to work quite well and I like it a lot. Just a work  
around till sifarey is fixed. Thank's for the e-maile though.
On 7-Jul-09, at 9:34 AM, Alex Jurgensen wrote:

 Hi,
 Dear accessibility team:

 I have included the following code below. The issues are that in  
 Webkit the radio buttons read properly in my opinion. The same code  
 in Safari does not. There are also issues with the dropdown box that  
 does not work in either Safari or Webkit.

 I provide this as VoiceOver feedback in the hope that we can build a  
 better screen reader together.

 Below my code is a previous e-mail explaining the problem with the  
 dropdown menus and yet another message which contains a description  
 of a problem I found with input fields.

 Code:


 html
 head
 title Accessibility example/title
 /head
 body
 form action=accessibility.cgi method=post
 input name=service type=hidden value=Contrast


 Service: labelinput checked= name=ca-sfu-icat-accessibilityOn  
 type=radio value=onOn/label  labelinput checked=true  
 name=ca-sfu-icat-accessibilityOn type=radio value=offOff/ 
 label
 span class=ca-sfu-icat-accessibilitySettings id=ca-sfu-icat- 
 accessibilityContrastSettingslabel for=ca-sfu-icat- 
 accessibilityContrastLevelContrast Level:/labelselect id=ca- 
 sfu-icat-accessibilityContrastLevel  
 name=caSfuIcatAccessibilityLeveloption value=iC1High (White  
 on Black)/optionoption value=C2Semi-contrast (Greyskale)/ 
 option/select/spanbr
 input id=ca-sfu-icat-accessibilityServiceUpdate name=save  
 type=submit value=update
 /form
 /body
 /html

 END of Code

 Thanks again,
 Alex,


 Begin E-mail 1:
 On 6-Jul-09, at 7:38 AM, Alex Jurgensen wrote:

 Hi,
 Dear Accessibility:

 I really appreciate your speedy response on the issue I reported  
 recently where form elements such as input tags were not properly  
 associated with their labels. I will stress, however, that support  
 of the title attribute as done in Safari 4.x brings greater web  
 design flexibility with regards to accessibility. However, fallback  
 mechanisms would be helpful for older sites.

 Unfortunately, I must report the same issue is now occurring with  
 Drop Down Menus. Consider the code:

 CODE:

 html
 head
 title
 Dropdown Sample
 /title
 /head
 body
 label for=dropdownChoose your province:/label
 select id=dropdown name=myProvince
 option value=bcBritish Columbia/option
 option value=abAlberta/option
 /select
 /body
 /html

 The dropdown's label should be Choose Your Province, but instead  
 no label is returned.

 Regards,
 Alex,

 END of E-mail 1

 Begin E-mail 2:


 On 27-Jun-09, at 4:44 PM, Alex Jurgensen wrote:
 Hi,
 Dear Accessibility:

 This shouldn't be a problem to fix in the current release of  
 Leopard 10.5.7. It was working prior to the Webkit Nightly builds  
 of two months ago or so, and the Safari 4.x series. I feel that it  
 is worth fixing in Leopard as many of the blind community are still  
 on PPC machines and won't be making the switch to SL.

 Regards,
 Alex,


 On 26-Jun-09, at 3:39 PM, Accessibility wrote:

 Hi Alex:

 Thank you for reporting this. We're not aware of a work-around for  
 the current release, but will do our best to address it in Snow  
 Leopard.


 On Jun 25, 2009, at 12:14 PM, Alex Jurgensen wrote:

 Hi,
 Dear accessibility team et al:

 I am the web accessibility consultant for my organization.

 One of the developers brought it to my attention that VoiceOver  
 and Safari 4.x have problems associating labels with elements in  
 forms, particularly the text input fields. Further research  
 revealed that about 90% of the site which was nearly all  
 accessible has been lost because the text fields all lost their  
 labels with Voiceover.

 Text cases also revealed that VoiceOver requires a title  
 attribute in a text input field to label it, such as on 
 http://labs.google.com/accessible/ 
  . I can appreciate why this is done, because it gives better  
 customizing of field labels, but unfortunately, when none is  
 present, VO does not fall back to labels as expected.

 Is there anything I can do to remedy this?

 Regards,
 Alex,

 END of E-mail 2

 Regards,
 Alex,



 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MacVisionaries group.
To post to this group, send email to macvisionaries@googlegroups.com
To unsubscribe from this group, send email to 
macvisionaries+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/macvisionaries?hl=en
-~--~~~~--~~--~--~---