Domain 1 (40%)

• Be familiar with WCAG 2.2 Success Criteria [Intentionally left blank]
  • Identify the conformance level of each WCAG 2.2 success criterion.[Intentionally left blank]
  • Understand the intent, requirements, and impact of each principle, guideline, and success criterion. [Intentionally left blank]
  • Be familiar with Sufficient Techniques, Failure, and Advisory Techniques for each success criterion. [Intentionally left blank]
• Understand the relationship between principles, guidelines, and success criteria.
  • Principle → Guideline → Success Criteria
    • Principles: Perceivable, Operable, Understandable, and Robust (POUR).
    • Guidelines: Broad recommendations on making content accessible.
    • Success Criteria: Specific, testable statements on how to achieve each guideline.
• Understand the conformance level designations (A, AA, AAA).
  • Level A is the minimum level.
  • Level AA includes all Level A and AA requirements. Many organizations strive to meet Level AA.
  • Level AAA includes all Level A, AA, and AAA requirements.
• Understand the three types of techniques and the W3C vetting process for techniques.
  • Sufficient: Methods that meet the success criteria.
  • Failure: Techniques that result in non-compliance.
  • Advisory: Methods that can enhance accessibility but aren't required.
• Understand the difference between normative and non-normative information in WCAG 2.2.
  • Introductory material, appendices, sections marked as "non-normative", diagrams, examples, and notes are informative (non-normative).
• Understand the purpose and impact of WAI-ARIA 1.2.
  • provides developers with a set of attributes and roles to define accessible user interface elements on websites
  • allows assistive technologies to better understand and interpret complex web content
  • improves accessibility for people with disabilities by conveying semantic information about widgets, structures, and behaviors on a webpage
• Understand the WAI-ARIA 1.2 model of roles and properties.
  • Roles + Attributes (State [dynamic] or property [less dynamic])
• Know when and why to use WAI-ARIA 1.2, and when to use standard HTML instead.
  • Use native HTML when possible
• Understand how ATAG 2.0 applies to web content authoring tools. Understand the intent, requirements, and impact of each principle, guideline, and success criterion. [Intentionally left blank]
• Understand the meaning and intent of the two main sections of ATAG 2.0.
  • Part A: Make the authoring tool user interface accessible
  • Part B: Support the production of accessible content
• Distinguish between good, automated practices in authoring tools and good practices that require author/user input. Understand the power and limitations of automated accessibility authoring features.
  • Automation - Excels in ensuring consistent and scalable accessibility by handling routine, repetitive, and rules-based tasks
    • Accessibility checks/summaries
    • Generating semantic structures for headings, lists, and links
    • Provide templates that are already formatted for accessibility
  • Author input - Critical for context-specific tasks where the author’s judgment is needed
    • Alt text for images
    • Error messages/requirements for forms
    • Ensuring readability/reducing jargon
    • Uploading vtt/srt for closed captions
    • Uploading transcripts
• Understand the difference between normative and non-normative information in ATAG 2.0.
  • Implementing ATAG 2.0 is NON-normative
• Know what kind of technologies are addressed by EN 301 549
  • Developed to support procurement of accessible products and services
• Identify the similarities and differences between WCAG and EN 301 549
  • While WCAG primarily focuses on web and mobile content, EN 301 549 expands its scope to include hardware, telecommunications, and other ICT components.
• Describe how WCAG is represented in EN 301 549
  • WCAG guidelines are integrated into EN 301 549, but EN 301 549 may include additional requirements for compliance with European laws.
• Identify requirements beyond WCAG that are relevant for compliance with the Web Accessibility Directive 2016/2102.
  • Scope: public sector specific; includes the requirement for accessible documents
  • Accessibility statement: Required, must also include feedback mechanism
  • Enforcement: EU member states must submit reports to the European Commission every two years
  • The Web Accessibility Directive is a directive (common framework), not a regulation, so each EU member state must transpose the directive into their national laws.
• Understand the intent and scope of requirements in Annex A Table A1 that go beyond WCAG.
  • Relationship between the present document and the essential requirements of Directive 2016/2102
• Understand the concept of progressive enhancement.
  • A design philosophy that provides a baseline of essential content and functionality to as many users as possible, while delivering the best possible experience only to users of the most modern browsers that can run all the required code.