Accessibility in general can vary depending on which HTML Doc Type i.e:
- XHTML 1.0 Transitional
- HTML 4.01 Transitional
This is because W3C has many accessibility attributes obsolete in HTML5, so your first decision should be which DOC type your going to support. Accessibility isn't my strongest field and not something I need to cater for but I decided to have a crack and I used HTML5 and used W3C HTML Techniques for Web Content Accessibility Guidelines 1.0 which you should use if Accessibility is important on your web design.
Anyway moving on in HTML5 good accessibility using tables will look something like this:
<CAPTION>Please Input Your information</CAPTION>
<th><label for="firstname" accesskey="n">Name</label></th>
<td><input id="firstname" tabindex="1"></td>
<th><label for="surname" >Surname</label></th>
<td><input id="surname" tabindex="2"></td>
Basically you need to ensure that things are described well as you know, the Caption field works well speech synthesizers and it should read exactly what the table is.. Your Information is pretty broad and you should describe your table best you can as this is important to impaired users, So in this example 'Please Input Your Information' is a good description as its asking for information, additionally you could add somewhere on the page why you require that information for even better accessibility.
tabindexsets the tab order, blind people and other impaired users will use tab very often as its a great key for them navigating.
accesskey sets focus point on the table, so in this case pressing N will focus the table.
In HTML4 you can use things like
ABBR which speech synthesizers will read out over labels as preferred method, for reasons unknown I'm not sure why this has been removed in HTML5 but none the less HTML5 fails validation when using it.
The other useful field I came across is
<table summary="I am a input table for user information"> which again is obsolete in version HTML5 which again unsure why because it seems pretty useful to add additional information, maybe W3C want the caption being used more, maybe someone else can answer this.