1. The Hook: The Color Contrast Trap
Slide: A "sleek" modern Drupal hero banner with white text over a light-colored image.
The Issue (UX): Ask the audience: "Who can read this?" Explain that users with low vision, color blindness, or even someone outside in bright sunlight are effectively blocked.
The Solution: Use a contrast checker to hit the 4.5:1 ratio.
The Result: Inclusion! Your "modern" design now works for 100% of your users, not just 80%.
2. The Basics: What is WCAG?
Definition: Keep it simple. WCAG (Web Content Accessibility Guidelines) is the "Manual for the Internet" to ensure people with disabilities can use it.
The Levels: Briefly mentioning that AA is the standard for most business and government sites.
3. The Reality Check: New US Federal Law (2024)
The Update: The DOJ Title II update (April 2024).
The Requirement: All state and local government websites and apps must meet WCAG 2.1 AA.
The Deadline: Most agencies must comply by April 2026. This makes accessibility a "must-have" for Drupal agencies.
4. The Core: POUR Fundamentals
Accessibility works on four pillars (POUR)
Perceivable, Operable, Understandable, and Robust
I'll explain all the rules for eg:
Perceivable ➔ Rule 1.3.2 (Meaningful Sequence)
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
The Drupal Problem: You use a Drupal View to show three columns. You use CSS "Flexbox" to visually move the 3rd item to the 1st position because it looks better.
The User Experience: A screen reader user hears the 3rd item first, then the 1st, then the 2nd. If these are "Step 1, Step 2, Step 3," the user is completely confused.
The Drupal Solution: Always order your fields or blocks in the Drupal UI (Manage Display) in the exact order you want them read. Use CSS only for styling, not for re-ordering core information.
5. Q&A Session
Invite the audience to share a specific Drupal module or "pain point" they’ve encountered.
6. Thank You & Resources
