Wave Tool Bar

0 views

Skip to first unread message

Rebecca Donnelly

unread,

Aug 5, 2024, 12:38:30 PM8/5/24

to rateposca

WAVEis a web accessibility evaluation tool developed by WebAIM.org. It provides visual feedback about the accessibility of your web content by injecting icons and indicators into your page. No automated tool can tell you if your page is accessible, but WAVE facilitates human evaluation and educates about accessibility issues. All analysis is done entirely within the Chrome browser allowing secure valuation of intranet, local, password protected, and other sensitive web pages.To run a WAVE report, simply click on the WAVE icon to the right of your browser address bar, or select "WAVE this page" from the context menu.WAVE errors align with WCAG 2.2 failures. The WAVE interface facilitates human evaluation of many other aspects of accessibility and Web Content Accessibility Guidelines and Section 508 compliance.Version 3.2.5.3 (February 2024) fixes numerous minor bugs and adds testing refinements. Some hidden inputs are no longer incorrectly flagged as not labeled.Version 3.2.4.4 (October 2023) fixes a few minor bugs with testing hidden content and with the sidebar contrast tools.Version 3.2.3.9 (June 2023) removes the warning message on UserWay pages due to them removing code that changes page content when the WAVE extension is activated.Version 3.2.3.8 (June 2023) includes numerous accessibility test enhancements, several minor bug fixes, and simplification of the contrast checking tools. Users are informed that WAVE results may be manipulated on pages that utilize UserWay or accessiBe overlays.Version 3.2.3 (March 2023) includes several minor bug fixes. A previous update to test for contrast errors in hidden elements has been reverted. While this was useful for finding contrast errors in drop-down menus, tab panels, dialog windows, etc., identification of errors in hidden elements caused user confusion and, in some rare cases, false positives.Version 3.2 (December 2022) includes over 100 bug fixes and performance enhancements. The extension no longer utilizes jQuery, resulting in faster testing and better compatibility with a variety of pages. A new Navigation Order panel is available that shows the navigation order, element roles, and accessible names (what is read by a screen reader) for all navigable elements.Version 3.1.6 (October 2021) includes numerous bug fixes and test rule enhancements for better testing contrast (filters, background images, and other complex color definitions are better handled), document language (IANA-defined language values are now tested), empty links and buttons (better ARIA support for accessible name computations), broken ARIA references, etc., etc. Performance and accessibility has been improved.Version 3.1.3 (November 2020) includes performance enhancements and fixes several minor bugs, including fixes for multiple alerts for some pseudo-lists and disabled controls being incorrectly flagged for contrast failures.Version 3.1.2 (October 2020) fixes several minor bugs, including with the Structure tab sometimes incorrectly showing no structure, and improves performance and accessibility testing reliability.Version 3.1 (September 2020) includes new accessibility tests (region, figure, possible list, select element missing label, and image with title), improved contrast checking, expanded lang attribute value checking, and numerous other bug fixes and improvements.Version 3.0.9 (July 2020) includes numerous bug fixes, improved accessibility, and improved color contrast checking including fewer false positives and expanded contrast checking for form inputs.

WAVE is a suite of evaluation tools that helps authors make their web content more accessible to individuals with disabilities. WAVE can identify many accessibility and Web Content Accessibility Guideline (WCAG) errors, but also facilitates human evaluation of web content. Our philosophy is to focus on issues that we know impact end users, facilitate human evaluation, and to educate about web accessibility.

You can use the online WAVE tool by entering a web page address (URL) in the field above. WAVE Chrome, Firefox, and Edge browser extensions are available for testing accessibility directly within your web browser - handy for checking password protected, locally stored, or highly dynamic pages.

The WAVE subscription API and Stand-alone WAVE API and Testing Engine are powerful tools for easily collecting accessibility test data on many pages. The stand-alone API and Testing Engine can be integrated into your infrastructure for testing intranet, non-public, and secure pages, including in continuous integration processes.

Your Accessibility IMpact (AIM) assessment report provides detailed WAVE test data, your site's AIM score (a measure of end user impact compared to web pages generally and as determined by human testers), and expert manual test results to give you insights into the accessibility of your web site for users with disabilities.

I may just be getting old, but although I can find lots of references to this app/driver in the forum, I can't seem to find the actual source thread for it where I would presume there would be instructions etc.

For this tool, you'll need 3 things - Parameter #, Size, and desired Value - you cannot leave any of those fields blank. Prior to my tweak, I checked the Parameter Report (available thru this tool) for my parameter and noticed the Size field was as expected, so I thought I could leave it blank when I updated the desired Value. Nope, gotta fill out all 3 fields for the change to stick.

This is probably not what mostly people use the Tool for, but the "Get Version Report" command should spit out a few things in "Logs," one of which should be the firmware version for most devices that report it. I think something like "firmware version" and "firmware subversion" are the pieces you could put together to do this (e.g., "1" and "5" would be 1.5 or, as it is often displayed, 1.05--but keep in mind that these are equivalent).

Many drivers also display this in the "Device Data" section at the bottom of the device page. However, some drivers don't update this after a firmware update, and there's no standard for how to force it to re-check (a refresh or configure might). So, I suppose the Tool is one way to always see for sure. If you're using a C-7 hub, the built-in Device Firmware Updater app can also tell you--just go to the page in it where you choose deivces, and pick the one you're interested it. The "firmware targets" dropdown will then show you the version(s), and you can just back out or close it before you update (you don't even need to upload any firmware files to get this far).

Normally, I guess commands should use hex, but since the log messages from this driver displays the parameter values in decimal I don't feel sure, and I really don't know how much I might mess up my devices if I put the wrong numbers...

This solution will show you how to utilize your Door / Window Sensor 7 Pro with dry contact and forms part of the larger Door / Window Sensor 7 Pro user guide. The Door / Windows Sensor 7 Pro has the capability to work with any dry contact...

Hi, my problem is really basic, I cant figure out how to choose the Tool as a driver for my device. I thought Id need to change the "Type" in the Device Information Part of the Device Tab, but I cant find "Basic Z-Wave Tool" as an option there. I have added the Code in the Drivers Code Section and now there is a listing of said driver.

Should not need to reboot - but you may have to refresh the Device page you were on for it to show up, or return to the Device tab and re-select the device. If you have installed it correctly it would show up after above or after a reboot, of course, since you're accessing a fresh version of the Device page.

Thx, unfortunately it doesnt do what I expected it to do... I wanted to change parameter 11 of the Fibaro RGBW Controller to "0". According to the Manual this should change the "phasing duration" during color changes, on and off and so on to "immediate" but it is still phasing...

It's the Get Parameter Report option on the Device page when you have the Basic Z-Wave Tool set as the driver. Go to your logs to see the output. Leave the parameterNumber field blank to see all parameters.

It does change parameters if used correctly...I've used it many times as have others. From your logs it does look like it changed. If the device is still not reacting properly it seems like it's a documentation problem w/the device.

Its kinda weird.... after I used the tools, it reports back as set to 0, which is the setting I want it to be... after switching back to the correct driver though it gets set to 50 (found that out after once more going back to the Basic Z-Wave Tools driver...

There is one Preference which can be set in the "original" driver and that is "Transition Time" and the Lowest Value it can be set to is 500 ms, standard seems to be 1s, there is also "no selection" but if I choose that, it reverts to 1s. I guess that is why I cant choose 0 via the parameters.

If the driver you return to modifies the parameter setting (and you can't stop it from doing that) then you could try not hitting Configure after you change drivers back to the original driver. That may stop it from changing the parameter back to 50.

If you haven't been hitting Configure after changing back to the original driver then you could look into editing the driver (or asking the author of the driver to modify it) Is the driver you're using a community driver, or a built-in driver?

I guess its a built-in driver, it was there from the start, didnt install anything else. And I havent been hitting "Configure"..

And I am relatively sure that modifying the driver is way beyond my capabilities. I managed to copy/paste and modify some LUA scripts for the Fibaro Hub scenes, but only with lots of help.