Action Items

Follow up on already reported issues in current and previous releases.

Attendees

Hadi Rangin

Laurie Harrison

Anne Marie Armstrong

Nicaise Dogbo

Terry Thompson

Allen Maynard

Steve Lee

Dean B. Purdue University

Jon Gunderson

Nancy Swenson

Kathleen Bastedo

Phil Kragnes

Ella Herz, Blackboard

William Murray, Blackboard

Alex, Blackboard

Discussion

1. Sub-Groups Reporting

Blackboard Testing Sub-Group Report

Reporting: Terry Thompson

New Grade Centre is being tested, with initial review and reporting by testing group members having been completed. After several weeks of regular meetings, teleconferences among group members are suspended until updated build is available as the group is currently standing by, waiting for integration of their suggestions for improvement by Blackboard. Major issues were identified and these issues have been entered formally into the Blackboard development process tracking system. Initially the group has been looking at instructor mode with focus on navigation. Screen reader and keyboard testing has occurred. If others in the group are interested in participating in this activity please contact Terry.

QA Sub-Group Report

Reporting: Ella Herz
Last week’s meeting for this sub-group discussed best practices for testing application of this scale and how the application can be broken down into smaller modules for review. Blackboard is investigating Evaluation Tools such as WebXM with possility of licencing/acquisition in January to enable a more systemic approach. There will be a meeting on this January 30th. Hadi will contribute criteria/priorities for testing tools functionality. Clarification around mandate confirmed that this sub-group focuses on development of practices and areas of focus.

Documentation Sub-Group Report

Reporting: Hadi Rangin
The work of the documentation sub-group is targeting the following stakeholder groups:

Support Team at Blackboard – how to field questions, provide support

Engineers – practices to follow to ensure accessibility

AT Users – how Bb works with AT software

Content Creators – guidelines for those who are authoring or building courses

This information is currently available as a work in progress in the sub-groups page in the Wiki for Documentation Sub-Group. Resources are currently being collected. These resources will be organized, updated and made more usable to the community. Many contributors have posted documents which can be seen at: http://www.athenpro.org/wiki/index.php?title=BB-DOC_Subgroup_page

2, Outstanding Issues – Review Process

Reporting: Will Murray
Some of these remaining issues from Vista (16) and Bb (10) are still being addressed for current/past releases. The list of issues are being reviewed and noted as resolved or open. Through review of current status of outstanding issues the gaps are being identified. May be fixed or included in guidelines for future development as appropriate.

3. New Release of Vista

Hadi Rangin asks how we can participate in review of anticipated new Vista release. Will had no information at this time but will be consulting with Stephanie.

4. Blackboard use of HiSoft for testing.

Reporting: Ella Herz
Ella stated that Stephanie was coordinating this and that no detailed information was available at this time. She indicated that WebXM is being considered for purchase. It is configurable for various guidelines (508, WAI WCAG). This software acts as a crawler to review the application and create reports that are used by developers to correct code. Hadi asked if it reviews for Functional web accessibility. Jon expressed concern that review requires human intervention; encouraged review of navigation components. Ella suggested that WebXM was the most automated in the creation of content as part of the review process.

Stephanie responded to this problem via an e-mail and wrote: "Blackboard is not using these tools internally. The document outlines
that a third party performed the audit and used these advanced tools for
their evaluation."

5. HTML & CSS validation

Accessing Frame
Hadi asked about strategy for access to source code for Frame-based pages. He has had difficulty in viewing source code of the frames. It was suggested that he route JAWS to PC Cursor to access source code for the frame.

Hadi also raised issues he has had with validating pages. (ie doc type, CSS, frameset). Ella stated that Stephanie will be following up. Frameset coding was discussed as inconsistencies in DOM are problematic. For example some instructor links are not navigable by keyboard and screen reader. Ella suggested it would require review. Currently she doesn’t believe they are testing to address this specific issue with screen readers, though readability of doc types is checked.