Sakai 2.7 Accessibility Review

Table of Contents

• Conference Call info
• Testing Schedule
• 2.7 Accessibility Review Contacts
• Tool Signup
• Test Server

Accessibility Review Kick-Off Conference Call

The regularly scheduled Accessibility Working Group Teleconference for Thursday, January 28th, 2010 at 2pm EST will be used for the Accessibility Review Kick-Off Meeting.

To join the call:

• Dial (812) 856-3600
• Enter Conference Access Code: 002264#
• Listen until the conference begins
  

Testing Schedule

2.7 Accessibility Review Contacts

Accessibility Review Work Flow

1. Sign up in the Testing Participation Sign-up Table
2. Pick tools/components you want to test, determine the protocol(s) you'll use, and then sign-up under the appropriate protocol columns in the Tools/Components Sign-up Tables
3. Attend the Accessibility Review Kick-off Teleconference Thursday, January 28th, 2pm EST [Optional, but recommended]
4. Check the Tools/Components Sign-up Tables "Info" column for any special instructions and for a walkthrough script.
5. If using a walkthrough script, please verify with Brian Richwine that the required content has been created.
6. If test scripts do not exist, either create your own, explore the tool ad-hoc, or request assistance
7. If you create scripts, please add them to the wiki under the Sakai 2.7 Accessibility Walkthrough Scripts page. Please also update "Info" column in the Tools/Components Sign-up Tables
8. Test according to your chosen protocol, record the results in the appropriate reporting template, rename the template as instructed, and then save the results by attaching it to the Sakai 2.7 Accessibility Review Results page.
9. Attend the Accessibility Review Results Teleconference and discuss issue priorities and recommendations
10. Accessibility Review Lead will summarize results, and group will discuss after review from WG post them to the wiki and announce them
11. Accessibility Review Lead will issue Jira Tickets based on issues discovered and contact appropriate project leads
12. Followup Jira Tickets

Getting a Confluence - Jira Account and Joining the Accessibility Working Group Email List

To comment on or edit wiki pages you will need an account. Go here to signup for an account (One account for both the Confluence Wiki and Jira systems). Go here if you forgot your password.

Visit this page to join the accessibility working group's email list.

Testing Participation Sign-up

Please add your name and contact information to the Accessibility Review Participants table below, and then go to the sign-up table belowand indicate the tool (or tools!) you plan to review by putting your name in the appropriate space. Please take note of the tools marked with high or medium priority levels, as these tools will definitely need covered in the review.
You can add your name to the table by logging into the wiki, choosing the "Edit" tab, clicking on the "Rich Text" tab that appears, scrolling down to the tool you're interested in, and adding your name.

The amount of time to review a tool will vary by the number of pages it contains; in our experience it takes about two to three hours on average to review a tool. Please add any comments to the Sakai 2.7 Accessibility Review Results page. Record your results in the appropriate template,name the template file appropriately, and then add your finished templates as attachments to the Sakai 2.7 Accessibility Review Results page.

Contact Brian Richwine with any questions. Thank you in advance for your help!

Accessibility Review Participants

Please add your name, contact info, and indicate your interest in participating in the Sakai 2.7.0 Accessibility Review:

Tools/Components Sign-up

Add your name below to the tool you are interested in testing.

MyWorkspace Tools

Sakai Enterprise Bundle Tools

Access to Test Servers

The Sakai 2.7 QA Servers Page lists and provides links to servers running Sakai 2.7 that are available for testing. Unless otherwise specified, we will be using the "qa1-nl" QA server. If using an existing walkthrough script, please check the script to see if user names have been specified, otherwise create a new user account as needed.|