What steps can be taken to create a semantic, accessible, standards-compliant client on the client side using ASP.NET Web forms?

I understand that it may not be possible to separate the client side from the server code in ASP.NET Web formats. What steps can be taken to create a website on this basis that meets web standards?

I am particularly interested in making the site accessible with JavaScript disabled and compatible with WCAG2 at AA compliance level.

Is it possible to achieve a separation between content (HTML), presentation (CSS) and behavior (JavaScript)?

+3
source share
4 answers

, ASP.Net WebForms:

  • ASP.Net , . , ASP.Net. ASP.Net 4 , HTML (. ).
  • , , . , , , .
  • - , .
+2

Render, , , , .

+1
+1

ASP.NET, ASP.NET MVC. MVC ASP.NET. , HTML, .

If you cannot select MVC and are not comfortable with the default output for the ASP.NET server element, you can use the Render method of the ASP.NET server element. See Providing ASP.NET Server Management .

You can also override the output of child controls if its a composite control, such as a DataGrid.

Hope this helps.

0
source

Source: https://habr.com/ru/post/1755727/


All Articles