Accessibility seeks to make an application or website usable by everyone, including people with disabilities such as visual, auditory, ambulatory, or cognitive impairment. *This tag should NOT be used for:* programming that requires "accessing" a process in multiple threads, a object in a class, a resource on a network, etc. or responsive design, which deals with serving content to a wide range of devices, unless there are also accessibility concerns.
Accessibility seeks to make an application or website usable by everyone, including people with disabilities such as visual, auditory, mobility or cognitive impairment. For example, usage of alt="description" text for graphic images on the web can help users with low-functioning vision.
Accessible design for the Internet is formally guided by the Web Content Accessibility Guidelines (WCAG), the Authoring Tool Accessibility Guidelines (ATAG) and the Web Accessibility Initiative's Accessible Rich Internet Applications standard (WAI-ARIA).
Accessible design may be required by law, notably Section 508 of the Rehabilitation Act of 1973 (USA) and the European Accessibility Act (Europe).
Other helpful resources are found at WebAIM.org.
Stand-alone software is made accessible by thoughtful design and APIs such as Microsoft UI Automation for Windows.
This tag should not be used for:
- programming that requires "accessing" a process in multiple threads, a object in a class, a resource on a network, etc.
- responsive-design, which deals with serving content to a wide range of devices. (This can be closely related at times, but is generally a separate topic.)
