Accessibility - Mobile development:
The Web Content Accessibility Guidelines is technical standard document that explains how to make web content more accessible to people with disabilities.
WCAG addresses barriers faced by a wide range of people with disabilities, including those with visual, auditory, physical, speech, cognitive and neurological disabilities.
ATAG: Authoring Tool Accessibility Guidelines (ATAG) addresses authoring tools:
Authoring tools can help developers and assist users in the creation of accessible web content through proper design standards.
- Websites that let users add content, such as blogs and wikis
- Tools designed to produce web content (e.g., What-you-see-is-what-you-get (WYSIWYG) HTML, XML editors)
- Web developers usually use authoring tools and evaluation tools to create web content.
ATAG 2.0 is divided into two parts:
- Part A relates to the accessibility of authoring tool user interfaces to authors with disabilities.
- Part B relates to support by authoring tools for the creation of web content that is more accessible to end users with disabilities.
WAI-ARIA: Accessible Rich Internet Applications (WAI-ARIA) addresses web applications, dynamic content and advanced user interface controls.
WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps screen reader users and keyboard users with dynamic content and advanced user interface controls developed with HTML, JavaScript, and related technologies.
Web Accessibility Toolkit (WET)::
The Web Accessibility Toolkit (WET) is a front-end framework of flexible and themeable templates and reusable components that are accessible, usable, interoperable, mobile friendly and multilingual.
Web Content Accessibility Guidelines (WCAG) 2.1:
WCAG 2.1 builds upon the previous version, WCAG 2.0, by adding new success criteria that address more recent technologies and user needs. It focuses on four main principles, often referred to as the "POUR" principles, which are the foundation of creating accessible content:
Perceivable:
Information and user interface components must be presented in ways that users can perceive. This includes providing alternatives for non-text content like images and multimedia.Operable:
User interface components and navigation must be operable by various means, including keyboard, mouse, and touch. It also covers time-based media like video and audio.Understandable:
Content and navigation should be clear and easy to understand. This includes providing legible text, predictable navigation, and clear instructions.Robust:
Content should be developed using technologies that are reliable and can be interpreted correctly by a wide range of user agents, including assistive technologies.
The Web Content Accessibility Guidelines is technical standard document that explains how to make web content more accessible to people with disabilities.
WCAG addresses barriers faced by a wide range of people with disabilities, including those with visual, auditory, physical, speech, cognitive and neurological disabilities.
WCAG 2.1 includes three levels of conformance, often referred to as "A," "AA," and "AAA":
Level A:
This includes the most basic accessibility features and is the minimum standard for accessibility. It addresses the most critical barriers to accessibility.Level AA:
This is the recommended level of conformance and covers a wide range of common barriers to accessibility. Meeting this level makes content significantly more usable for people with disabilities.Level AAA:
This is the highest level of conformance and addresses more advanced accessibility features. Meeting this level ensures a higher degree of accessibility, but it's not always achievable for all types of content.