Has anyone ever made a website to conform to section 508 standards. My question is my companies target audience is school systems. They may/may not have the most current browsers. We still have to code for netscape 4 people. How do you write stylesheets that chnage font dynamically without breaking UI of page.<!--content-->Take a look under the hood at <!-- m --><a class="postlink" href="http://www.saintjohns.ang-md.org/">http://www.saintjohns.ang-md.org/</a><!-- m -->. And view the site in MSIE 6, Opera 7, Netscape 4.7 and Lynx.<!--content-->thx for the site, unfortunetely it doesnt look the same in netscape 4<!--content-->Originally posted by joer <br />
thx for the site, unfortunetely it doesnt look the same in netscape 4 Nor does it look the same in Lynx, that's the whole idea. You cannot make your site look the same in all graphical browsers and still work on all browsers but you can make your site work well on all browsers while maintaining your "optimal" look and feel for 99% of users.<!--content-->No, because 508 is irrelevant to me personally (not living in the USA) although I have created various websites that I have deemed to follow the Conformance to the W3C Web Content Accessibility Guidelines 1.0.<br />
<br />
Some authors use tricks like @import to hide stylesheets from old Netscape 4.7x<!--content-->I have all my sites look 99% the same on all mac, and windows browsers including opera/safari netscape 4.7, netscape 6, netscape 7, mozilla,, firebird, ie. My problem with section 508 is the ability to change fonts for people with disability and having UI stay the same without breaking structure. I realize the text only browsers will not show site exactly the same.<!--content-->No doubt you are using tables for layout, and that will make the page inaccesible to users of certain types of screen readers. From the HTML 4.01 Specification:<br />
Tables should not be used purely as a means to layout document content as this may present problems when rendering to non-visual media. Additionally, when used with graphics, these tables may force users to scroll horizontally to view a table designed on a system with a larger display. To minimize these problems, authors should use style sheets to control layout rather than tables.<br />
<!-- m --><a class="postlink" href="http://www.w3.org/TR/html4/struct/tables.html#h-11.1">http://www.w3.org/TR/html4/struct/tables.html#h-11.1</a><!-- m --><!--content-->yes the whole site is made in tables, and some css for layers. I would love to make the entire site in css but me have to support netscape 4 which has limitations on some css attributes. We also have to support windows 95, and os 8.5 on mac. If we could only used standard based browsers, i think it would be quite easy to build a good looking site<!--content-->Please note that the site referenced above works on all browsers - and it uses only CSS for layout.<!--content-->I think you misunderstand what "compatible" and "working" site means....<!--content-->
thx for the site, unfortunetely it doesnt look the same in netscape 4 Nor does it look the same in Lynx, that's the whole idea. You cannot make your site look the same in all graphical browsers and still work on all browsers but you can make your site work well on all browsers while maintaining your "optimal" look and feel for 99% of users.<!--content-->No, because 508 is irrelevant to me personally (not living in the USA) although I have created various websites that I have deemed to follow the Conformance to the W3C Web Content Accessibility Guidelines 1.0.<br />
<br />
Some authors use tricks like @import to hide stylesheets from old Netscape 4.7x<!--content-->I have all my sites look 99% the same on all mac, and windows browsers including opera/safari netscape 4.7, netscape 6, netscape 7, mozilla,, firebird, ie. My problem with section 508 is the ability to change fonts for people with disability and having UI stay the same without breaking structure. I realize the text only browsers will not show site exactly the same.<!--content-->No doubt you are using tables for layout, and that will make the page inaccesible to users of certain types of screen readers. From the HTML 4.01 Specification:<br />
Tables should not be used purely as a means to layout document content as this may present problems when rendering to non-visual media. Additionally, when used with graphics, these tables may force users to scroll horizontally to view a table designed on a system with a larger display. To minimize these problems, authors should use style sheets to control layout rather than tables.<br />
<!-- m --><a class="postlink" href="http://www.w3.org/TR/html4/struct/tables.html#h-11.1">http://www.w3.org/TR/html4/struct/tables.html#h-11.1</a><!-- m --><!--content-->yes the whole site is made in tables, and some css for layers. I would love to make the entire site in css but me have to support netscape 4 which has limitations on some css attributes. We also have to support windows 95, and os 8.5 on mac. If we could only used standard based browsers, i think it would be quite easy to build a good looking site<!--content-->Please note that the site referenced above works on all browsers - and it uses only CSS for layout.<!--content-->I think you misunderstand what "compatible" and "working" site means....<!--content-->