WordPress

Dendrila Accessibility Assistant

An editorial accessibility assistant that identifies potential issues and guides fixes, without claiming automated checks are compliance certification.

What is it for?

For someone publishing with WordPress: identify images without useful alternative text, poorly structured headings and confusing buttons, then get guidance on fixes. It is an editorial assistant, not a WCAG or RGAA certification.

What the alpha already does

Local checks of saved content: missing image alternatives, alternative text resembling filenames, empty or skipped heading levels, links or buttons with no apparent accessible name, and unlabeled fields.
Conservative, read-only inspection of Elementor Image, Text, Heading and Button widgets, Divi 4 Image modules, and exploratory detection of Divi 5 blocks. Builder data and page content are not rewritten.
A dashboard for manually scanning up to the 100 most recent published public posts, plus an editor panel based on the last saved version. Errors and uninspected content are reported separately.
Media-library guidance: new images may be flagged for completion and reviewed as informative (useful alternative text) or decorative (intentionally empty alternative). Existing media is not blocked and can be reviewed progressively.
Local operation, with no third-party service, no automatic page edits and no additional WordPress role.

Proposed improvements — PR #4

A GitHub pull request adds WordPress Plugin Check, prepares the creation of an installable alpha ZIP for testing, and makes incomplete scans explicit when HTML findings exceed 70, Elementor Text widgets are oversized, or structures are too deep. These proposed changes must not be confused with the main branch until merged.

PHP 8.1 and 8.3 checks passed on that branch, including regression tests. This is not proof of a successful real WordPress installation or acceptance on WordPress.org.

Testing and limitations

Version 0.1.0-alpha: for pilot sites only. The installable ZIP is produced by a manual GitHub Actions workflow; its availability and installation on a real WordPress site still need verification. Gutenberg, Elementor, Divi 4/5, media-library, keyboard and screen-reader tests remain necessary.

“100%” only means the scan job completed, even if some content failed or was skipped. Automated checks do not cover all RGAA/WCAG criteria, themes, rendered interactions and contrast, or all dynamic pages. This is neither a full accessibility audit nor a certification.