E-mail List Archives
Thread: Tenon.io
Number of posts in this thread: 3 (In chronological order)
From: Weissenberger, Todd M
Date: Tue, Jun 21 2016 7:09AM
Subject: Tenon.io
No previous message | Next message →
One of our groups has expressed an interest in adopting Tenon.io to help their developers keep tabs on accessibility during the development cycle. My knowledge of Tenon is limited to a few perfunctory tests on the public site, and minimal use of the Chrome plug-in.
Does anyone have a good example of a Tenon.io workflow that can help make this a good fit for developers who may not have a solid grasp of accessibility principles, standards, and practices? Feel free to share off-list if you prefer.
Best,
Todd
T.M. Weissenberger
Web Accessibility Coordinator
Information Technology Services
University of Iowa
319-384-3323
From: Caid, Lisa M.
Date: Tue, Jun 21 2016 7:54AM
Subject: Re: Tenon.io
← Previous message | Next message →
Hello Todd, Am copying information from a recent post to another list on same topic, in case it helps. Thanks!
"From: The EDUCAUSE IT Accessibility Constituent Group Listserv [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Gunderson, Jon R
Sent: Thursday, May 05, 2016 1:02 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [ITACCESS] Tenon Accessibility Testing
Tenon.io and other commercially developed testing tools are more geared for remediation of existing web pages or web applications where accessibility has not been fully considered in the design.
They only test a subset of accessibility requirements that can be classified as pass fail.
I would recommend the open source tools we have been developing at Illinois to give you more information on accessible design. In addition to Pass/Fail rules will be manual checks and information about how to use web standards, HTML5 and ARIA to create more accessible website that conform to WCAG 2.0 Level A and AA requirements.
AInspector Sidebar (for Firefox)
An Firefox Add-on to evaluate the current DOM of a web page for WCAG 2.0 Level A and AA requirements
http://ainspector.github.io/
Functional Accessibility Evaluator 2.0
Spiders a website for WCAG 2.0 Level A and AA requirements and generates a summary report
http://fae20.cita.illinois.edu/
Accessibility Bookmarklets
Browser add-ons that help make hidden accessibility information visible to sighted developers
http://accessibility-bookmarklets.org
Jon
From: The EDUCAUSE IT Accessibility Constituent Group Listserv [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Stefani Cuschnir
Sent: Thursday, May 05, 2016 11:45 AM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [ITACCESS] Tenon Accessibility Testing
I just wanted to share the link to additional information and location for the aXe - (open source a11y testing rules engine) for the group.
FREE download (on GitHub)
It was requested by a few in the group.
Stefani Cuschnir
Business Development Manager
703.909.8084
www.deque.com
On Thu, Apr 28, 2016 at 12:19 PM, Tunde Giwa < = EMAIL ADDRESS REMOVED = > wrote:
Hello All:
We are about to embark on a major redesign of our website. One of our key objectives is to make our site much more compliant with key accessibility mandates. Our digital agency is proposing tenon.io (https://tenon.io/documentation/what-tenon-tests.php) to identify any 508 and WCAG 2.0 issues on our new site. Is anyone here familiar with this service?
Thank you.
-----------------
Tunde Giwa | CTO | = EMAIL ADDRESS REMOVED = | The Juilliard School, 60 Lincoln Center Plaza, New York NY 10023 | 212.799.5000 x357 | Helpdesk Portal
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/."
And More â
"From: The EDUCAUSE IT Accessibility Constituent Group Listserv [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Terrill Thompson
Sent: Thursday, April 28, 2016 1:54 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [ITACCESS] Tenon Accessibility Testing
I wrote a blog post about this just a couple weeks ago:
http://terrillthompson.com/blog/730
I tested several web accessibility checkers on a single page where the accessibility problems were known. Some tools successfully detected a few more problems than others, but none of them could detect the big issues regarding the overall interface (i.e., is that dropdown menu accessible? What about that carousel?) So at best I think these tools are great for raising a basic level of awareness, but need to be part of a much larger overall accessibility effort. It's therefore important to keep this function in mind as you shop for a checker: If your goal is to raise awareness and/or educate website owners, which tool does the best job of explaining accessibility issues in a way that your campus community is likely to respond to?
Regards,
Terrill
---
Terrill Thompson
Technology Accessibility Specialist
DO-IT, Accessible Technology Services
UW Information Technology
University of Washington
= EMAIL ADDRESS REMOVED =
On Thu, Apr 28, 2016 at 11:25 AM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
yes i have used the tool. i think it does a good job but if this is there only way of assuring access you need to push back. ask what the plan is for user testing and what disability will be represented in the user pool. automated tools can only catch about 15% of the problems. make sure they plan on other ways to assure your access. lucy
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces
On Thu, Apr 28, 2016 at 9:57 AM, Stefani Cuschnir < = EMAIL ADDRESS REMOVED = > wrote:
Hi Tunde,
Another Open Source tool you may want to look at is aXe - download on GitHub. It is free and integrates with your current testing environment.
On Thu, Apr 28, 2016 at 12:19 PM, Tunde Giwa < = EMAIL ADDRESS REMOVED = > wrote:
Hello All:
We are about to embark on a major redesign of our website. One of our key objectives is to make our site much more compliant with key accessibility mandates. Our digital agency is proposing tenon.io (https://tenon.io/documentation/what-tenon-tests.php) to identify any 508 and WCAG 2.0 issues on our new site. Is anyone here familiar with this service?
Thank you.
-----------------
Tunde Giwa | CTO | = EMAIL ADDRESS REMOVED = | The Juilliard School, 60 Lincoln Center Plaza, New York NY 10023 | 212.799.5000 x357 | Helpdesk Portal
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
--
Stefani Cuschnir
Business Development Manager
703.909.8084
www.deque.com
Deque Systems
2121 Cooperative Way
Herndon, VA 20171
O: 703.225.0380 ext 127
F: 703.225.0387
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/."
Sincerely,
Lisa Caid, B.S.
Accessibility Coordinator
West Texas A&M University
= EMAIL ADDRESS REMOVED =
(806) 651-1241
IT Service Center (806) 651-4357
If you need email content or attachments in alternate formats for accessibility, please send your contact information and the specifics of your request to = EMAIL ADDRESS REMOVED = .
-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Weissenberger, Todd M
Sent: Tuesday, June 21, 2016 8:10 AM
To: ' = EMAIL ADDRESS REMOVED = ' < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] Tenon.io
One of our groups has expressed an interest in adopting Tenon.io to help their developers keep tabs on accessibility during the development cycle. My knowledge of Tenon is limited to a few perfunctory tests on the public site, and minimal use of the Chrome plug-in.
Does anyone have a good example of a Tenon.io workflow that can help make this a good fit for developers who may not have a solid grasp of accessibility principles, standards, and practices? Feel free to share off-list if you prefer.
Best,
Todd
T.M. Weissenberger
Web Accessibility Coordinator
Information Technology Services
University of Iowa
319-384-3323
From: _mallory
Date: Thu, Jun 23 2016 2:43PM
Subject: Re: Tenon.io
← Previous message | No next message
One possible workflow for an individual developer is to have it
integrated in whatever taskrunner is the hippest these days (task
runners are popular among front-end devs, which do things like
minify and concatinate HTML, CSS, and Javascript files, compile
CSS if a preprocessor like LESS or SASS is used, linting, etc) and
each change, or manually, the dev can send what's been built to
Tenon and get feedback (either directly in the terminal as JSON
or on the website for pretty graphs).
This is something we've got in the planning for our dev team at
work, however I feel developers running things like Tenon or aXe
are still best served by having someone on hand who can still
explain the results of the tool. What I think is nice about that
is that, while the developers are developing and getting feedback
from the tools, accessibility experts can help those developers
get more familiar with, and more facility reading accessibility
rules and things like the WCAG docs.
AXe is another that runs within a developer's dev cycle. Unlike
the browser-based testers, this is meant as automation to do what
automation is good at, just like the task runners mentioned above
that developers run. It's not necessarily meant as a replacement
for the browser-based tools, and no tools are a replacement for
dedicated QA/tester/specialists on the accessibility front.
Both aXe and Tenon can be integrated into Selenium tests as well
if you want these tests to be able to break the build when they
find warnings/errors. However for Tenon I'd say make sure you've
tweaked/set your levels (to lower false positives depending on
the kinds of code you have) before letting such a tool actually
break a build. You can adjust the sensitivity and importance of
individual tests (based on WCAG rules) and you can also set
tests by number to be skipped if necessary. I figure aXe has
similar ways of setting sensitivity but I haven't looked further
at it than someone internally giving a quick demo (using Selenium
and Java).
So I see something like Tenon as being useful in two ways: either
to give individual developers feedback as they interate through
write/read/fix code, or something sitting in the QA stack more
near the end, when a dev does a push or a pull request and
a bunch of other testing is happening too.
cheers,
_mallory
On Tue, Jun 21, 2016 at 01:09:57PM +0000, Weissenberger, Todd M wrote:
> One of our groups has expressed an interest in adopting Tenon.io to help their developers keep tabs on accessibility during the development cycle. My knowledge of Tenon is limited to a few perfunctory tests on the public site, and minimal use of the Chrome plug-in.
>
> Does anyone have a good example of a Tenon.io workflow that can help make this a good fit for developers who may not have a solid grasp of accessibility principles, standards, and practices? Feel free to share off-list if you prefer.
>
> Best,
> Todd
>
> T.M. Weissenberger
> Web Accessibility Coordinator
> Information Technology Services
> University of Iowa
>
> 319-384-3323
>
> > > >