Tag: DOJ-Series

Focus:

Shifting from remediation and archiving to a proactive, ongoing strategy for web accessibility.

Key Takeaways:

• Accessibility as Ongoing: Emphasize that compliance isn’t a one-time fix but a continuous effort.
• New Content First: Stress the importance of building accessibility in from the start for all new content.
• Training: Suggest training for content creators, web developers, and designers.
• Regular Audits: Recommend periodic accessibility audits and testing.
• Feedback Mechanisms: Encourage having an easy way for users to report accessibility issues on your site.
• Future-Proofing: Briefly touch on looking ahead to future WCAG versions (though the focus remains on 2.1 AA for now).
• Concluding Thought: Reiterate the positive impact of an accessible government website.

Focus:

Practical, actionable steps for implementing a compliant archiving strategy based on the best practices you provided earlier.

Key Takeaways:

• Dedicated Archive Section: Stress the importance of a separate, clearly labeled /archive section.
• Archived Page Notice: Provide the exact wording for the notice that should appear on archived pages.
• Content Curation: Advise on removing unnecessary or duplicate content before archiving.
• Search Engine Exclusion: Explain why and how to use noindex for archived pages.
• Accessibility Where It Counts: Reinforce the idea of remediating frequently accessed older documents even if they could be archived.
• Visual Aid (Optional): This post would be a great place for an example of what an archived page with the notice looks like.

Focus: This is where the “Archiving Web Content” information comes in, highlighting the relief this exception offers.

Key Takeaways:

• The Problem: Acknowledge the challenge of legacy content for state and local governments.
• The Solution: Introduce the DOJ’s specific exception for archived web content.
• The Four Conditions: Clearly outline the four conditions for content to qualify as “archived” (created before compliance date, reference only, clearly marked, unmodified).
• Initial Relief: Emphasize that not everything needs to be remediated, offering a sense of hope and clarity.

Focus: A slightly more technical (but still high-level) look at what WCAG 2.1 AA actually requires, without diving into every single success criterion.

Key Takeaways:

• The Four Principles (POUR): Explain Perceivable, Operable, Understandable, Robust in simple terms.
• Examples: Give concrete, easy-to-understand examples of what WCAG 2.1 AA means in practice (e.g., alt text for images, keyboard navigation, clear headings, sufficient color contrast).
• Beyond the Basics: Briefly touch on new additions in 2.1 over 2.0, such as mobile accessibility and touch targets, if relevant to your audience.
• Starting Point: Suggest an accessibility audit or review as a first step.

Focus: An introductory post announcing the new DOJ rules, why they matter, and the core message of WCAG 2.1 compliance.

Key Takeaways:

Call to Action: Encourage readers to understand what WCAG 2.1 AA entails.

Big Picture: The DOJ has updated its regulations under the ADA, making WCAG 2.1 AA the new standard for state and local government websites.

Why It Matters: This isn’t just about compliance; it’s about making government services truly accessible to everyone, including people with disabilities.

Key Date: Mention the general compliance dates (e.g., small vs. large entities) without getting into extreme detail, just to set expectations.