From the course: Using Stark for Accessible Design Projects

Software changes

- [Instructor] One of the joys of being a LinkedIn Learning author is that on occasion, we get to interact with the people behind the software. As I was developing this course, the Stark wizards made it abundantly clear to me that Stark had no intention of adding features when they get around to it. Instead, it was made abundantly clear to me that Stark embraces change and to expect it. Imagine my surprise when, after the day I recorded this course, Stark revamped its web tools UI, thus, you may be looking at your version of the Stark UI and thinking the one used in this course doesn't look anything like yours. You would be correct. The tools are all there; just in different places, not to mention the fact a new tool has been added to the lineup. What they have done, as you can see, is to categorize the tools by purpose, testing and inspecting. In many respects, this change makes the tool set even more intuitive. Instead of the list used in this course, you now know exactly what the tools do. There is also a new tool, automatic monitoring, which is a pretty neat addition to the lineup, and I'll go through it in Chapter 2. With that out of the way, let's start using Stark for accessible design projects.

Contents