WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: .NET wrapping entire page in a form element

for

From: Greg Wocher
Date: Jul 9, 2014 2:00PM

Hello,
I used asp.net and C# at my college and I never noticed any
accessibility challenges with this at all. Both JAWS and NVDA worked
with the applications I developed quite well. I am curious as to what
problems you think might happen from this especially since I am a novice
in this area. As a matter of fact I just finished my degree about two
weeks ago. My degree is a Bachelors of science in Computer Information
Systems specializing in Web Development and Administration.

Thanks,
Greg Wocher

Follow me on Twitter @GWocher

On 7/9/2014 2:08 PM, Jordan Wilson wrote:
> Greetings all,
>
> I'm looking for more information regarding the common practice of wrapping the entire contents of a page in a <form> element on .NET projects, particularly to use ViewState. That seems like a detrimental practice both for standards based coding and for accessibility.
>
> Are there standard workarounds to avoid using the <form> wrapper solution?
> Is there information about how it adversely affects assistive technology users?
>
> The best information I could find online was a random thread on a CMS forum:
> http://devnet.kentico.com/forums/f67/t43834/necessary-usage-of-form-on-master-page
>
> Any accessibility specific thoughts or experience with that would be useful. I'm not working on the backend team, but I want to make sure the backend team doesn't inject a form element wrapper and break our accessibility efforts.
>
> Jordan Wilson
> <EMAIL REMOVED>
> > > >