AriAccess · Accessibility for WordPress

Find and fix real accessibility problems, honestly.

AriAccess checks your content and your live pages, maps every issue to WCAG and to Norway's rules, fixes what can be fixed safely in code, and helps you write your accessibility statement. No overlay, no tracking, and it never calls your site “compliant”.

v1.0.0WordPress 6.5+PHP 7.4+GPLv2 or later

26content checks on every post and page
13switchable code fixes for common theme gaps
19display options for visitors, in 5 profiles
0requests to outside services
What it does

A checker, fixes and a panel, in one plugin

For people who use a screen reader, a keyboard or a magnifier, and for people with dyslexia, low vision or a sensitivity to motion.

Content checker

26 checks on every post and page when you save, or on the whole site in one click: alt text, vague links, headings, tables, frames, media, form labels, button names, duplicate ids and more.

Contrast that knows your theme

Checks colour contrast inside your content, including block colours from your theme's palette.

Page checker

“Check accessibility” in the admin bar runs axe-core on the live page in your own browser, so it also sees menus, headers, footers and theme colours. Problems are highlighted on the page.

13 fixes

Switchable code fixes for common theme gaps: skip link, focus outline, pinch zoom, new-tab warnings, “Read more” context, names for unlabelled fields, page language and more.

Display panel for visitors

19 options and 5 profiles: text size and spacing, readable and dyslexia-friendly fonts, contrast modes, stopped animations, reading guide, read-aloud and more. Keyboard and screen reader friendly.

Accessibility statement

Answer a few questions and AriAccess writes your statement in Norwegian or English as a page you can edit, with known problems, a contact address and how to complain to Uutilsynet.

Alt text manager

Every Media Library image without alt text on one screen, plus a “Missing alt text” filter in the Media Library.

Results where you work

Issues in the editor sidebar, a column in your post lists and a site-wide report. Dismiss what you have checked by hand.

Nothing leaves your site

No cookies, no visitor data and no requests to outside services. Fonts and axe-core are bundled, and results stay in your own database.

Norway's rules built in

Each issue marked required or good practice

Choose the standard that applies to you, and every report follows it. Each issue links to its WCAG success criterion.

Standards you can choose

Norway, private sector: 35 WCAG 2.0 criteriaNorway, public sector: 47 WCAG 2.1 criteriaWCAG 2.1 AA / EN 301 549WCAG 2.2 AA

Knows Nordic words

“click here”“les mer”“läs mer”“lue lisää”

Vague link texts are found in English and the Nordic languages.

Setup

Five steps to your first report

  1. Install and activate AriAccess.
  2. Go to AriAccess → Overview and press Check all content.
  3. Press Check the home page to run the page checker.
  4. Work through the issues, starting with those marked “Problem”.
  5. Fill in Statement and publish it.
Your own button

Open the display panel from anywhere

[ariaccess_button]

Or keep only the checker: the panel button and every fix can be switched off.

Be clear about the limits

What AriAccess does not do

It does not make your site “compliant” by itself

No plugin can. Automated checks find roughly a third of accessibility problems. AriAccess finds what can be found automatically, shows you exactly where each problem is, and fixes what is safe to fix in code. Finish with a manual test using the keyboard and a screen reader.

The panel is not an overlay

Overlays claim to repair a site automatically for assistive technology users and often get in their way. AriAccess's panel only changes how the page looks for visitors who choose to use it, like the zoom and contrast settings in a browser.

AriAccess Pro

Planned, for agencies and public bodies

None of this is available yet, and nothing in the free version will move to Pro.

Audit history

Every check kept, with trends over time and what you fixed since last month.

Client reports

PDF and CSV exports, white-label, and scheduled emails.

Whole-site page checks

Every page from your sitemap checked on a schedule, to catch theme-level problems everywhere.

Alt text with your own AI key

Suggested alt text in bulk and on upload, in Norwegian too, with keys and images under your control.

Free on WordPress.org

In your WordPress dashboard, go to Plugins → Add New, search for AriAccess, then click Install Now and Activate. Updates arrive the same way as for any other plugin.

Questions

Frequently asked

Will AriAccess make my site compliant with the law?

No plugin can do that on its own, and AriAccess never claims to. Automated checks find roughly a third of accessibility problems. AriAccess finds what can be found automatically, fixes what is safe to fix in code and shows you the rest. Finish with a manual test: the Tools tab has a short checklist. Get started

Which rules apply in Norway?

Private businesses must meet 35 success criteria from WCAG 2.0, levels A and AA. Public bodies must meet 47 criteria from WCAG 2.1 and publish an accessibility statement. Choose your standard under Settings and the reports follow it. Choose the standard to measure against

Is the display panel an overlay?

No. The panel only changes how the page looks for visitors who choose to use it, like the zoom and contrast settings in a browser. It does not try to repair your site for screen reader users. Problems are fixed by the Fixes and by you, at the source.

Does it slow my site down?

Visitors load one small stylesheet and two small deferred scripts. The fonts load only when a visitor turns them on, and axe-core loads only for logged-in editors who run a page check. The content check runs in the admin when you save a post or press “Check all content”, not when visitors load a page.

Can I use only the checker?

Yes. Untick “Show the display panel button” under Display panel, and switch off any fix you do not want. Settings reference

Does it work with my theme or page builder?

The content check reads each post the way WordPress outputs it, so it covers blocks, the classic editor and anything else that appears in the post content. Headers, footers, menus and theme templates are outside the post content. For those, run the page check, which checks the whole page as it appears in your browser. Check a live page

Where are the visitor's panel choices stored?

Only in the visitor's own browser. No cookies are set and nothing is sent anywhere.

What does AriAccess store, and what happens when I delete it?

Settings, statement answers, page check results (the latest 200 pages) and each post's check result and dismissed issues are kept in your own database. By default they stay when you delete the plugin. Tick “Delete all AriAccess data when the plugin is deleted” under Settings to remove them. Your statement page and alt text always stay. Stored data

Does it work on multisite?

Yes, site by site. Each site has its own settings, reports and statement, and there are no network-wide settings. When the plugin is deleted, the data clean-up runs for the main site only.

Which languages does AriAccess speak?

The plugin is in English, with Norwegian Bokmål and Nynorsk, Swedish, Danish and Finnish translations of the visitor-facing text on the way through translate.wordpress.org. The accessibility statement can be written in Norwegian Bokmål or English, and the vague link check knows phrases in English, the Nordic languages and German.