Version 2.7.3 - Release Date 2023-07-04.
Version 2.7.2 - Release Date 2023-06-27.
Version 2.7.1 - Release Date 2023-06-12.
Version 2.7 - Release Date 2023-05-02.
Version 2.6 - Release Date 2023-03-27.
Introduced a new crawler. Replaced the Crawler4j library with a new custom crawler developed using the Selenium Library.
This new feature allows crawling of dynamics web sites built upon modern libraries such as Angular, Vue or React.
Version 2.5 - Release Date 2023-01-03.
Added Selenium Library to support server side rendering (SSR). Server Side Rendering allows to validate dynamics web sites built upon modern libraries such as Angular, Vue or React.
The following WCAG 2.1 techniques have been updated:
Version 2.4 - Release Date 2022-11-07.
Added the number of occurrences per result of the success criterion applied to HTML elements in the web page.
Version 2.3.5 - Release Date 2022-07-25.
The maximum number of web pages that can be validated by creating a project has been extended to 50.
The following WCAG 2.1 techniques have been implemented:
The implementation of the ARIA11 technique has been updated.
Within WCAG 2.1 guidelines, techniques may relate to multiple Success Criteria. We updated our WCAG 2.1 implementation by adding the following associations, which were previously missing:
Updated technique F78 considering only outline-color to check whether the focus is visible
Updated technique H98 added the 'off' value to the list of allowed values for all the input element types.
Added the value REM to the allowed values for the following thechniques: C12-C13-C14-C28
Updated techniques H30 and H65 in order to check whether the link or button description is contained also within descendant elements (in the previous version the description was only checked within text part of the analysed element
Several users reported that the validator returns error for element that are not visible to users but they are accessible to assistive technologies such as screen readers. Such elements in bootstrap have the following class (Bootstrap 4:sr-only, sr-only-focusable; Bootstrap 5: visually-hidden and visually-hidden-focusable), we decided to skip the analysis of visual requirements (i.e. contrast between background and text color) for all elements having such classes
Updated the evaluation summary overview by presenting the violated/warning/passed/not_applicable techiques listed by conformance level
The implementation of the following thechniques has been updated:
The new version 2.2 allows users to create projects (set of pages to validate), and to schedule periodical audits, and visualize how the validation results change over time.
Added to the evaluation report the Not Applicable category: it reports the number of techniques that are not applicable to the evaluated page elements.
The accessibility and completeness metrics have been updated in their calculation, now they no longer consider not applicable techniques.
"Introduced the Project functionality to monitor the accessibility of multiple pages of a web
"Within a project, multiple audits can be created to evaluate the web pages. Audits can be executed just once or scheduled at fixed interval.
"Such new functionalities allow users to compare and improve the accessibility of a web site over the time." "The difference between the Multipage Evaluation and the Project concerns the results of the evaluation: in the first case, each Multipage evaluation is atomic and not related to other Multipage Evaluations even if the the base url is the same; while the Project functionality introduces the concept of Audit (there can be multiple audits for the same project) allowing users to do multiple evaluations of the same web pages belonging to the project and then to compare the evaluation results in order to monitor the evolution of the accessibility over the time."
M.A.U.V.E. (Multiguideline Accessibility and Usability Validation Environment) is a system to evaluate accessibility of Web sites by checking their HTML and CSS code through guidelines, which are to be specified through an XML-compliant specification language called L.W.G.D (Language for Web Guideline Definition) that maintains the guidelines separated from the underlying logic. MAUVE++ aims to reduce the cost of validation, increase consistency in the identification of the problematic parts, and extend the set of features that can be assessed. It is not able to identify all the possible accessibility problems since in some cases human intervention is necessary for this purpose.Its main features are: .
MAUVE++ is easy to use. At https://mauve.isti.cnr.it, you can indicate the way what to evaluate (single page or creating projects (set of pages to validate)) and enter the corresponding web address.
In order to indicate the level of accessibility detected MAUVE++ provides two metrics.
Each validation technique with an error result is assigned a weight based on the corresponding WCAG conformance level of the applied validation technique:
MAUVE++(Multiguideline Accessibility and Usability Validation Environment) is a system to evaluate accessibility of websites by checking their HTML and CSS code through guidelines, it provides validation results for different types of stakeholders, and supports validation of W3C guidelines.
Download from GitHub the supported guidelines definition in the XML language
At the moment MAUVE++ is able to validate the accessibility of web pages in relation to the following guidelines:
Depends on the validation type (single or multi page, MAUVE++ will report the results in 3 different way:
In the traditional Static Web Page validation, the validation tool downloads the HTML and the CSS ofthe page, then it parses and validates the corresponding DOM
Using the Server Side Rendering Validation, the validation tool does not parse the static web page code, but it exploits the Puppeteer library to load the HTML (and CSS) code in a headless version of the Chrome browser. In this way, it simulates the loading phase as if the page were open in the user's browser and then performs the validation on the DOM of the resulting page obtained by also performing the scripts included in it.
This can be useful in case of Single Page Applications, but more in generally it can provide a more complete validation.
Of course, since the page will be loaded in a headless version of Chrome and then validated, the validation completion time will be longer than standard Static HTML validation.