title: Advice on using .NET to generate semantic html
body: <p>I've just started working on a project which a) uses .NET and a fair bit of AJAX, and b) must comply to AA accessibility standards.</p>
  
  <p>.NET AJAX toolkit is ideal in one sense - it provides a non-javascript fallback for each bit of javascript interactivity - but equally it fails badly as the html generated by the controls is often completely unsemantic (eg I can't see a way to make the accordion control use ul/ol tags instead of divs).</p>
  
  <p>Are there any approaches that can make use of the positive aspects of the toolkit, while minimising the negative effect of the poor html?</p>