The plugin uses WordPress roles and optional per-feature capability maps. Administrators always have full access and can delegate features to other roles where the UI allows it.
Defaults (summary)
| Feature | Default | Configurable |
|---|---|---|
| Dashboard | edit_posts | No |
| AI Alt Text | Administrators only | Yes |
| Accessibility Test — single runs | Administrator, Editor | Yes |
| Accessibility Test — batch | Administrators only | Yes |
| Test others’ content | Administrators only | Yes |
| Delete results | Administrators only | Yes |
| Analytics (Accessibility Test) | manage_options (admins) | No |
| AI Image Review | manage_options; Premium or Agency plan | No |
| All settings screens | manage_options (admins) | No |
Where to configure
Permission blocks live inside each feature’s Settings tab. Only administrators can change them.
AI Alt Text
Path: WP Admin → EZZE WCAG Pro → AI Alt Text → Settings → Permissions for AI generation
- Who may generate: choose which roles see the “Generate AI Alt Text” control in Media
- Eligible roles: only roles with upload_files (e.g. Administrator, Editor, Author)
- Note: Administrators always retain access
Accessibility Test
Path: WP Admin → EZZE WCAG Pro → Accessibility Test → Settings → Permissions
- Allow single tests: who can run one-off tests (default: Administrator, Editor)
- Allow batch tests: who can start batch runs (default: administrators)
- Test other users’ content: who may queue items they do not own (default: administrators)
- Delete results: who may remove stored scores (default: administrators)
Eligible roles: roles with edit_posts appear in the picker.
Note: Administrators always keep full test permissions.
Examples
Example 1: Editorial team, least privilege
- Editors: single tests on their drafts
- Authors: single tests on their posts
- Batch: administrators only (heavy workload)
- Others’ content: administrators only
- Delete results: administrators only
Why: authors improve content without batch or cross-user access.
Example 2: Dev-led site
- Editors (web team): single + batch + others’ content + delete
- Authors: single tests for owned content only
Why: builders can audit the whole site; marketing stays scoped.
Example 3: Delegate AI Alt Text
Enable generation for Editors and Authors so Media workflows do not bottleneck on one admin.
Remember: each generation consumes plan quota.
Example 4: Locked-down
Only administrators use AI Alt Text and Accessibility Test; other roles get neither—central control over quota usage.
Example 5: Trusted editors
Grant editors everything except mass delete; authors stay on single tests for owned posts.
Configuration tips
- Least privilege: grant the minimum that matches workflow—reduces accidental quota burn
- Batch carefully: reserve for trusted roles
- AI features: AI Alt Text and AI Explanation & Fix count toward limits; AI Image Review already requires Premium/Agency + admin
- Protect history: limit “delete results” to admins when audits must be retained
- Iterate: start strict, relax as needed
- Document: note the policy for future site owners
Technical notes
- Checks run server-side (authoritative) with client-side gating for UX
- Built-in roles (administrator, editor, author, …) and custom roles work when capabilities exist
- Stored in options such as wcag_alt_text_settings, wcag_lighthouse_settings
- Capabilities are not cached—evaluated per request