Server side controls and their markup in ASP.Net 1.1
-
hey guys, well I'm working on a web site, medium sized, pretty heavily data driven. Now I need to pretty much figure out on my own how to make this site more accessible (to comply with American Disability Act). Anyways here are some of my concerns: 1- Server side controls such as datagrid, repeater, drop down lists, combo boxed and things like that renders HTML 4.01 (XHTML 1). Now I'm no expert in HTML, and that's why this is going to be challenging. So question is if I just dive in the HTML mode of for instance default.aspx page....and start messing around with HTML in their...well chances are design view will disappear if i make a mistake. I need guidance as to what's the best approaach here to make these markup changes. 2- HTML tables, frames and things of that nature don't seem to work well with screen readers (used by blind/low vision folks). In other words, what is the best approach/practice here. I'm sure some of you guys have done things like this in the past. Please help me out here. Thanks Sam
----------------------------- If you don't go after what you want, you'll never have it. If you don't ask, the answer is always no. If you don't step forward, you're always in the same place. -Nora Roberts
-
hey guys, well I'm working on a web site, medium sized, pretty heavily data driven. Now I need to pretty much figure out on my own how to make this site more accessible (to comply with American Disability Act). Anyways here are some of my concerns: 1- Server side controls such as datagrid, repeater, drop down lists, combo boxed and things like that renders HTML 4.01 (XHTML 1). Now I'm no expert in HTML, and that's why this is going to be challenging. So question is if I just dive in the HTML mode of for instance default.aspx page....and start messing around with HTML in their...well chances are design view will disappear if i make a mistake. I need guidance as to what's the best approaach here to make these markup changes. 2- HTML tables, frames and things of that nature don't seem to work well with screen readers (used by blind/low vision folks). In other words, what is the best approach/practice here. I'm sure some of you guys have done things like this in the past. Please help me out here. Thanks Sam
----------------------------- If you don't go after what you want, you'll never have it. If you don't ask, the answer is always no. If you don't step forward, you're always in the same place. -Nora Roberts
I haven't done this before but come across the links that you might be interested in: http://www.wdvl.com/Authoring/Design/Friendly/[^] http://www.allyhazell.com/webdesignresources.php[^] http://www.aspnetresources.com/blog/color_blidness_simulator_announced.aspx[^] And if you want to make changes in the markup generated by those controls I guess that you will need to get yourself familiar with them and see how you can control how the controls render in the way you want.
-
I haven't done this before but come across the links that you might be interested in: http://www.wdvl.com/Authoring/Design/Friendly/[^] http://www.allyhazell.com/webdesignresources.php[^] http://www.aspnetresources.com/blog/color_blidness_simulator_announced.aspx[^] And if you want to make changes in the markup generated by those controls I guess that you will need to get yourself familiar with them and see how you can control how the controls render in the way you want.
Thanks for your response, is there anyone else out here who may have done something along these lines. I would appreciate it. Thanks sam
----------------------------- If you don't go after what you want, you'll never have it. If you don't ask, the answer is always no. If you don't step forward, you're always in the same place. -Nora Roberts