2024

The highlight of our current sprint is the new function for assigning multiple test checkpoints to one issue.

It is often the case that an error that is listed under ‘4.1.2 Name, Role, Value’, for example, is also an error in ‘2.1.1 Keyboard’.
Previously, you had to manually set the other test checkpoint to ‘failed’ and write a corresponding note. With the new function, several test steps can now be directly assigned to one issue.

We were busy in July and released three waves of improvements (see the log at the end of this post): this includes new features, as well as multiple bug fixes, among others:

• Display tags of individual checkpoints on their details-views (previously only in the checkpoint list)
• Accessibility improvements of the PDF export
• Possibility to configure an alternative text for your organization logo
• Improved handling of longer CSS selectors in automated testing
• Extended support for the LanguageTool plugin in several form fields
• Improved test catalog management: filter by organization affiliation
• Keyboard shortcut improvements on Mac for the rich text editor

Add a sample with URL to your audit and CAAT will open the individual web page in the background and perform automated accessibility tests. These tests identify potential errors, which then appear as suggestions in your manual test report.

Over the last few weeks, we have mainly been working on the new project views. In the future, it will be possible to manage several audits (manual and automated) together in one project. One of CAAT's principles is to offer a tool that is as flexible as possible for different workflows and situations. With the project views, CAAT will be able to be used for even more diverse tasks.

In the last few weeks we have made some changes again. In addition to major internal changes, we have been able to fix some bugs and improve user-friendliness.

With this update it is possible to import files with tests for multiple URLs from the axe-core CLI. Information on importing issues

We have also been able to fix some bugs.

With this update, we are continuing to prepare CAAT for new exciting functions.

The otherwise more technical changes are accompanied by a number of bug fixes in various parts of the application and the text editor.

Even the small changes can make day-to-day business more productive.

We are happy to release a long-awaited feature with this update: Issues now have a number unique to their test. This makes it easier for you to talk to your customers and colleagues about your test results.

The number is incremented over the course of a test. If you delete an issue, a gap remains in the sequence of numbers. This is how we ensure that yesterday's number 10 is tomorrow's number 10.

The same applies when copying a test: copied issues are not re-numbered. The numbering continues from where the previous test left off.

The first update of the year comes with some minor bug fixes and some usability improvements.

The name of the current test is now part of the document title. This makes it easier to distinguish when you have different tests open in several windows, e.g. to compare content.

Previously, it was in many places not possible to open links in a new browser tab using Ctrl + click or Cmd + click. This behavior has now been updated so that you can, for example, write an issue in a new tab and leave the list of previous issues open.