Troy Chaplin

mikecorkum

<a href="https://blockaccessibilitychecks.com/" rel="nofollow ugc">Block Accessibility Checks</a> is a comprehensive WordPress plugin that proactively prevents accessibility issues in your content before they reach your audience. Designed for the Gutenberg block editor, it provides real-time validation with a three-tier system that ensures your blocks, post meta fields, and overall document structure meet WCAG (Web Content Accessibility Guidelines) requirements.
Unlike reactive accessibility tools that scan published content, this plugin catches problems during the editing process—giving immediate visual feedback and preventing publication of content with critical accessibility errors. Content creators get clear guidance on what needs fixing, while developers can extend the system with custom checks for blocks, meta fields, and editor-level validation.
Whether you’re a content creator ensuring your posts are accessible, a developer building accessible blocks, or an organization maintaining compliance standards, Block Accessibility Checks provides the tools you need to create inclusive content effortlessly.
Features for Content Creators & Editors:
<ul>
<li>Real-time Visual Feedback – See accessibility issues instantly with color-coded borders (red for errors, yellow for warnings) around problematic blocks and detailed error messages in the block inspector panel</li>
<li>Smart Publishing Control – Critical accessibility errors prevent publishing until resolved, while warnings allow publication with user awareness</li>
<li>Comprehensive Block Coverage – Built-in validation for images, buttons, tables, headings, and galleries with clear guidance on how to fix issues</li>
<li>Document-Wide Validation – Advanced heading hierarchy checking prevents skipped heading levels and ensures proper content structure across your entire post</li>
<li>Title Validation – Ensures posts and pages have a title set for accessibility and SEO, validates in real-time as you type</li>
<li>Intelligent URL Validation – Real TLD validation using the Public Suffix List ensures only legitimate domains are accepted in button links</li>
<li>Configurable Settings – Control which checks are errors (prevent publishing), warnings (allow with notice), or disabled through an intuitive admin interface</li>
<li>Grouped Error Display – All accessibility issues shown at once in organized groups, eliminating the “fix one, see another” frustration</li>
<li>Works Everywhere – Validation runs in both the post editor and site editor (templates/template parts) with separate configurable settings</li>
</ul>
Features for Developers & Plugin Authors:
<ul>
<li>Three-Tier Validation API – Register custom checks for block attributes, post meta fields, and editor-level validation using comprehensive hooks and filters</li>
<li>JavaScript-Only Validation – All validation logic runs in JavaScript for real-time editor feedback without server round-trips</li>
<li>Automatic Settings Integration – External plugins automatically get their own settings pages under the Block Checks menu</li>
<li>External Plugin Support – Works seamlessly with custom blocks from third-party plugins and themes</li>
<li>Extensive Hook System – 20+ action and filter hooks for complete customization of registration, validation, and display behavior</li>
<li>Well-Documented API – Complete developer documentation with quick start guides and working code examples</li>
</ul>
How It Works:
The plugin provides immediate feedback as you edit content through a sophisticated three-tier validation system:
<ol>
<li>Block Validation – Validates individual block attributes in real-time as you type and edit</li>
<li>Meta Field Validation – Checks required post meta fields with automatic post locking when validation fails</li>
<li>Editor-Level Validation – Validates document-wide concerns like heading hierarchy that span across multiple blocks</li>
</ol>
When accessibility issues are detected, they are highlighted with visual indicators (red for errors, yellow for warnings) and detailed messages explain how to fix the problems. Critical errors prevent publishing until resolved, while warnings allow publication with user acknowledgment.
Built-in Accessibility Checks:
<ul>
<li>Button Blocks – Ensures buttons have descriptive text content and validates link destinations using real TLD validation (Public Suffix List)</li>
<li>Image Blocks – Requires alt text (unless marked decorative), validates alt text length (warns if exceeding 125 characters), prevents caption duplication, and detects non-descriptive patterns like “image of” or “photo123”</li>
<li>Table Blocks – Requires proper headers or captions for screen reader navigation</li>
<li>Heading Blocks – Validates proper heading hierarchy across entire document (prevents skipped levels), ensures appropriate first heading level (H2 recommended, H1 allowed with warnings), and provides configurable heading level restrictions (H1, H5, H6 can be disabled)</li>
<li>Gallery Blocks – Applies comprehensive image accessibility checks to all gallery items (alt text, length, patterns, caption duplication)</li>
<li>Post & Page Title Validation – Ensures posts and pages have a title set for accessibility and SEO, validates in real-time as users type, prevents publishing content without a title, configurable independently for posts and pages</li>
<li>Post Meta Fields – Validate required custom fields with real-time validation, automatic post locking for errors, and seamless integration with block validation system</li>
</ul>
Perfect For:
<ul>
<li>Government websites requiring WCAG compliance</li>
<li>Educational institutions with accessibility mandates</li>
<li>Businesses committed to inclusive web content</li>
<li>Developers building accessible WordPress themes and plugins</li>
<li>Content teams who want accessibility guidance built into their workflow</li>
</ul>
Developer Resources:
Extend the plugin with <a href="https://github.com/troychaplin/block-accessibility-checks/blob/main/docs/" rel="nofollow ugc">custom accessibility checks</a> using the comprehensive validation API. See the complete <a href="https://github.com/troychaplin/block-accessibility-checks/blob/main/docs/" rel="nofollow ugc">developer documentation</a> for quick start guides, API reference, code examples, and a <a href="https://github.com/troychaplin/block-check-integration-example" rel="nofollow ugc">working example plugin</a>.
<h3>Getting Involved</h3>
If you would like to get involved and contribute to the development of this plugin or view it’s source code you can find more information in the <a href="https://github.com/troychaplin/block-accessibility-checks" rel="nofollow ugc">plugins GitHub repo</a>.

Block Accessibility Checks

Prevent WCAG accessibility errors in your content with real-time validation for blocks, meta fields, and document structure.

Joe Dolson

<h4>How to use this plug-in:</h4>
If you install and activate this plug-in before installing Contact Form 7, the default form created by Contact Form 7 will be accessible. If you’ve already installed Contact Form 7, you’ll want to delete the default form and create new forms using the templates available in this plug-in.
<h4>Use Contact Form 7 with an accessible default form</h4>
This plug-in replaces the default template that Contact Form 7 automatically generates with an accessible equivalent of that form and adds a suite of additional basic form types that you can choose from to model your new forms.
The plug-in doesn’t change anything about forms that have already been built with Contact Form 7. The structure of Contact Form 7 is such that it isn’t possible for the plug-in to rewrite existing forms for improved accessibility, but it is possible to make sure that the base you have for starting a form is accessible.
Contact Form 7 is actually a very accessible plug-in. It has an accessible back-end, and if you create the right template, the front-end form will have great accessibility.
Since version 4.5, Contact Form 7 has included the label element; but the usage of them is limited, and isn’t the best possible method. This plug-in supplies a new default form that includes everything you need to make your default form accessible.
For more information about making Contact Form 7 accessible, read <a href="https://rianrietveld.com/2014/03/how-to-set-up-an-accessible-form-using-contact-form-7-in-wordpress/" rel="nofollow ugc">how to set up an accessible form using contact form 7</a>, by Rian Rietveld.

Contact Form 7: Accessible Defaults

Replaces the default Contact Form 7 form with an accessible equivalent and provides a suite of selectable base forms.

Block Accessibility Checks vs Contact Form 7: Accessible Defaults