Drupal accessibility control map: what the platform covers and what your team owns
A checklist that maps all 55 WCAG 2.2 Level A and AA success criteria to the Drupal core feature, contributed module or configuration that meets each one. Use it to confirm what your university's Drupal platform covers by default, assign what your team owns, and log conformance for Section 508 and ADA Title II.
Key takeaways
- Building a Drupal site to WCAG 2.2 AA meets Section 508 (WCAG 2.0 AA) and the ADA Title II web rule (WCAG 2.1 AA) in one pass.
- The map covers 55 success criteria: 37 inside Section 508's standard, 12 added in WCAG 2.1 for Title II, and 6 new in WCAG 2.2.
- Drupal core targets WCAG 2.2 AA, so much of the map is covered by default. Conformance is usually lost in authored content and custom JavaScript components.
- Under the April 2026 extension, Title II compliance dates are 26 April 2027 for entities serving 50,000 or more people, and 26 April 2028 for smaller entities and special districts.
- Ask for an Accessibility Conformance Report (ACR) for the platform and for each contributed module in scope, and check which WCAG version it is written to.
Who this control map is for
- University accessibility leads who are accountable for conformance and need to separate what Drupal guarantees from what authors and developers maintain.
- Digital directors and web teams planning remediation ahead of the Title II compliance date.
- IT and procurement teams evaluating Drupal, a Drupal partner or a contributed module.
Teams usually reach for it before a Title II readiness review, an accessibility audit, a platform upgrade or an RFP.
Which accessibility standards apply to university websites?
Three layers apply, and each adds criteria to the one before. Build to WCAG 2.2 AA and you meet all three.
Layer | What it points to | Criteria added | Total |
|---|---|---|---|
Section 508 | WCAG 2.0 Level A and AA | 37 | 37 |
ADA Title II web rule (2024) | WCAG 2.1 Level AA | 12 | 49 |
WCAG 2.2, the current W3C standard | WCAG 2.2 Level A and AA | 6 | 55 |
The Title II rule covers state and local government entities, including public colleges and universities. Entities serving a total population of 50,000 or more must comply by 26 April 2027. Smaller entities and special district governments have until 26 April 2028.
What does Drupal cover for accessibility by default?
Drupal covers most of WCAG 2.2 AA out of the box. Its accessibility coding standards target WCAG 2.2 AA for public pages and ATAG 2.0 for authoring tools, and core runs axe-core in its automated tests. Drupal CMS adds a WCAG AA front-end theme, required alt text, semantic HTML, and Editoria11y, a content accessibility checker for editors.
That baseline still needs testing on your own templates. Conformance is most often lost where the platform can't guarantee it: the content authors add every day, and custom JavaScript components such as menus, sliders, maps and virtual tours.
How is the control map organized?
The map lists every WCAG 2.2 Level A and AA criterion under its principle, with its level, whether it sits inside Section 508, and the Drupal control that meets it.
WCAG principle | Criteria | In Section 508 | Added in WCAG 2.1 or 2.2 |
|---|---|---|---|
Perceivable | 20 | 14 | 6 |
Operable | 20 | 12 | 8 |
Understandable | 13 | 10 | 3 |
Robust | 2 | 1 | 1 |
Total | 55 | 37 | 18 |
Each control names the Drupal piece responsible: a core feature such as Inline Form Errors, a contributed module such as Webform or Metatag, a theme setting, or an editorial policy.
Which WCAG 2.2 criteria are new, and how does Drupal meet them?
WCAG 2.2 adds six Level A and AA criteria. Neither Section 508 nor the Title II rule requires them yet, but they are the current target layer. This is how the map handles each one.
Criterion | Level | Drupal-level control |
|---|---|---|
2.4.11 Focus Not Obscured (Minimum) | AA | Sticky headers, cookie banners and chat or accessibility widgets must not fully cover the focused element. Adjust scroll-margin and z-index in the theme. |
2.5.7 Dragging Movements | AA | Front-end reorder, slider and drag-upload components need a single-pointer alternative. Admin drag-and-drop (tabledrag, Layout Builder) already offers keyboard reordering. |
2.5.8 Target Size (Minimum) | AA | Design-system tokens give interactive targets at least 24 by 24 CSS pixels. Check dense utility menus and icon-only buttons. |
3.2.6 Consistent Help | A | Place the help, contact or chat block in the same theme region on every template. |
3.3.7 Redundant Entry | A | In multistep Webforms, prefill or carry forward data already entered instead of asking for it again. |
3.3.8 Accessible Authentication (Minimum) | AA | Allow password managers and paste on login. Replace puzzle CAPTCHAs with Honeypot or another accessible method on portal and SSO flows. |
How do you audit a Drupal site for accessibility?
Run four passes on representative templates: the home page, a content page, a Webform, search and the login flow. Automated tools catch only part of the issues, so three of the four passes are manual.
- Automated scan. Run a checker such as axe-core across the templates to catch machine-detectable issues.
- Keyboard and screen reader. Tab through each template, then test with at least two screen reader and browser pairings.
- Authored-content sample. Check real pages with Editoria11y for alt text, headings and link text, where conformance is most often lost.
- Log against the map. Record each criterion as pass, fail or not applicable, with the page tested, the owner and a date.
For the remediation sequence after the audit, see How to meet WCAG 2.2 AA on Drupal: a university checklist.
What's in the full control map?
The PDF is the working version: print it or share it, then log your platform against it.
- All 55 criteria with their level, Section 508 status and Drupal-level control
- A checkbox per criterion to log pass, fail or not applicable
- The four-pass method in full, including the screen reader and browser pairings to test
- What to request in an ACR for the platform and for each contributed module
Vardot's view
The criteria that slip between audits are the ones authors touch daily: alt text, headings, link text, captions and forms, plus any custom JavaScript component. Drupal Canvas, the visual page builder in Drupal CMS, adds a new watch point: pages built from a component library are only as accessible as the components and theme behind them.
The lasting fix is governance, not one-time remediation: accessible patterns built into the component library, and Editoria11y running site-wide.
Vardot is a Top Tier Drupal Certified Partner (previously Diamond) with 200+ platforms launched, including Georgetown University. UNHCR's Drupal 11 multisite, built by Vardot for 44 country operations in 31 languages, scores 97/100 for accessibility.
Want a second reviewer on your accessibility plan?
Bring your last audit or your template list. In a 20-minute call, a Vardot architect will review which criteria your Drupal platform already covers, which your team owns, and where conformance is most likely to slip.