[
    {
        "role": "user",
        "content": "Is%20there%20an%20expiration%20date%20on%20the%20DHS%20Trsuted%20Tester%20Certifications%3F%20I%20just%20passed%20mine%20and%20was%20wondering%3F"
    },
    {
        "role": "assistant",
        "content": "No \u2014 the *DHS Trusted Tester* certification doesn\u2019t have a fixed expiration date **once you\u2019ve earned it**. ([legalclarity.org](https://legalclarity.org/dhs-trusted-tester-program-certification-and-requirements/?utm_source=openai))\n\nHowever, there are a few caveats to keep in mind:\n\n- Even though your certification is indefinite, it only remains useful while the version of the Trusted Tester methodology you were trained on is still accepted. When DHS updates the methodology (e.g. new test tools, updated standards like Section 508 or WCAG), you may need to recertify. ([legalclarity.org](https://legalclarity.org/dhs-trusted-tester-program-certification-and-requirements/?utm_source=openai))  \n- The methodology version matters. For example, V3/V4 test results are no longer accepted in DHS HQ or component governance processes after September 30, 2019. Existing TT V3 or V4 testers needed to move to V5. ([section508.gov](https://www.section508.gov/blog/DHS-Trusted-Tester-Program-Updates/?utm_source=openai))  \n\nIf you let me know which version your certification is (like V5.0, V5.1, etc.), I can check if DHS is considering that version still valid or maybe phasing it out."
    },
    {
        "role": "user",
        "content": "What%20WCAG%20Standard%20is%20the%20present%20DHS%20Trsuted%20Tster%20based%20on%3F%20I%20just%20pased%20the%205.1%20version%20of%20the%20test."
    },
    {
        "role": "assistant",
        "content": "Great question. If you\u2019ve just passed *Trusted Tester Version 5.1*, here\u2019s the most up-to-date information on which WCAG standard that version is based on:\n\n---\n\n## What WCAG standard does Trusted Tester 5.1 follow?\n\nTrusted Tester Version **5.1** (including recent sub-versions like 5.1.3) is aligned with *WCAG 2.0*, specifically **WCAG 2.0 Level A and AA**, through its incorporation into the **Revised Section 508** standards. ([section508coordinators.github.io](https://section508coordinators.github.io/SCRT/Resources/Trusted%20Tester%20Test%20Process%20v5.1.3.pdf?utm_source=openai))\n\n- The Trusted Tester 5.1 Conformance Test Process for Web explicitly states that it *\u201crelies principally on the rationale provided in Understanding WCAG 2.0: A guide to understanding and implementing Web Content Accessibility Guidelines 2.0.\u201d* ([section508coordinators.github.io](https://section508coordinators.github.io/SCRT/Resources/Trusted%20Tester%20Test%20Process%20v5.1.3.pdf?utm_source=openai))  \n- The Revised Section 508 Standards reference WCAG 2.0 Level A and AA. Trusted Tester 5.1 uses those WCAG 2.0 Success Criteria as its benchmark for web content. ([section508coordinators.github.io](https://section508coordinators.github.io/ACRT/Resources/Trusted%20Tester%20Test%20Process%20v5.1.3.pdf?utm_source=openai))\n\n---\n\n## What about WCAG 2.1 or WCAG 2.2?\n\nAlthough WCAG 2.1 and 2.2 introduce additional criteria (such as new requirements for mobile accessibility, low vision, target size, etc.), **Trusted Tester 5.1** does *not* yet formally include all of those as required baseline criteria.\n\n- The Baseline tests and Trusted Tester 5.1 cover WCAG 2.0 Level A & AA\u2014these are the \u201cmust-have\u201d requirements under the Revised 508 rules. ([ictbaseline.access-board.gov](https://ictbaseline.access-board.gov/web-baselines/?utm_source=openai))  \n- Although there is awareness of WCAG 2.1/2.2 and study materials exist showing differences/new success criteria, Trusted Tester\u2019s formal referenced standard is still WCAG 2.0. ([wai-wcag-act-rules.netlify.app](https://wai-wcag-act-rules.netlify.app/standards-guidelines/act/implementations/?utm_source=openai))\n\n---\n\n## TL;DR\n\nSince you passed Trusted Tester Version **5.1**, your certification is based on:\n\n- **WCAG 2.0**, Levels **A and AA**, under the Revised Section 508 standards  \n- Not yet WCAG 2.1 or 2.2 as baseline requirements (though those newer standards are increasingly discussed and included in study guides)\n\nIf you share the date/version (or any subversion like 5.1.3) you completed, I can check if there have been any recent changes or updates since then!"
    },
    {
        "role": "user",
        "content": "when%20was%202.0%20AA%20Adopted%2C%20what%20year%3F%20And%20I%27m%20looking%20at%20a%20job%20for%20WCAG%202.1%20AA%3F%20When%20was%20that%20adopted%3F%20And%20what%20are%20the%20sbustatial%20changes%3F%20or%20new%20features%3F"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s a summary of when WCAG 2.0 AA and WCAG 2.1 AA were adopted, and the substantive differences between them (especially the new success criteria added in 2.1).\n\n---\n\n## Adoption Dates\n\n- **WCAG 2.0** was published as a W3C Recommendation on **11 December 2008**, including all of the Level A, AA, and AAA criteria. ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/?utm_source=openai))  \n- **WCAG 2.1** was published on **5 June 2018**. ([w3.org](https://www.w3.org/TR/WCAG21/?utm_source=openai))\n\nSo WCAG 2.1 is the more recent version, which builds on WCAG 2.0 without removing existing criteria. ([w3.org](https://www.w3.org/TR/WCAG21/?utm_source=openai))\n\n---\n\n## What\u2019s New in WCAG 2.1 vs WCAG 2.0 (Key Updates & Success Criteria)\n\nWCAG 2.1 adds **17 new success criteria** designed to address gaps in WCAG 2.0. These focus mainly on accessibility for:\n\n- Mobile devices  \n- Low vision  \n- Cognitive or learning disabilities ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/?utm_source=openai))\n\nBelow are the main new criteria (especially those at **Level AA**) and what changed:\n\n---\n\n### New Level AA Success Criteria in WCAG 2.1\n\nHere are some of the most important additions at Level AA in WCAG 2.1:  \n\n| Criteria | What it requires / Why it matters |\n|---|--------------------------------------|\n| **1.3.4 Orientation (AA)** | Content must not be locked to portrait or landscape if orientation isn\u2019t essential. Helps users who rotate devices (tablet on wheelchair, etc.). ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/?utm_source=openai)) |\n| **1.3.5 Identify Input Purpose (AA)** | Form input fields include proper programmatic labels to allow browsers/assistive tech to identify the purpose (e.g., street address, date). Useful for autocomplete, keyboards, etc. ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/?utm_source=openai)) |\n| **1.4.10 Reflow (AA)** | Content should reflow (wrap) in simpler ways without needing horizontal scrolling, at certain zoom levels / widths. Important for low vision and mobile. ([w3.org](https://www.w3.org/TR/WCAG21/?utm_source=openai)) |\n| **1.4.11 Non-Text Contrast (AA)** | Ensures contrast between non-text elements (like icons, borders, controls) and adjacent colors meets minimum thresholds. ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/?utm_source=openai)) |\n| **1.4.12 Text Spacing (AA)** | User should be able to change spacing (line height, letter spacing, paragraph spacing, etc.) without loss of content/function. Helps readability. ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/?utm_source=openai)) |\n| **1.4.13 Content on Hover or Focus (AA)** | Content that appears on hover or focus should be dismissible, hoverable, and accessible via keyboard/focus. ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/?utm_source=openai)) |\n| **4.1.3 Status Messages (AA)** | Dynamic status updates (like error messages, live content updates) must be programmatically available to assistive technologies, unless they are trivial. ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/?utm_source=openai)) |\n\n---\n\n### Other Important Additions (Level A and AAA) to Note\n\n- **2.1.4 Character Key Shortcuts (A):** Keyboard shortcuts composed only of letters/numbers must be remappable or able to be turned off. ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/?utm_source=openai))  \n- **2.5.x Pointer Gestures / Gestures Cancellation / Label in Name / etc.:** These help with mobile and gesture-based interactions. ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/?utm_source=openai))  \n\n---\n\n## Why WCAG 2.1 Matters\n\n- It\u2019s **backwards compatible** with WCAG 2.0: everything you had under 2.0 is still there. ([w3.org](https://www.w3.org/TR/WCAG21/?utm_source=openai))  \n- Adds more focus on newer device types (mobile/tablets), and accessibility needs that weren\u2019t fully addressed before (low vision contrast, cognitive issues).  \n- Many laws, policies, and procurement standards have started referencing or mandating WCAG 2.1 AA rather than just 2.0 AA. E.g., the U.S. ADA\u2019s new \u201cWeb Rule\u201d for State & Local governments requires WCAG 2.1 AA conformance. ([ada.gov](https://www.ada.gov/resources/2024-03-08-web-rule/?utm_source=openai))  \n\n---\n\nIf you like, I can also pull up what\u2019s new in **WCAG 2.2** and whether Trusted Tester or DHS is planning to update to that next."
    },
    {
        "role": "user",
        "content": "when%20was%202.1%20AA%20adopted%2C%20what%20year%3F%20and%20is%20the%20modern%20WAS%20Certification%20based%20on%20which%20WCAG%3F"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s the latest information:\n\n---\n\n## WCAG 2.1 Adoption \u2014 Year Published\n\n- WCAG 2.1 was officially adopted **5 June 2018** as a W3C Recommendation. ([w3.org](https://www.w3.org/WAI/news/2018-06-05/wcag-21-is-a-web-standard/?utm_source=openai))  \n- It built on version 2.0 by adding a number of new success criteria (17 new ones) to better cover mobile device accessibility, low vision, cognitive and learning disabilities. ([w3.org](https://www.w3.org/WAI/standards-guidelines/wcag/?utm_source=openai))  \n\n---\n\n## IAAP WAS Certification \u2014 What WCAG Version It\u2019s Based On\n\nThe **IAAP Web Accessibility Specialist (WAS)** certification is based primarily on WCAG 2.1, and more recently updated to include WCAG 2.2. Key points:\n\n- As of their **June 2020 Body of Knowledge (BoK)**, the exam content covered **WCAG 1, WCAG 2.0, and WCAG 2.1**. ([wcag2.com](https://wcag2.com/wp-content/uploads/2022/09/IAAP-WAS-Body-of-Knowledge-BOK-2020-October.pdf?utm_source=openai))  \n- In late **2024**, the WAS BoK was updated (version 2.3) to include **WCAG 2.2**, making that the basis for the **March/April 2025** WAS exam session. ([linkedin.com](https://www.linkedin.com/posts/international-association-of-accessibility-professionals_professionalcertification-iaap-activity-7285702405248221184-jvMJ?utm_source=openai))  \n- So, if you're taking the WAS exam from **March/April 2025 onward** (at least in English), expect WCAG 2.2 to be part of the required knowledge. ([linkedin.com](https://www.linkedin.com/posts/international-association-of-accessibility-professionals_professionalcertification-iaap-activity-7285702405248221184-jvMJ?utm_source=openai))  \n\n---\n\nIf you want, I can contrast what\u2019s in WCAG 2.2 vs 2.1 too \u2014 so you can be sure what to focus on for the latest exams or job requirements."
    }
]