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":3675162,"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":{},"all_blocks":[],"tagged_versions":["1.0.0"],"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":3675247,"resolution":"4","location":"assets","locale":"","width":2400,"height":3746}},"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=3675162","icon":"https:\/\/ps.w.org\/widewalk\/assets\/icon.svg?rev=3675162","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=3675247","caption":"The settings screen. Every control has its own switch, and the accessibility statement is written from here."}],"raw_content":"\n
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
You switch it on once. It works with the theme you already have.<\/p>\n\n
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
What a visitor can change<\/strong><\/p>\n\n 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 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 This is not an overlay<\/strong><\/p>\n\n 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 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 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 It writes your accessibility statement<\/strong><\/p>\n\n 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 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 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 Built to survive your theme<\/strong><\/p>\n\n 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 Block themes, classic themes, page builders. It mounts on Light, and quiet about it<\/strong><\/p>\n\n Made to the standard it talks about<\/strong><\/p>\n\n Who installs it<\/strong><\/p>\n\n 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\n That is the whole setup. There is nothing to configure before it works.<\/p>\n\n\n 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 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 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 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 Nothing. No tracking, no analytics, no account, no cookie. Preferences are held\nin local storage in the visitor's own browser. The plugin makes no outbound\nrequest of any kind, so nothing about your site or your readers goes anywhere.<\/p><\/dd>\n There is nothing to disclose, since nothing is collected, nothing is stored on\nyour server and nothing is shared. Preferences never leave the visitor's device.<\/p><\/dd>\n Yes. All twelve have their own switch. Offer what suits your site and leave the\nrest off.<\/p><\/dd>\n 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 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 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 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\n
wp_footer<\/code>, which\nevery theme fires.<\/p>\n\n\n
\n
\n
\/wp-content\/plugins\/<\/code>.<\/li>\n\n
Does this make my site ADA or WCAG compliant?<\/h3><\/dt>\n
Is Widewalk an accessibility overlay?<\/h3><\/dt>\n
Will it work with my theme?<\/h3><\/dt>\n
Will it slow my site down?<\/h3><\/dt>\n
Does it collect anything about my visitors?<\/h3><\/dt>\n
Is it GDPR-friendly?<\/h3><\/dt>\n
Can I choose which controls appear?<\/h3><\/dt>\n
Do I really need an accessibility statement?<\/h3><\/dt>\n
Does it work on phones?<\/h3><\/dt>\n
Can somebody use it with a keyboard, or a screen reader?<\/h3><\/dt>\n
Does it respect \"reduce motion\"?<\/h3><\/dt>\n