Web Content Accessibility Guidelines (WCAG) 2.1: Difference between revisions

From LINKS Community Center
Jump to: navigation, search
Dinu (talk | contribs)
No edit summary
Dinu (talk | contribs)
No edit summary
 
(6 intermediate revisions by 3 users not shown)
Line 3: Line 3:
|Language=English
|Language=English
|Year Published=2018
|Year Published=2018
|Target Audience=Businesses, Civil Society, Media, Policy Makers, Practitioners, Researchers
|Status=Published
|Status=Published
|Covers Thematic=Legal/Standards, Vulnerable groups
|Covers Thematic=Legal/Standards, Vulnerable groups
|Audience Experience Level=Intermediate
|Audience Experience Level=Intermediate
|Source Website=https://www.w3.org/TR/WCAG21/
|Source Website=https://www.w3.org/TR/WCAG21/
|Abstract=These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general
|Synopsis=These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general
The individuals and organizations that use WCAG vary widely and include Web designers and developers, policy makers, purchasing agents, teachers, and students.


The individuals and organizations that use WCAG vary widely and include Web designers and developers, policy makers, purchasing agents, teachers, and students. In order to meet the varying needs of this audience, several layers of guidance are provided including overall principles, general guidelines, testable success criteria and a rich collection of sufficient techniques, advisory techniques, and documented common failures with examples, resource links and code.
In order to meet the varying needs of this audience, several '''layers of guidance''' are provided including overall principles, general guidelines, testable success criteria and a rich collection of sufficient techniques, advisory techniques, and documented common failures with examples, resource links and code.


*'''Principles'''
*'''Principles'''
** At the top are four principles that provide the foundation for Web accessibility: perceivable, operable, understandable, and robust.  
** At the top are four principles that provide the foundation for Web accessibility:  
***perceivable
***operable
***understandable,
***robust.  
*'''Guidelines'''
*'''Guidelines'''
**Under the principles are guidelines.  
**Under the principles are guidelines.  
Line 28: Line 32:
***those that are sufficient for meeting the success criteria and  
***those that are sufficient for meeting the success criteria and  
***those that are advisory.  
***those that are advisory.  
**The advisory techniques go beyond what is required by the individual success criteria and allow authors to better address the guidelines. **Some advisory techniques address accessibility barriers that are not covered by the testable success criteria.  
**The advisory techniques go beyond what is required by the individual success criteria and allow authors to better address the guidelines.
**Some advisory techniques address accessibility barriers that are not covered by the testable success criteria.  
***Where common failures are known, these are also documented
***Where common failures are known, these are also documented
|Is Archived=No
|Is Archived=No
|Disaster Management Phase=Before, During, After
}}
}}
Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities.

Latest revision as of 13:13, 14 August 2023

Quick Facts

Publishing Organisation:
W3C
Year:
2018
Languages:
English
Status:
Published
Covers Thematic
  • Legal/Standards Legal Requirement means any federal, state, local, municipal, foreign or other law, statute, constitute, principle of common law, resolution, ordinance, code, edict, decree, rule, regulation, ruling or requirement issued, enacted, adopted, promulgated, implemented or otherwise put into effect by or under the authority of any Governmental Body. </br></br>Source: https://www.lawinsider.com/dictionary/legal-requirement</br></br>Standards are voluntary documents that set out specifications, procedures and guidelines that aim to ensure products, services, and systems are safe, consistent, and reliable. They cover a variety of subjects, including consumer products and services, the environment, construction, energy and water utilities, and more.</br></br>Source: https://www.standards.org.au/standards-development/what-is-standard
  • Vulnerable groups Those groups that, due to physical, social, economic and environmental factors or processes, are more exposed and susceptible to the impacts of hazards.
  • Target audience
    Audience experience level
  • Intermediate Those who currently use social media to communicate with the public and have developed a draft social media strategy, even if this is not thoroughly documented or communicated across the organisation</br></br>Source: https://www.fp7-emergent.eu/wp-content/uploads/2017/09/20170529_D7.3_Guidelines_to_increase_the_benefit_of_social_media_EmerGent.pdf
  • Disaster Management Phase
  • Before Comprises 'Preparedness Phase' and 'Prevention Phase'</br></br>Preparedness action is carried out within the context of disaster risk management and aims to build the capacities needed to efficiently manage all types of emergencies and achieve orderly transitions from response to sustained recovery.</br></br>Source: https://www.undrr.org/terminology/preparedness</br></br>Prevention (i.e., disaster prevention) expresses the concept and intention to completely avoid potential adverse impacts of hazardous events.</br></br>Source: https://www.undrr.org/terminology/prevention
  • During Also referred to as "Response Phase"</br></br>Actions taken directly before, during or immediately after a disaster in order to save lives, reduce health impacts, ensure public safety and meet the basic subsistence needs of the people affected.</br></br>Annotation: Disaster response is predominantly focused on immediate and short-term needs and is sometimes called disaster relief. Effective, efficient and timely response relies on disaster risk-informed preparedness measures, including the development of the response capacities of individuals, communities, organizations, countries and the international community.</br></br>Source: https://www.undrr.org/terminology/response
  • After Also referred to as 'Recovery Phase'</br></br>The restoring or improving of livelihoods and health, as well as economic, physical, social, cultural and environmental assets, systems and activities, of a disaster-affected community or society, aligning with the principles of sustainable development and “build back better”, to avoid or reduce future disaster risk.</br></br>Source: https://www.undrr.org/terminology/recovery
  • Synopsis

    These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general The individuals and organizations that use WCAG vary widely and include Web designers and developers, policy makers, purchasing agents, teachers, and students.

    In order to meet the varying needs of this audience, several layers of guidance are provided including overall principles, general guidelines, testable success criteria and a rich collection of sufficient techniques, advisory techniques, and documented common failures with examples, resource links and code.

    • Principles
      • At the top are four principles that provide the foundation for Web accessibility:
        • perceivable
        • operable
        • understandable,
        • robust.
    • Guidelines
      • Under the principles are guidelines.
      • The 13 guidelines provide the basic goals that authors should work toward in order to make content more accessible to users with different disabilities.
      • The guidelines are not testable, but provide the framework and overall objectives to help authors understand the success criteria and better implement the techniques.
    • Success Criteria
      • For each guideline, testable success criteria are provided to allow WCAG 2.0 to be used where requirements and conformance testing are necessary such as in design specification, purchasing, regulation, and contractual agreements.
      • In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest).
      • Additional information on WCAG levels can be found in Understanding Levels of Conformance.
    • Sufficient and Advisory Techniques
      • For each of the guidelines and success criteria in the WCAG 2.0 document itself, the working group has also documented a wide variety of techniques.
        • The techniques are informative and fall into two categories:
        • those that are sufficient for meeting the success criteria and
        • those that are advisory.
      • The advisory techniques go beyond what is required by the individual success criteria and allow authors to better address the guidelines.
      • Some advisory techniques address accessibility barriers that are not covered by the testable success criteria.
        • Where common failures are known, these are also documented

    Linked to