{"id":360771,"date":"2026-09-01T02:18:17","date_gmt":"2026-09-01T02:18:17","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/widewalk-accessibility-toolbar\/"},"modified":"2026-09-25T01:06:40","modified_gmt":"2026-09-25T01:06:40","slug":"widewalk","status":"publish","type":"plugin","link":"https:\/\/en-au.wordpress.org\/plugins\/widewalk\/","author":20319283,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.9","stable_tag":"1.0.9","tested":"7.1.2","requires":"6.2","requires_php":"7.4","requires_plugins":null,"header_name":"Widewalk \u2013 Accessibility Toolbar","header_author":"WalletUp","header_description":"The web, wide open. Twelve reading controls your visitors set for themselves \u2014 bigger text, looser lines, stronger links, calmer colour. One switch to turn on, and it works on any theme.","assets_banners_color":"4b5569","last_updated":"2026-09-25 01:06:40","external_support_url":"","external_repository_url":"","donate_link":"https:\/\/walletup.app\/","header_plugin_uri":"https:\/\/walletup.app\/widewalk","header_author_uri":"https:\/\/walletup.app\/","rating":0,"author_block_rating":0,"active_installs":100,"downloads":1824,"num_ratings":0,"support_threads":1,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"walletup","date":"2026-09-01 04:27:47","revision":3675247},"1.0.1":{"tag":"1.0.1","author":"walletup","date":"2026-09-02 05:20:20","revision":3677186},"1.0.2":{"tag":"1.0.2","author":"walletup","date":"2026-09-02 05:29:16","revision":3677203},"1.0.3":{"tag":"1.0.3","author":"walletup","date":"2026-09-02 16:10:22","revision":3678336},"1.0.4":{"tag":"1.0.4","author":"walletup","date":"2026-09-02 21:11:36","revision":3678682},"1.0.5":{"tag":"1.0.5","author":"walletup","date":"2026-09-03 03:37:14","revision":3678907},"1.0.6":{"tag":"1.0.6","author":"walletup","date":"2026-09-03 23:52:56","revision":3680497},"1.0.7":{"tag":"1.0.7","author":"walletup","date":"2026-09-11 14:38:35","revision":3691585},"1.0.9":{"tag":"1.0.9","author":"walletup","date":"2026-09-25 01:06:40","revision":3712206}},"upgrade_notice":{"1.0.9":"<p>A lighter touch on the media, images and motion a visitor controls, and richer hooks for your theme.<\/p>","1.0.8":"<p>Your published content, read against thirteen WCAG criteria, and a way to work through what it finds.<\/p>","1.0.6":"<p>Themes can now hold their own slideshows still when a visitor pauses animation.<\/p>","1.0.5":"<p>Pausing animation now covers film and sound too, and tooltips follow the pointer.<\/p>","1.0.4":"<p>The settings screen now checks whether the panel reached a page you built\nyourself, and on servers that allow it, offers to add the line for you.<\/p>","1.0.3":"<p>More dependable cache clearing after a settings change.<\/p>","1.0.2":"<p>Only one panel is shown when a theme already provides the same one.<\/p>","1.0.1":"<p>Bigger text now works on every theme, and the panel can be placed on a front end\nWordPress does not render with a single script tag.<\/p>","1.0.0":"<p>First release. Switch it on under Settings \u2192 Widewalk, then publish your\naccessibility statement from the same screen.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3675159,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3675159,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3678906,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3675159,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3675159,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{"blueprint.json":{"filename":"blueprint.json","revision":3712206,"resolution":false,"location":"assets","locale":"","contents":"{\"$schema\":\"https:\\\/\\\/playground.wordpress.net\\\/blueprint-schema.json\",\"landingPage\":\"\\\/\",\"preferredVersions\":{\"php\":\"8.2\",\"wp\":\"latest\"},\"features\":{\"networking\":true},\"steps\":[{\"step\":\"login\",\"username\":\"admin\",\"password\":\"password\"},{\"step\":\"installPlugin\",\"pluginData\":{\"resource\":\"wordpress.org\\\/plugins\",\"slug\":\"widewalk\"},\"options\":{\"activate\":true}},{\"step\":\"runPHP\",\"code\":\"<?php require '\\\/wordpress\\\/wp-load.php'; update_option( 'widewalk_settings', array( 'enabled' => true, 'position' => 'right' ) ); ?>\"}]}"}},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1","1.0.2","1.0.3","1.0.4","1.0.5","1.0.6","1.0.7","1.0.9"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3675159,"resolution":"1","location":"assets","locale":"","width":680,"height":1906},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3675159,"resolution":"2","location":"assets","locale":"","width":872,"height":2360},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3675159,"resolution":"3","location":"assets","locale":"","width":680,"height":2164},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3678680,"resolution":"4","location":"assets","locale":"","width":2400,"height":4612}},"screenshots":{"1":"The panel open on a live site, with several controls set to different steps.","2":"The panel enlarged, for anybody who finds the standard size hard to press.","3":"Moving the panel to the other corner, or hiding it for this visit.","4":"The settings screen. Every control has its own switch, and the accessibility statement is written from here."}},"plugin_section":[],"plugin_tags":[1447,1953,226238,240895,1956],"plugin_category":[34],"plugin_contributors":[208762],"plugin_business_model":[],"class_list":["post-360771","plugin","type-plugin","status-publish","hentry","plugin_tags-a11y","plugin_tags-accessibility","plugin_tags-accessibility-toolbar","plugin_tags-accessibility-widget","plugin_tags-wcag","plugin_category-accessibility","plugin_contributors-walletup","plugin_committers-walletup"],"banners":{"banner":"https:\/\/ps.w.org\/widewalk\/assets\/banner-772x250.png?rev=3675159","banner_2x":"https:\/\/ps.w.org\/widewalk\/assets\/banner-1544x500.png?rev=3675159","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/widewalk\/assets\/icon.svg?rev=3678906","icon":"https:\/\/ps.w.org\/widewalk\/assets\/icon.svg?rev=3678906","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/widewalk\/assets\/screenshot-1.png?rev=3675159","caption":"The panel open on a live site, with several controls set to different steps."},{"src":"https:\/\/ps.w.org\/widewalk\/assets\/screenshot-2.png?rev=3675159","caption":"The panel enlarged, for anybody who finds the standard size hard to press."},{"src":"https:\/\/ps.w.org\/widewalk\/assets\/screenshot-3.png?rev=3675159","caption":"Moving the panel to the other corner, or hiding it for this visit."},{"src":"https:\/\/ps.w.org\/widewalk\/assets\/screenshot-4.png?rev=3678680","caption":"The settings screen. Every control has its own switch, and the accessibility statement is written from here."}],"raw_content":"<!--section=description-->\n<p>Widewalk puts a small button in the corner of your site. A visitor presses it and\na panel opens with the settings they need in order to read you: bigger text, more\nair between the lines, letters further apart, links they can actually pick out of\na paragraph, a calmer palette, a pointer large enough to find. Whatever they\nchoose is kept in their own browser. Nobody else's view of your site moves an inch.<\/p>\n\n<p>You switch it on once. It works with the theme you already have, on the front end\nyou already have, and it asks nothing of your visitors in return.<\/p>\n\n<p><strong>What you decide<\/strong><\/p>\n\n<p>All twelve controls have their own switch, so you offer the ones that suit your\nsite and leave the rest off. You choose which bottom corner the button sits in.\nYou publish your accessibility statement from the same screen, in a long or a\nshort version. That is the whole settings page, and there is nothing to\nconfigure before it works.<\/p>\n\n<p>The name comes from pavements built wide enough for everyone at the same time:\nthe wheelchair, the pushchair, the delivery trolley, and the people walking\nalongside them. Widen the path rather than build a second one round the back.<\/p>\n\n<p><strong>What a visitor can change<\/strong><\/p>\n\n<p>Each control steps through its settings as it is pressed, and the button says\nwhich step it is on. \"Line Height (1.75x)\" or \"Low Saturation\" tells a visitor\nwhere they are without making them guess.<\/p>\n\n<ul>\n<li>Bigger Text, at 110%, 125% and 150%<\/li>\n<li>Line Height, at 1.5x, 1.75x and 2x<\/li>\n<li>Letter and word spacing, from light through to heavy<\/li>\n<li>Invert Colors, then High Contrast<\/li>\n<li>Saturation: low, high, or monochrome<\/li>\n<li>Highlight Links, then Boxed Links<\/li>\n<li>Dyslexia Friendly type<\/li>\n<li>Big Cursor, then Bigger Cursor<\/li>\n<li>Pause animations<\/li>\n<li>Hide images<\/li>\n<li>Text alignment: left, centre, right<\/li>\n<li>Tooltips, which read out the descriptions a screen reader gets and a mouse user never sees<\/li>\n<\/ul>\n\n<p>Twelve of them, and each has its own switch on the settings screen. Offer the\nones that suit your site and leave the rest off.<\/p>\n\n<p><strong>This is not an overlay<\/strong><\/p>\n\n<p>Worth saying plainly, because that word has earned its reputation. Widewalk does\nnot scan your pages, does not rewrite them for everybody, and makes no claim\nabout your legal compliance. Those three promises are what the overlay industry\nsells, and no plugin is in a position to keep them.<\/p>\n\n<p>Accessibility lives in your own markup. Your headings, your alt text, your colour\ncontrast, your link text, your forms. Five minutes with any plugin will not\nchange what is underneath.<\/p>\n\n<p>What Widewalk does is smaller and it is true. It hands a visitor the settings\nthey would otherwise have to fight your stylesheet for, which is real help to\nsomebody with low vision, or dyslexia, or a migraine coming on, or a phone held\nup in bright sunlight. Do the underlying work as well. This sits beside it.<\/p>\n\n<p><strong>It writes your accessibility statement<\/strong><\/p>\n\n<p>Any site that offers a panel like this ought to say what it is aiming for and how\nto report a problem. Most plugins tell you to go away and write one. Widewalk\nwrites it for you, out of what you have actually switched on, and shows you the\nwhole thing before a word of it is published.<\/p>\n\n<p>Choose the complete version, which follows the structure the W3C recommends, or\nthe short one if your site is small. You supply two things: an address where\nsomebody can report a barrier, and the number of working days you will take to\nreply. Promise something you can keep.<\/p>\n\n<p>Publish it and you have an ordinary WordPress page, yours to edit like any other.\nWidewalk will not overwrite it later. The wording claims partial conformance and\nnothing beyond that, because a plugin cannot certify a site it has never seen.<\/p>\n\n<p><strong>Built to survive your theme<\/strong><\/p>\n\n<p>The panel renders inside a shadow root. Your stylesheet cannot reach into it, and\nits stylesheet cannot leak out into your pages. It has been measured against a\ntheme written for the sole purpose of breaking it: global button rules marked\n    !important, a forced box model, oversized icons, a page claiming the highest\nstacking order there is. It came through without a mark.<\/p>\n\n<p>Block themes, classic themes, page builders. It mounts on <code>wp_footer<\/code>, which\nevery theme fires.<\/p>\n\n<p><strong>Works past WordPress, too<\/strong><\/p>\n\n<p>Plenty of sites keep WordPress for the admin and build their public pages in\nplain PHP, in React, or as static files. Nothing on those pages runs a WordPress\nfooter, so the panel never arrives. Add one line to your own instead:<\/p>\n\n<pre><code>&lt;script src=\"\/wp-content\/plugins\/widewalk\/assets\/embed.js\" defer&gt;&lt;\/script&gt;\n<\/code><\/pre>\n\n<p>Same panel, same controls, the settings you already chose. Nothing else to set up.<\/p>\n\n<p><strong>Light, and quiet about it<\/strong><\/p>\n\n<ul>\n<li>About 7 KB gzipped covers everything a visitor downloads. One stylesheet, one small script, no framework, no jQuery.<\/li>\n<li>Switch the panel off and nothing at all is added to your pages.<\/li>\n<li>No account, no API key, no third-party service, no fonts pulled from somebody else's server.<\/li>\n<li>Nothing is tracked about your visitors and no cookie is set. Preferences sit in local storage on the visitor's own device, under a single key.<\/li>\n<li>One request can leave, and only if you press the button that sends it. It carries counts, never content. See External services below.<\/li>\n<\/ul>\n\n<p><strong>Made to the standard it talks about<\/strong><\/p>\n\n<ul>\n<li>Every control works from the keyboard alone, with a focus outline you can see.<\/li>\n<li>The panel is a labelled dialog. Focus stays inside it while it is open, and returns where it came from when it closes.<\/li>\n<li>Changes are announced to screen readers as they happen.<\/li>\n<li>Motion stops when a visitor's device has asked for less of it.<\/li>\n<li>Text and background inside the panel meet WCAG 2.2 AA contrast.<\/li>\n<\/ul>\n\n<p><strong>Who installs it<\/strong><\/p>\n\n<p>Sites whose readers are not all twenty-five with good eyes and a large monitor.\nCharities, galleries, schools, clinics, councils, artists, shops, small\nnewsrooms. Anywhere that would rather be read than admired.<\/p>\n\n<h3>External services<\/h3>\n\n<p>Widewalk works fully without contacting anything. One optional feature sends a\nshort note to WalletUp, and only after you press the button that sends it.<\/p>\n\n<p><strong>What it is.<\/strong> A dated record of your content report's three counts, kept once a\nweek off your own server, so you can show the accessibility work you are doing,\nwatch the counts fall over time, and still have the record after a reinstall.<\/p>\n\n<p><strong>What is sent, and when.<\/strong> Once at the moment you press the button, then once a\nweek while it stays switched on. Every field is shown on the settings screen,\nfilled in with your own values, before you press anything:<\/p>\n\n<ul>\n<li>site: your site address<\/li>\n<li>token: a random name for this site's record, made on your site, meaning nothing on its own<\/li>\n<li>plugin: the plugin name and version<\/li>\n<li>wp: your WordPress version<\/li>\n<li>php: your PHP version<\/li>\n<li>locale: your site language<\/li>\n<li>issues: how many findings the content report counted, as three numbers: critical, serious, moderate<\/li>\n<\/ul>\n\n<p>No page content, no post or page titles, no email address, no user account, no\nIP-based profile, and nothing about anyone visiting your site.<\/p>\n\n<p>When a site connects for the first time, WalletUp fetches one public address on\nit, \/wp-json\/widewalk\/v1\/registry, to confirm the note really came from that\nsite and not from someone naming it. That address answers with a yes and a\ncheck value; it carries no content and no settings.<\/p>\n\n<p>To show you your weeks, the settings screen asks for them back with site, token\nand the word history, at most once an hour.<\/p>\n\n<p>Pressing stop sends site, token and the word leave, deletes your numbers there,\nand removes everything the plugin kept about it here. Nothing else is sent at\nany time.<\/p>\n\n<p><strong>Where it goes.<\/strong> https:\/\/walletup.app\/wp-json\/widewalk-registry\/v1\/site , run by\nWalletUp. Terms: https:\/\/walletup.app\/terms\/ . Privacy: https:\/\/walletup.app\/privacy\/<\/p>\n\n<h3>For theme developers<\/h3>\n\n<p>Widewalk tells the page about every preference, so a theme can respond in ways the toolbar cannot know about, such as swapping a hero video for a still, reflowing a grid, or replacing a decorative image with its caption.<\/p>\n\n<p>Attributes on the html element (a stable contract):<\/p>\n\n<ul>\n<li>data-a11y-animations, data-a11y-images, data-a11y-text, data-a11y-invert, data-a11y-saturation, data-a11y-lineheight, data-a11y-spacing, data-a11y-align, data-a11y-links, data-a11y-dyslexia, data-a11y-cursor and data-a11y-tooltips each hold the active level as a number, and are absent when the control is off.<\/li>\n<li>data-a11y-os-reduce is \"1\" when the visitor's system asks for reduced motion.<\/li>\n<\/ul>\n\n<p>Events on document:<\/p>\n\n<ul>\n<li>widewalk:change fires once at load with detail.state (every control and its level), and again on each change with detail.key and detail.level.<\/li>\n<li>widewalk:motion fires when animations are paused or resumed with detail.paused, kept for compatibility.<\/li>\n<\/ul>\n\n<p>Mark any element the toolbar should leave alone with data-widewalk-keep. Images, media and animations inside it stay untouched when images are hidden or motion is paused.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install from Plugins \u2192 Add New, or upload the folder to <code>\/wp-content\/plugins\/<\/code>.<\/li>\n<li>Activate it.<\/li>\n<li>Open Settings \u2192 Widewalk and switch the panel on.<\/li>\n<li>While you are there, publish your accessibility statement from one of the two templates. Read it through afterwards and make it true of your site.<\/li>\n<\/ol>\n\n<p>That is the whole setup. There is nothing to configure before it works.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20this%20make%20my%20site%20ada%20or%20wcag%20compliant%3F\"><h3>Does this make my site ADA or WCAG compliant?<\/h3><\/dt>\n<dd><p>No, and treat anything that says otherwise with suspicion. Conformance rests on\nyour own markup: headings, alt text, contrast, link text, forms, error messages.\nWidewalk helps a visitor read what you have written. It cannot repair what sits\nunderneath. Use it alongside the real work.<\/p><\/dd>\n<dt id=\"is%20widewalk%20an%20accessibility%20overlay%3F\"><h3>Is Widewalk an accessibility overlay?<\/h3><\/dt>\n<dd><p>No. An overlay scans your page and rewrites it for every visitor, usually with a\npromise of automatic compliance attached. Widewalk changes nothing until a\nvisitor asks it to, changes it only for that visitor, and promises nothing about\nyour legal position.<\/p><\/dd>\n<dt id=\"my%20site%27s%20front%20end%20isn%27t%20wordpress.%20can%20i%20still%20use%20it%3F\"><h3>My site's front end isn't WordPress. Can I still use it?<\/h3><\/dt>\n<dd><p>Yes. Plenty of sites keep WordPress for the admin and build their public pages\nin plain PHP, in React, or as static files. Nothing on those pages runs a\nWordPress footer, so add one line to your own:<\/p>\n\n<pre><code>&lt;script src=\"\/wp-content\/plugins\/widewalk\/assets\/embed.js\" defer&gt;&lt;\/script&gt;\n<\/code><\/pre>\n\n<p>That is the whole integration. It reads the settings you chose in the admin and\nmounts the same panel, with the same controls.<\/p>\n\n<p>Settings has the line ready to copy, and a box where you can give it one of your\nown pages. It will fetch that page and tell you whether the line arrived, so you\nare not left guessing.<\/p><\/dd>\n<dt id=\"will%20it%20work%20with%20my%20theme%3F\"><h3>Will it work with my theme?<\/h3><\/dt>\n<dd><p>Yes. The panel lives inside a shadow root, so your theme's rules do not reach it\nand its rules do not escape into your pages. It has been tested against popular\nthemes and against a stylesheet built on purpose to wreck it. Block themes,\nclassic themes and page builders are all fine.<\/p><\/dd>\n<dt id=\"will%20it%20slow%20my%20site%20down%3F\"><h3>Will it slow my site down?<\/h3><\/dt>\n<dd><p>Everything a visitor downloads comes to roughly 7 KB gzipped: one stylesheet, one\nsmall script, no framework, no jQuery. With the panel switched off, nothing is\nadded to your pages at all.<\/p><\/dd>\n<dt id=\"does%20it%20collect%20anything%20about%20my%20visitors%3F\"><h3>Does it collect anything about my visitors?<\/h3><\/dt>\n<dd><p>Nothing. No tracking, no analytics, no account, no cookie. Preferences are held\nin local storage in the visitor's own browser. Nothing about a visitor is read,\nkept or sent, and that does not change if you connect the site: the note that\ntravels then is about the site, never about anyone reading it.<\/p><\/dd>\n<dt id=\"is%20it%20gdpr-friendly%3F\"><h3>Is it GDPR-friendly?<\/h3><\/dt>\n<dd><p>There is nothing about your visitors to disclose: nothing is collected about\nthem, nothing is stored and nothing is shared. Preferences never leave their\ndevice. If you connect the site, what travels is your own site address and a\ncount of findings, which is yours to decide on and yours to undo.<\/p><\/dd>\n<dt id=\"can%20i%20choose%20which%20controls%20appear%3F\"><h3>Can I choose which controls appear?<\/h3><\/dt>\n<dd><p>Yes. All twelve have their own switch. Offer what suits your site and leave the\nrest off.<\/p><\/dd>\n<dt id=\"do%20i%20really%20need%20an%20accessibility%20statement%3F\"><h3>Do I really need an accessibility statement?<\/h3><\/dt>\n<dd><p>If you are offering a panel like this, you should say what you are aiming for,\nwhat you know still falls short, and how somebody tells you about a barrier.\nPublic bodies in many countries are required to publish one. Widewalk writes the\npage in two lengths and links the panel to it.<\/p><\/dd>\n<dt id=\"does%20it%20work%20on%20phones%3F\"><h3>Does it work on phones?<\/h3><\/dt>\n<dd><p>Yes. The panel is built for touch as much as for mouse and keyboard, and the\ncontrols are large enough to press without aiming.<\/p><\/dd>\n<dt id=\"can%20somebody%20use%20it%20with%20a%20keyboard%2C%20or%20a%20screen%20reader%3F\"><h3>Can somebody use it with a keyboard, or a screen reader?<\/h3><\/dt>\n<dd><p>Yes. Every control is reachable by keyboard with a visible focus outline. The\npanel is a labelled dialog, focus is held inside it and returned when it closes,\nand each change is announced.<\/p><\/dd>\n<dt id=\"pausing%20animation%20does%20not%20stop%20my%20slideshow.%20why%3F\"><h3>Pausing animation does not stop my slideshow. Why?<\/h3><\/dt>\n<dd><p>A slideshow that moves on a timer is a script, and a plugin cannot safely reach\ninto another script's timers. Widewalk stops what it can reach: animation and\ntransitions from your stylesheet, video and sound, and moving SVG.<\/p>\n\n<p>For the rest it tells your page, and the page can stop itself. Two lines in your\ntheme are enough. Widewalk puts <code>data-a11y-animations<\/code> on the <code>html<\/code> element,\nand fires a <code>widewalk:motion<\/code> event on the document:<\/p>\n\n<pre><code>if (document.documentElement.hasAttribute('data-a11y-animations')) return;\n<\/code><\/pre>\n\n<p>Put that at the top of whatever advances your slides, and it will hold still\nwhile a visitor has asked it to.<\/p><\/dd>\n<dt id=\"does%20it%20respect%20%22reduce%20motion%22%3F\"><h3>Does it respect \"reduce motion\"?<\/h3><\/dt>\n<dd><p>Yes. When a visitor's device asks for less motion, the panel stops animating.\nThey can also pause animation across your whole site from inside the panel.<\/p><\/dd>\n<dt id=\"can%20i%20move%20the%20button%3F\"><h3>Can I move the button?<\/h3><\/dt>\n<dd><p>Yes, to either bottom corner, from the settings screen. A visitor can move it\nthemselves as well, if it is sitting over something they need.<\/p><\/dd>\n<dt id=\"i%20already%20have%20an%20accessibility%20toolbar.%20can%20i%20run%20both%3F\"><h3>I already have an accessibility toolbar. Can I run both?<\/h3><\/dt>\n<dd><p>Please don't. Two panels arguing over the same page is worse than either one on\nits own. Pick the one you prefer and turn the other off.<\/p><\/dd>\n<dt id=\"does%20it%20need%20javascript%3F\"><h3>Does it need JavaScript?<\/h3><\/dt>\n<dd><p>Yes. The panel is a set of controls, and without a script there is nothing for\nthem to control. Where scripting is unavailable, nothing is added to the page.<\/p><\/dd>\n<dt id=\"is%20it%20available%20in%20my%20language%3F\"><h3>Is it available in my language?<\/h3><\/dt>\n<dd><p>Every string is translatable, and translations arrive through\ntranslate.wordpress.org. Contributions are very welcome.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.9<\/h4>\n\n<ul>\n<li>Improved: video and audio a visitor starts themselves keep playing while animations are paused.<\/li>\n<li>Improved: script-driven animations settle into their finished state instead of holding partway.<\/li>\n<li>Improved: turning images off keeps interface icons, embedded frames, form controls and your logo in view; only pictures are hidden.<\/li>\n<li>New: the toolbar button shows a count while any preference is active, and the pause and hide controls start fresh on a new visit.<\/li>\n<li>New: a widewalk:change event and documented data-a11y-* attributes let a theme respond to every control; mark anything to leave alone with data-widewalk-keep.<\/li>\n<li>Improved: the toolbar reflects your system's reduced-motion setting.<\/li>\n<li>Improved: the optional script for pages WordPress does not build can be scoped to a path.<\/li>\n<\/ul>\n\n<h4>1.0.8<\/h4>\n\n<ul>\n<li>New: a content report reads your published pages against thirteen WCAG criteria. Each finding is one line with a count; open it for the pages concerned and what to do.<\/li>\n<li>New: work through the findings one kind at a time, ask for that one check again, and watch the count fall. Findings the report no longer finds can be taken out of your statement.<\/li>\n<li>New: keep the report's three counts with WalletUp once a week as a dated record of your work, off your own server, and watch them fall over time. Off until you switch it on, and every field is shown before anything is sent.<\/li>\n<li>New: the statement records another way to reach anything still out of reach.<\/li>\n<li>Improved: the report says what it cannot decide, so nothing is claimed that a person has not checked.<\/li>\n<\/ul>\n\n<h4>1.0.7<\/h4>\n\n<ul>\n<li>New: the accessibility statement records the standard you aim for, what it covers, how it was assessed, when you last looked at it, anything left out of it, and the points you know fall short. That last list stays live on the page, so publishing once is enough.<\/li>\n<li>Improved: the panel sizes itself to the screen it is on, and its heading and close button stay within reach while you move through the controls.<\/li>\n<li>Improved: caches are refreshed whenever the plugin's files change, and page optimisers are asked to leave the panel's script whole.<\/li>\n<\/ul>\n\n<h4>1.0.6<\/h4>\n\n<ul>\n<li>New: a <code>widewalk:motion<\/code> event, and the <code>data-a11y-animations<\/code> marker on the page, so a slideshow or anything else driven by a script can hold still while a visitor has asked for stillness. Two lines in a theme are enough, and the FAQ shows them.<\/li>\n<\/ul>\n\n<h4>1.0.5<\/h4>\n\n<ul>\n<li>Improved: pausing animation reaches video, sound and moving SVG, as well as the animation a stylesheet controls. Anything a visitor had already paused is left alone, and everything resumes when the control is switched off again.<\/li>\n<li>Improved: tooltips appear beside the pointer, and only for the thing being pointed at. A label that repeats words already on the screen stays quiet.<\/li>\n<li>Improved: both of those hold from the moment a page opens, not only after the control is pressed again.<\/li>\n<\/ul>\n\n<h4>1.0.4<\/h4>\n\n<ul>\n<li>New: a card on the settings screen for sites whose public pages WordPress does not build. It shows the one line to paste, with a button to copy it, and will fetch a page of yours and tell you whether the line arrived.<\/li>\n<li>New: on a server that can do it, Widewalk will offer to add that line for you. It shows exactly what it would write before you decide, keeps your file first, checks your front page afterwards, and puts everything back untouched unless the page comes back whole with the line in it. You can undo it at any time, and pasting by hand always works instead.<\/li>\n<\/ul>\n\n<h4>1.0.3<\/h4>\n\n<ul>\n<li>Improved: clearing the page cache after a change is more dependable, using each caching plugin's own published method.<\/li>\n<\/ul>\n\n<h4>1.0.2<\/h4>\n\n<ul>\n<li>Improved: where a theme or kit already puts this same panel on the page, the plugin stands aside rather than adding a second one.<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>New: the panel can be added to pages WordPress does not render. A site whose front end is plain PHP, React or static files adds one script tag and gets the same panel, with the same settings.<\/li>\n<li>Improved: bigger text now reaches every theme. Sizes are set on the text itself, so a theme that measures in fixed pixels grows with the rest.<\/li>\n<li>Improved: switching the panel on, or changing what it offers, clears the page cache so visitors see it straight away.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>New: a reading panel on every page, with twelve controls a visitor sets for themselves. Text size, line height, letter spacing, contrast, saturation, link marks, dyslexia-friendly type, cursor size, animation, images, alignment and tooltips.<\/li>\n<li>New: each control steps through its settings and names the one in force, so a visitor always knows where they are.<\/li>\n<li>New: every control can be offered or withheld from a single settings screen.<\/li>\n<li>New: writes your accessibility statement in a complete or a short version, out of what you have switched on, and links the panel to it.<\/li>\n<li>New: the panel can sit in either bottom corner, and a visitor can move it themselves.<\/li>\n<li>Isolated inside a shadow root, so it survives any theme and disturbs none of it.<\/li>\n<li>Keyboard operable throughout, focus held and returned, changes announced, motion dropped when the visitor asks for less.<\/li>\n<li>About 7 KB gzipped on the front end, and nothing at all when the panel is off.<\/li>\n<li>No tracking, no cookies, no account, and no request leaves unless you send it.<\/li>\n<\/ul>","raw_excerpt":"Reading controls your visitors set for themselves: bigger text, looser lines, stronger links, calmer colour. Any theme. Not an overlay.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/360771","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=360771"}],"author":[{"embeddable":true,"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/walletup"}],"wp:attachment":[{"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=360771"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=360771"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=360771"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=360771"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=360771"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/en-au.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=360771"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}