concept accessibility in category jQuery

This is an excerpt from Manning's book jQuery in Action, Third Edition.
As you can see from the listing, each field is composed of three elements: a label, an input (textarea for the message), and a span. The label element is used to specify the name of the field and has the for attribute set to improve the accessibility of the form. The <input>s and the <textarea> allow users to write the information required. Finally, span is used to show the feedback illustrated in figure 11.1. In addition to these elements, you have the Submit and the Reset buttons at the bottom of the form.
As it turns out, you can slightly update your project to solve this issue. What you need to do is edit contact.php so that it can distinguish whether the request is an Ajax one or not. If it’s an Ajax request, it can serve the JSON object; otherwise, it should use the data collected to fill a complete page and serve it to the user. Although it may seem like a simple change, it improves the accessibility of the demo and can save your users a lot of frustration. The presented approach, called progressive enhancement, has many advantages and is valid for more than just this project.

This is an excerpt from Manning's book jQuery UI in Action.
Accessibility is an important consideration when building anything for the web, but making even simple applications accessible to all audiences can be a difficult task. Documentation is scarce, screen readers can be tricky to test on, and specifications such as Accessible Rich Internet Applications (ARIA) can be complex and difficult to understand.
All jQuery UI widgets are designed with accessibility in mind. You can add widgets to your site and feel confident that everyone can use them. The jQuery UI widgets are keyboard accessible, use ARIA roles appropriately, and use proper markup to optimize user experiences on screen readers.