Major updates to Tenon: Spring 2020

Karl Groves
By Karl Groves | January 16, 2020

Introduction

In late 2012 I had an idea: Change accessibility testing by creating an API-centered tool that frees the user from the requirement that they use an external tool for testing, instead allowing developers, testers, and content authors to do accessibility testing within their existing toolsets. Since that time, Tenon has become a multi-million-dollar company - with $0 investment dollars - based solely on the excellent team we've assembled.

The Tenon API has become an ecosystem that continues to grow and improve while continually attaining my initial goal of becoming an integral part of the existing toolsets of web development staff. 

  • Tenon was the first SaaS product for Web Accessibility
  • Tenon was the first "API first" product for Web Accessibility
  • Tenon was the first accessibility testing tool to have a plugin for WordPress
  • Tenon was the first accessibility testing tool to have a plugin for Drupal
  • Tenon was the first accessibility testing tool to have a plugin for Grunt
  • Tenon was the first accessibility testing tool to have a plugin for Gulp
  • Tenon was the first accessibility testing tool to have a plugin for Silverstripe CMS
  • Tenon was the first external accessibility testing tool to have a plugin for Visual Studio (and it was developed by Microsoft themselves)
  • Tenon was the first accessibility testing tool available from CLI
  • Tenon was the first accessibility testing tool to be able to generate reports in xUnit format
  • Tenon has been added to unit test libraries like Protractor and Intern
  • Tenon was the first accessibility testing tool to have a plugin for Fractal
  • Tenon has browser plugins written for Chrome, Opera, Firefox, Internet Explorer, and Edge
  • Tenon has libraries for developers to use that are written in PHP, Python, Ruby, NodeJS, and C#

All of the above, we should add, were created by our community of over 11,500 users worldwide.

Our own developers are no slouches, either. Since January 6, 2013, our developers have:

  • Closed 4438 tickets in Jira (that's 89% of all tickets created for Tenon during our entire history)
  • Created 30787 commits (that's 17 commits per day)

And we won't be stopping anytime soon. In fact, the next 3 months may be the most impactful period in our product history.

This blog post is the first in a long series of blog posts I'll be making between now and March, highlighting what's been done and what's coming up.

Updates to Tenon's Tests

The first set of changes that we'll talk about are updates to Tenon's tests

Today we deployed dozens of changes to Tenon's tests.  In fact, the volume of changes deployed today is the largest set of changes in Tenon's entire history: over 50 test improvements including new tests, bug fixes, and removal of tests.

All-in-all, Tenon now has 180 distinct accessibility tests that look for over 3000 failure conditions.

Not only have the tests themselves been overhauled, but so has our documentation. In fact the documentation for every single test was reviewed and improved by Tenon's consulting staff. The description and remediation guidance of every test in Tenon has been improved.

If you're an existing Tenon user, you'll need to enable 8 new tests. To do so, head over to https://www.tenon.io/user/settings/edittestsettings.php and turn on the tests beginning after #260.

Stay tuned for next week's post where I'll discuss Tenon's research program and how you can get free access to Tenon!

Call us +1 443.489.6549
Mail us talktous@tenon.io