Version 4.0 - Release Date 2024-10-07.

• UI CHANGES: Italian language added, layout updated. NEW FEATURE: possibility to download the report in CSV format for a single page and for an audit (from the same audit page).

Version 3.0.4 - Release Date 2024-07-30.

• BUG FIXES: Fixed a bug in PDF validation related to technique MPDF2 (concerning WCAG Success Criterion 1.1.1)

Version 3.0.3 - Release Date 2024-06-21.

• BUG FIXES: Restored the functionality for downloading PDFs modified with accessibility corrections.Please note that this functionality is not yet available for "Projects".

Version 3.0.2 - Release Date 2024-02-23.

• Features removed: "Static Web Page Validation" and the validation report in PDF format.

Version 3.0.1 - Release Date 2024-02-05.

• Added COMBINED Accessibility Percentage: Obtained by calculating the average value between the accessibility percentage of the linked PDF documents and the accessibility percentage of the web page based on the techniques.

Version 3.0.0 - Release Date 2024-01-17.

• Added PDFs ACCESSIBILITY PERCENTAGE: Number of PDF techniques successfully evaluated out of the total number of PDF techniques for which the tool was able to make a successful or unsuccessful evaluation.

Version 2.9.0 - Release Date 2024-01-09.

• Added PDFs ACCESSIBILITY VALIDATION within Projects: If selected, the crawler will find a maximum of 50 PDFs linked in the project pages and these will be analysed.
  PDF TECHNIQUES:
  • SC 1.3.2 - 2.4.1 - 2.4.3 - Added the PDF3 technique.
  • MAUVE++ Best Practices - Added the MPDF3 technique. Allow the user to extract text and images from the PDF document for accessibility purposes.

Version 2.8.0 - Release Date 2023-12-04.

• NEW PDFs ACCESSIBILITY VALIDATION FEATURES: Added accessibility validation for PDF documents. With the "Single PDF doc evaluation" feature, you can validate a single PDF resource by entering its url or uploading the file directly. In addition, in the "Single page evaluation" feature, it is possible to specify whether validation should also be conducted on all PDFs linked to the page.
• SC 1.1.1 - Updated the implementation of F65 technique. Improved control for decorative images.
• SC 1.1.1 - Updated the implementation of H37 technique. Improved control for decorative images.
• SC 1.4.1 - Updated the implementation of F73 technique.

???info_Version_2.7.4??? - Release Date 2023-10-11.

• The Color Contrast Checker tool has been added

Version 2.7.3 - Release Date 2023-10-02.

• Updated the crawling process.

Version 2.7.3 - Release Date 2023-07-04.

• SC 1.3.4 - Updated the implementation of F97 technique.

Version 2.7.2 - Release Date 2023-06-27.

• Improved ability to exclude html elements not visible on page from analysis.
• SC 1.3.1 and 4.1.2 - Updated the implementation of ARIA16 technique.
• SC 1.3.1 - ARIA11
• SC 3.2.5 - Updated the implementation of H76 technique.

Version 2.7.1 - Release Date 2023-06-12.

• SC 1.4.11 and 2.4.7 - Updated the implementation of G195 and F78 technique.
• SC 1.4.3 and 1.4.6 - Updated the implementation of G18 technique. Added the possibility to validate the font-size property expressed with named font-size.

Version 2.7 - Release Date 2023-05-02.

• Updated accessibility percentage calculation to include weighted values (based on the level of conformance - A, AA, AAA - of the success criteria) for occurrences with a pass result;
• Added Accessibility and Evaluation Completeness percentages based on Success Criteria. Up until now, values were generated solely based on technique results;
• A bug has been fixed in the assignment of the pass or fail result to an HTML element during the comparison of the conditions of a technique. This resulted in an incorrect assignment of the result to some analyzed elements;
• Fixed a bug in false positive reporting for techniques H30, G195, F78;
• SC 1.4.11 - Updated the implementation of G207 technique.

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:

• SC 1.4.10 and 1.4.4 - Removed the technique SCR34 because in its current state it is not possible to automatically verify it
• SC 2.4.7 and 1.4.11 - Updated the implementation of G195 and F78 techniques
• SC 1.4.1 - Updated the implementation of F73 technique. Now Mauve++ is able to provide a certain answer about this technique (moved from CannotTell to error result).
• SC 1.4.4 - SCR34
• SC 1.3.1 and 1.4.5 and 1.4.9 - Updated the implementation of G140 technique

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:

• SC 4.1.1 - F77
• SC 1.3.1, 3.3.2 - G162
• SC 2.4.2 - G88
• SC 1.4.8 - SCR34

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:

• SC 1.2.3 - H96
• SC 1.3.1 - ARIA11
• SC 1.4.3 - G145
• SC 1.4.4 - SCR34
• SC 1.4.8 - SCR34
• SC 2.4.1 - ARIA11
• SC 2.4.4 - F89
• SC 2.4.7 - G195
• SC 2.4.9 - H33
• SC 4.1.2 - F89

Updated technique F78 considering only outline-color to check whether the focus is visible

???info3_Update_H98???

???info3_Add_REM???

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

???info3_SeveralUsersReported???

Updated the evaluation summary overview by presenting the violated/warning/passed/not_applicable techniques listed by conformance level

The implementation of the following techniques has been updated:

• G18: Understanding Minimum Contrast.
  ???info4_Update_G18_Description???
  • ???info4_Update_G18_Sub1???
  • ???info4_Update_G18_Sub2???
  • ???info4_Update_G18_Sub3???
• C38: The goal of this technique is to present labels and inputs in order to avoid horizontal scrolling. When the viewport space is limited and the inputs and labels cannot sit next to each other then they must be modified so that they are under one another (vertical alignment); this can be achieved by setting the display: flex property on form element or on div elements contained within a form.
• G195: Managed both the hover and focus pseudoclasses and check the border-color (top, bottom, left, right) and outline-color properties. Added the control to check whether the contrast is not at least 3 then it checks that the border (or outline) is> = 2. Applied to input type text, button, color, date,email, file, month, number, password, reset, search, submit,tel, time, url, week; button and a elements.
• G195: Added the 'off' value to the list of allowed values. Fixed a bug in the technique evaluation.
• H65: We have modified the implementation of the technique control so that it does not return an error if the button element contains some text inside it (since several screenreaders correctly associate the text with the button role). If there was no text inside the button, then there must be a title and/or aria-label attribute
• F30: The validator, in the previous version, checked all images contained within an element and returned an error if the alt attribute was null / empty string. Currently it is becoming common practice to associate the empty alt attribute with decorative images and in this case the validator must not return an error; in this regard, in the new version, we have excluded decorative images from checking the alt attribute (attribute role = presentation).
• H30: In the validation of the H30 technique if a link does not have a text describing its scope than the validator checks whether the link has title or aria-label attribute. Regarding the images with empty alt attribute and contained within a element, two additional checks have been added: one checks that the parent link element has the title attribute and the second checks that the parent link contains text inside it; if one of the two cases occurs, the validator does not return an error.
• F78: Fixed a bug in the technique evaluation: it was checked the element instead of , input and button elements.
• C28: Fixed a bug in the technique evaluation: in the new version we exclude the input type hidden elements.
• SCR34: Specified the list of element that must be checked (div, input, span, p, textarea, section, table, form)

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 site.
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.