Title: BarrierForge
Author: dsweeneyjr
Published: <strong>22 Eylül 2026</strong>
Last modified: 23 Eylül 2026

---

Eklentilerde ara

![](https://ps.w.org/barrierforge/assets/banner-772x250.png?rev=3708065)

![](https://ps.w.org/barrierforge/assets/icon-256x256.png?rev=3708065)

# BarrierForge

 [dsweeneyjr](https://profiles.wordpress.org/dsweeneyjr/) tarafından

[İndir](https://downloads.wordpress.org/plugin/barrierforge.1.0.5.zip)

 * [Detaylar](https://tr.wordpress.org/plugins/barrierforge/#description)
 * [Değerlendirmeler](https://tr.wordpress.org/plugins/barrierforge/#reviews)
 *  [Kurulum](https://tr.wordpress.org/plugins/barrierforge/#installation)
 * [Geliştirme](https://tr.wordpress.org/plugins/barrierforge/#developers)

 [Destek](https://wordpress.org/support/plugin/barrierforge/)

## Açıklama

BarrierForge scans the rendered front end of published WordPress content for common
accessibility barriers. Results appear in a filterable Fix Queue with severity, 
WCAG level, affected elements, page links, and suggested next steps.

BarrierForge includes:

 * Rendered-page scanning for up to 250 published public posts and pages.
 * Checks for missing image alt attributes, empty links and buttons, generic link
   text, positive tabindex values, skipped heading levels, text contrast, and small
   touch targets.
 * WCAG level and success-criterion references for each supported check.
 * Administrator-only links that locate and highlight affected elements on the front
   end.
 * Persistent automatic fixes for supported touch-target findings.
 * Opt-in sitewide enhancements for page language, a keyboard skip link, and visible
   keyboard focus.
 * Remediation history and progress reporting that distinguishes open and resolved
   findings.

Automated testing finds only some accessibility barriers. BarrierForge does not 
guarantee conformance with WCAG or any law, and it does not replace manual testing
or testing with people with disabilities.

## Yükleme

 1. Upload the BarrierForge ZIP from Plugins > Add New > Upload Plugin, or install 
    it from the WordPress.org Plugin Directory.
 2. Activate BarrierForge.
 3. Open BarrierForge in the WordPress admin menu.
 4. Select Scan rendered pages to create the first Fix Queue.
 5. Review each finding before applying a fix or changing site content.

## SSS

### Does BarrierForge make my site legally compliant?

No. Automated tools cannot establish legal compliance or complete WCAG conformance.
BarrierForge identifies a limited set of common barriers and helps administrators
review them.

### Does a scan change my content?

No. Scanning is read-only. Sitewide enhancements and automatic fixes are opt-in.
Supported touch-target fixes are stored in WordPress Additional CSS so the approved
work remains if BarrierForge is removed. Other enhancements require BarrierForge
to remain active.

### Does BarrierForge send site data to an external service?

No. Scans run between the WordPress administration screen and pages on the same 
site. Scan results, remediation records, settings, and local usage counters are 
stored in the site’s WordPress database and are not transmitted by BarrierForge 
to an external service.

### What data is removed when I delete the plugin?

Deleting BarrierForge through the WordPress Plugins screen removes scan results,
runtime enhancement settings, and local usage counters. Approved remediation records
and persistent touch-target CSS remain so deleting and reinstalling the plugin does
not discard completed accessibility work. Use Undo / reopen before deletion if you
want to remove an applied persistent fix.

### Why can a page or element fail to scan or highlight?

Security headers, authentication rules, caching, or dynamically generated markup
can prevent a rendered page from loading in the scanner or can change an element
after a scan. BarrierForge preserves existing findings when a page cannot be loaded
and reports when a saved element can no longer be found.

### Are all WCAG success criteria tested?

No. WCAG levels and criterion numbers identify the standards related to checks that
BarrierForge supports. Many WCAG requirements require human judgment and manual 
testing.

## İncelemeler

Bu eklenti için herhangi bir değerlendirme bulunmuyor.

## Katkıda Bulunanlar ve Geliştiriciler

“BarrierForge” açık kaynaklı yazılımdır. Aşağıdaki kişiler bu eklentiye katkıda 
bulunmuşlardır.

Katkıda bulunanlar

 *   [ dsweeneyjr ](https://profiles.wordpress.org/dsweeneyjr/)

[“BarrierForge” eklentisini dilinize çevirin.](https://translate.wordpress.org/projects/wp-plugins/barrierforge)

### Geliştirmeyle ilgilenir misiniz?

[Kodu görüntüleyin](https://plugins.trac.wordpress.org/browser/barrierforge/), [SVN deposuna](https://plugins.svn.wordpress.org/barrierforge/)
göz atın ya da [RSS](https://plugins.trac.wordpress.org/log/barrierforge/?limit=100&mode=stop_on_copy&format=rss)
ile [geliştirme günlüğüne](https://plugins.trac.wordpress.org/log/barrierforge/)
abone olun.

## Değişiklik Kaydı

#### 1.0.5

 * Made supported touch-target automatic fixes persistent through plugin deletion
   and reinstallation.
 * Preserved approved remediation records while still removing scan results, runtime
   settings, and usage data on uninstall.
 * Limited the Auto Fix action to fixes that BarrierForge can safely preserve without
   remaining active.

#### 1.0.4

 * Applied automatic fixes to legacy and fragment-style theme templates that omit
   the standard WordPress head and footer hooks.

#### 1.0.3

 * Applied automatic fixes from the page head with a guarded footer fallback for
   older or incomplete theme templates.

#### 1.0.2

 * Reapplied touch-target fixes after responsive layout changes and late-rendered
   controls.
 * Added a small sizing buffer and a longer verification window for reliable rescans.

#### 1.0.1

 * Prevented cached pre-fix pages from causing automatic fixes to reopen during 
   verification scans.
 * Reapplied automatic fixes immediately before rendered-page measurements.
 * Preserved active automatic fixes when a scan cannot yet verify them.

#### 1.0.0

 * Added rendered-page accessibility scanning and a filterable Fix Queue.
 * Added affected-element evidence and administrator-only front-end highlighting.
 * Added WCAG level, criterion, severity, and remediation progress reporting.
 * Added reversible sitewide enhancements and supported automatic fixes.
 * Added verified remediation history and safe handling for partial scan failures.
 * Added complete data removal on uninstall and documented local data handling.

## Meta

 *  Sürüm **1.0.5**
 *  Son güncelleme **20 saat önce**
 *  Etkin kurulumlar **10dan fazla**
 *  WordPress sürümü ** 6.2 veya üstü **
 *  Test edilen sürüm **7.1.2**
 *  PHP sürümü ** 7.4 veya üstü **
 *  Dil
 * [English (US)](https://wordpress.org/plugins/barrierforge/)
 * Etiketler
 * [accessibility](https://tr.wordpress.org/plugins/tags/accessibility/)[audit](https://tr.wordpress.org/plugins/tags/audit/)
   [testing](https://tr.wordpress.org/plugins/tags/testing/)[wcag](https://tr.wordpress.org/plugins/tags/wcag/)
 *  [Gelişmiş görünüm](https://tr.wordpress.org/plugins/barrierforge/advanced/)

## Puanlar

Henüz inceleme gönderilmedi.

[Değerlendirmeniz](https://wordpress.org/support/plugin/barrierforge/reviews/#new-post)

[Tüm değerlendirmeleri gör](https://wordpress.org/support/plugin/barrierforge/reviews/)

## Katkıda bulunanlar

 *   [ dsweeneyjr ](https://profiles.wordpress.org/dsweeneyjr/)

## Destek

Söyleyeceğiniz bir şey mi var? Yardım mı lazım?

 [Destek forumunu görüntüle](https://wordpress.org/support/plugin/barrierforge/)