{"id":396468,"date":"2026-11-02T16:18:01","date_gmt":"2026-11-02T16:18:01","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/ariaccess-accessibility-checker-fixes-display-panel\/"},"modified":"2026-11-02T18:30:13","modified_gmt":"2026-11-02T18:30:13","slug":"ariaccess","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/ariaccess\/","author":23589628,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.1.0","stable_tag":"1.1.0","tested":"7.1.4","requires":"6.5","requires_php":"7.4","requires_plugins":null,"header_name":"AriAccess \u2013 Accessibility Checker, Fixes & Display Panel","header_author":"AriHub","header_description":"Find and fix real accessibility problems: a content checker mapped to WCAG and the Norwegian rules, an admin page scanner, code-level fixes, an accessible visitor display panel, an alt text manager and an accessibility statement generator. No overlays, no tracking, no compliance claims.","assets_banners_color":"121f2d","last_updated":"2026-11-02 18:30:13","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/www.arihub.com\/ariaccess\/","header_author_uri":"https:\/\/www.arihub.com\/","rating":0,"author_block_rating":0,"active_installs":0,"downloads":39,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"arihub","date":"2026-11-02 16:17:51","revision":3780253},"1.1.0":{"tag":"1.1.0","author":"arihub","date":"2026-11-02 18:30:13","revision":3780489}},"upgrade_notice":{"1.1.0":"<p>A clearer workflow: a Dashboard with the next step, one Issues list for content and page checks, dismissals with a reason and undo, and a &quot;Check key pages&quot; button.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3780252,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3780252,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3780252,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3780252,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3780252,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3780488,"resolution":"1","location":"assets","locale":"","width":1280,"height":960},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3780488,"resolution":"2","location":"assets","locale":"","width":1280,"height":960},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3780252,"resolution":"3","location":"assets","locale":"","width":2560,"height":1600},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3780252,"resolution":"4","location":"assets","locale":"","width":2560,"height":1600},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3780252,"resolution":"5","location":"assets","locale":"","width":1170,"height":2532},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3780488,"resolution":"6","location":"assets","locale":"","width":1280,"height":960}},"screenshots":{"1":"Dashboard: the next step, open problems by severity, your six steps and the pages to fix first.","2":"Issues from both checks in one list, each mapped to WCAG and marked as required by the standard you chose, with where it is and how to fix it.","3":"The page check on a live page, with the problem highlighted on the page.","4":"The visitor display panel with the Low vision profile turned on.","5":"The display panel on a phone.","6":"The accessibility statement form (Norwegian or English)."}},"plugin_section":[],"plugin_tags":[1447,1953,209467,290343,1956],"plugin_category":[34],"plugin_contributors":[289004],"plugin_business_model":[],"class_list":["post-396468","plugin","type-plugin","status-publish","hentry","plugin_tags-a11y","plugin_tags-accessibility","plugin_tags-accessibility-checker","plugin_tags-universal-design","plugin_tags-wcag","plugin_category-accessibility","plugin_contributors-arihub","plugin_committers-arihub"],"banners":{"banner":"https:\/\/ps.w.org\/ariaccess\/assets\/banner-772x250.png?rev=3780252","banner_2x":"https:\/\/ps.w.org\/ariaccess\/assets\/banner-1544x500.png?rev=3780252","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/ariaccess\/assets\/icon.svg?rev=3780252","icon":"https:\/\/ps.w.org\/ariaccess\/assets\/icon.svg?rev=3780252","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/ariaccess\/assets\/screenshot-1.png?rev=3780488","caption":"Dashboard: the next step, open problems by severity, your six steps and the pages to fix first."},{"src":"https:\/\/ps.w.org\/ariaccess\/assets\/screenshot-2.png?rev=3780488","caption":"Issues from both checks in one list, each mapped to WCAG and marked as required by the standard you chose, with where it is and how to fix it."},{"src":"https:\/\/ps.w.org\/ariaccess\/assets\/screenshot-3.png?rev=3780252","caption":"The page check on a live page, with the problem highlighted on the page."},{"src":"https:\/\/ps.w.org\/ariaccess\/assets\/screenshot-4.png?rev=3780252","caption":"The visitor display panel with the Low vision profile turned on."},{"src":"https:\/\/ps.w.org\/ariaccess\/assets\/screenshot-5.png?rev=3780252","caption":"The display panel on a phone."},{"src":"https:\/\/ps.w.org\/ariaccess\/assets\/screenshot-6.png?rev=3780488","caption":"The accessibility statement form (Norwegian or English)."}],"raw_content":"<!--section=description-->\n<p>AriAccess helps you make your WordPress site work for everyone: people who use a screen reader, a keyboard, a magnifier, or who have dyslexia, low vision or a sensitivity to motion.<\/p>\n\n<p>It does this the honest way. <strong>No plugin can make a site \"compliant\" on its own<\/strong>, and AriAccess never claims to. Automated checks find roughly a third of accessibility problems. AriAccess finds what can be found automatically and shows you exactly where each problem is and how to fix it at the source. It fixes what can be fixed safely in code and helps you write an accessibility statement.<\/p>\n\n<h4>Content checker<\/h4>\n\n<ul>\n<li>Checks every post and page when you save it, or the whole site in one click.<\/li>\n<li>26 checks, including missing or poor alt text, empty and vague links (\"click here\", \"les mer\", \"l\u00e4s mer\", \"lue lis\u00e4\u00e4\"), skipped and empty headings, tables without headers, frames without titles, autoplaying media, missing captions, unlabelled form fields, nameless buttons, duplicate ids and positive tabindex.<\/li>\n<li><strong>Colour contrast inside your content<\/strong>, including block colours from your theme's palette.<\/li>\n<li>Each issue is mapped to its WCAG success criterion and marked as required or good practice for the standard you choose:\n\n<ul>\n<li>Norway, private sector (35 WCAG 2.0 criteria)<\/li>\n<li>Norway, public sector (47 WCAG 2.1 criteria)<\/li>\n<li>WCAG 2.1 AA \/ EN 301 549 (EU)<\/li>\n<li>WCAG 2.2 AA<\/li>\n<\/ul><\/li>\n<li>Results in the editor sidebar, a column in your post lists and one Issues list for the whole site, grouped by problem or by page, with filters, search and paging.<\/li>\n<li>Three plain severities everywhere: Must fix, Should review, Check by hand.<\/li>\n<li>Dismiss a problem with a reason (not a problem, fixed another way, accepted for now). AriAccess records who and when, and you can restore it at any time.<\/li>\n<\/ul>\n\n<h4>Page checker<\/h4>\n\n<ul>\n<li>\"Check accessibility\" in the admin bar runs axe-core, the open-source engine used by accessibility professionals, on the live page in your own browser.<\/li>\n<li>Sees what a content check cannot: menus, headers, footers, theme colours, landmarks.<\/li>\n<li>Highlights each problem on the page and saves it to the Issues list, with where it is and how to fix it.<\/li>\n<li>\"Check key pages\" checks your home page, menu pages, newest post and statement one after another, from the admin.<\/li>\n<li>A problem both checks find on the same page is shown once.<\/li>\n<li>Nothing is sent to any outside service.<\/li>\n<\/ul>\n\n<h4>Fixes<\/h4>\n\n<p>Code-level repairs for common theme and plugin gaps, each one switchable:<\/p>\n\n<ul>\n<li>Skip-to-content link (only if your theme has none)<\/li>\n<li>Clear keyboard focus outline<\/li>\n<li>Pinch zoom allowed on phones<\/li>\n<li>\"Opens in a new tab\" warnings, or same-tab links<\/li>\n<li>Post titles added to \"Read more\" links for screen readers<\/li>\n<li>Accessible names for unlabelled search and form fields<\/li>\n<li>Media Library alt text used where older posts have none<\/li>\n<li>Positive tabindex removed<\/li>\n<li>Page language and direction added if missing<\/li>\n<li>Empty searches explained<\/li>\n<li>Redundant title attributes removed<\/li>\n<li>Optional: underlined links, respect for \"reduce motion\"<\/li>\n<\/ul>\n\n<h4>Display panel for visitors<\/h4>\n\n<p>A panel visitors can use to adjust the site for themselves: text size, line and letter spacing, a readable font (Atkinson Hyperlegible), a dyslexia-friendly font (OpenDyslexic), left-aligned text, dark and light high contrast, greyscale, soft colours, highlighted links and headings, stopped animations (including GIFs and videos), hidden images, big cursor, reading guide, reading mask, strong focus outline and read-aloud on click. Five quick profiles combine these.<\/p>\n\n<ul>\n<li>Built to be used with a keyboard and screen readers: real buttons, <code>aria-pressed<\/code> states, Escape to close, focus returned, announcements for changes.<\/li>\n<li>Tested with axe-core: the panel itself has no violations, in light and dark mode.<\/li>\n<li>Choices are stored only in the visitor's browser. <strong>No cookies, no tracking, no requests to other servers.<\/strong> Fonts are bundled.<\/li>\n<li>Norwegian (bokm\u00e5l and nynorsk), Swedish, Danish and Finnish translations of all visitor-facing text are being added through translate.wordpress.org.<\/li>\n<li>Place your own button anywhere with <code>[ariaccess_button]<\/code>.<\/li>\n<\/ul>\n\n<h4>Accessibility statement<\/h4>\n\n<p>Answer a few questions and AriAccess writes your accessibility statement in Norwegian or English as a normal page you can edit. One click adds the problems AriAccess found to Known problems, ready to reword for visitors. The statement includes known problems, a contact address, reply time and how to complain to Uutilsynet. Public bodies can link their uustatus.no statement. The display panel links the statement and a \"Report a problem\" email.<\/p>\n\n<h4>Alt text manager<\/h4>\n\n<p>See every Media Library image without alt text and fill them in on one screen. A \"Missing alt text\" filter is added to the Media Library.<\/p>\n\n<h4>Privacy<\/h4>\n\n<p>AriAccess sets no cookies, collects no visitor data and makes no external requests. Check results are stored in your own database.<\/p>\n\n<h4>Third-party code<\/h4>\n\n<ul>\n<li>axe-core 4.14.0 by Deque Systems, MPL-2.0, used for the page check (loaded only for logged-in editors). Source: https:\/\/github.com\/dequelabs\/axe-core<\/li>\n<li>Atkinson Hyperlegible by the Braille Institute, SIL Open Font License 1.1. Source: https:\/\/github.com\/googlefonts\/atkinson-hyperlegible<\/li>\n<li>OpenDyslexic by Abbie Gonzalez, SIL Open Font License 1.1. Source: https:\/\/github.com\/antijingoist\/opendyslexic<\/li>\n<\/ul>\n\n<p>All are bundled with the plugin. AriAccess makes no requests to external services.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>Go to <strong>AriAccess \u2192 Dashboard<\/strong>. The next step is always at the top.<\/li>\n<li>Press <strong>Check all content<\/strong>, then <strong>Check key pages<\/strong> (home page, menu pages, newest post).<\/li>\n<li>Open <strong>Issues<\/strong> and work through the must-fix problems, one kind at a time or one page at a time.<\/li>\n<li>Do the five tests by hand on the Dashboard, then fill in <strong>Statement<\/strong> and publish it.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"will%20this%20make%20my%20site%20compliant%20with%20the%20law%3F\"><h3>Will this make my site compliant with the law?<\/h3><\/dt>\n<dd><p>No plugin can do that on its own, and you should be wary of any that claims to. Accessibility depends on your theme, your content and how people can use your forms and menus. AriAccess finds and fixes a large share of common problems and shows you the rest. Finish with a manual test using the keyboard and a screen reader; the Tools tab has a short checklist.<\/p><\/dd>\n<dt id=\"is%20the%20display%20panel%20an%20%22overlay%22%3F\"><h3>Is the display panel an \"overlay\"?<\/h3><\/dt>\n<dd><p>No. 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. Problems are fixed by the Fixes and by you, at the source.<\/p><\/dd>\n<dt id=\"which%20rules%20apply%20in%20norway%3F\"><h3>Which rules apply in Norway?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"does%20it%20slow%20my%20site%20down%3F\"><h3>Does it slow my site down?<\/h3><\/dt>\n<dd><p>Visitors load one small CSS file and two small deferred scripts. The fonts load only when a visitor turns them on. axe-core loads only for logged-in editors who run a page check.<\/p><\/dd>\n<dt id=\"can%20i%20turn%20off%20the%20display%20panel%20and%20only%20use%20the%20checker%3F\"><h3>Can I turn off the display panel and only use the checker?<\/h3><\/dt>\n<dd><p>Yes. Untick \"Show the display panel button\" under Display panel. Every fix can also be switched off.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>New Dashboard: the next step at the top, six steps from choosing a standard to publishing the statement, the pages to fix first, and how the number of must-fix problems changes over time. No score.<\/li>\n<li>New Issues screen: problems from the content check and the page check in one list, grouped by problem or by page, with filters, search and paging. A problem both checks find is shown once.<\/li>\n<li>One set of names everywhere: Must fix, Should review, Check by hand. Counts on every screen and in the menu badge now agree.<\/li>\n<li>Dismiss with a reason (not a problem, fixed another way, accepted for now); AriAccess records who and when. A Dismissed view lets you restore anything, and Undo works straight away.<\/li>\n<li>Check key pages: checks the home page, menu pages, the newest post and the statement one after another, without leaving the admin. Page checks now keep where each problem is and how to fix it.<\/li>\n<li>Statement: \"Add the problems AriAccess found\" fills in Known problems; a warning appears if you choose \"Fully\" while must-fix problems are open; the uustatus.no field shows only for public bodies; the standard comes from Settings.<\/li>\n<li>Images: a \"Looks like a file name\" view, and save one image at a time.<\/li>\n<li>Settings and Tools are one screen; the contrast checker takes hex codes.<\/li>\n<li>Each screen has its own page title and heading; results are announced after a check.<\/li>\n<li>Uninstall on multisite cleans every site that chose to delete its data.<\/li>\n<li>Page-check problems now have plain-language names (\"List contains items that are not list items\"), with axe's own wording kept under \"Why\".<\/li>\n<li>A page that is trashed, deleted or unpublished leaves the list, together with its page-check results.<\/li>\n<li>Page checks table counts now match the Issues screen for the same page.<\/li>\n<li>Fixed: key-page checks timed out when the admin and the site use different addresses (for example www and non-www).<\/li>\n<li>Fixed: undoing a Restore now keeps the original dismiss reason, so accepted problems stay in the statement.<\/li>\n<li>Saving a post no longer recounts every problem on the site; the menu badge is recounted once on the next admin page.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First release: content checker (26 checks, palette-aware contrast), axe-core page checker, 13 fixes, display panel with 19 options and 5 profiles, accessibility statement generator (Norwegian\/English), alt text manager.<\/li>\n<\/ul>","raw_excerpt":"Find and fix real accessibility problems: content and page checks, code fixes, a keyboard-friendly display panel and a statement. No overlay.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/396468","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=396468"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/arihub"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=396468"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=396468"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=396468"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=396468"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=396468"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=396468"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}