We're confident that Treejack is compliant with Section 508, though Chalkmark and Optimal Sort are not. Our compliance has not been officially assessed by any other party.

We take accessibility seriously and attempt to make considerations for accessibility when designing all of our applications. We encourage any of our users to point out accessibility problems with our applications, and we will endeavor to fix them with priority.

Section 508 was enacted by the US Federal Government to eliminate barriers in information technology, to make available new opportunities for people with disabilities, and to encourage development of technologies that will help achieve these goals. The law applies to all Federal agencies when they develop, procure, maintain, or use electronic and information technology. Information on Section 508 can be found at the official website: http://www.section508.gov/

The Web Content Accessibility Guidelines (WCAG) are a set of requirements for making web pages accessible to people with disabilities.

The Government of Canada requires web systems to conform to the requirements set out in WCAG 2.0 to the standard of Level AA.

If you have any questions, or if there's any aspect of the WCAG 2.0 guidelines you feel we're not adequately complying with, please let us know.

Treejack conforms to the criteria of WCAG 2.0 at Level AA

In some cases it's not possible to guarantee this. For example, the criteria 1.4.3 Contrast - Minimum and 3.1.2 (Language of Parts) both require action from survey administrators to ensure that language metadata is present and that color contrast on buttons is adequate.

Chalkmark can't comply with WCAG 2.0 because of Criterion 1.1.1: 'All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.'

Chalkmark tests static images, like screenshots and wireframes. It's therefore not possible to test people who can't see and click on the image. A text description of the webpage would not be any help in completing the exercise, as people who rely on solely text input can't interact with a wireframe in any way. They need a prototype that is capable of being traversed by assistive technologies like screen readers.

OptimalSort currently doesn't comply with WCAG 2.0 because of criterion 2.1.1: 'All functionality of the content is operable through a keyboard interface.' Participants must use a mouse to use the interface to sort cards, and therefore can't use a keyboard. This is something we are looking to change in the future.