State of Connecticut Web Site Accessibility Committee ConneCT - Your Key to Accessibility

Last updated: March 17, 2005

Home | Policy | About | Status Reports | Meetings | Membership | Listserv | Resources | Tools | Tutorials | Forms | News | Search | Site Map

Meeting Announcements and Minutes (1999)

1999 - October 6, 1999 | November 8, 1999 | December 13, 1999

December 13, 1999

Web Site Accessibility Committee Meeting Minutes, December 13, 1999, 2 p.m., Office of Protection and Advocacy for Persons with Disabilities, 60B Weston Street, Hartford, Connecticut.


Kathleen passed out WAI (Website Accessibility Initiative) Tips Reference Cards and an article "Make the Internet Accessible for All" published in the December issue of magazine.

The Comptrollers Office puts out the Popular Report each year. Had put it on the Web Site previously. Last year it came in PDF (Portable Document Format) format which was difficult to convert to HTML. In the future work will be given in source files (Word, Excel, pictures) and PDF will not be used.

Kathleen had two accessibility demos with Judicial; Carlos Velez from DAS came with their Webmaster to review Purchasing, Procurement and Job Application portions of their Website for accessibility. Will communicate with Dr. Pam Libby about the issues.

Kathleen saw OMNIForm 4.0, being used as part of the e-government project, which will scan in preprinted forms then converts to a form that could be filled out on line with JAVA scripting. Tested it with a preprinted Comptrollers form and it worked great. Cost $150.00 per seat.

Kathleen met with several people from the city of Hartford after the last meeting. Their web site has a bitmap image with links that do not show up anywhere with graphics turned off. They left committed to making their site accessible.

Bobby is now available in a Macintosh version.

Brian Sigman asked if there any procedures for a state agency developing a Web site to ensure accessibility. Kathleen stated that there are procedures for where Websites reside and how consultants are hired but they do not address accessibility.

Recommendation: DOIT should have the requirements in their RFP for Website design to include accessibility. The standards we have are 4 years old and need to be updated before we could give them to DOIT to reference.

ConneCT Management Advisory Committee meeting- reviewed two state agencies (DMR and DOT) Websites with JAWS, Web TV and Bobbie. Attendees where very interested in seeing their sites under these conditions.

The feeling is that DOIT is aware of accessibility issues and will make any web masters aware of this for new sites that are developed.

Next CMAC meeting is at the end of January 2000.

This group needs to review and update the guidelines for accessible Website design. Will they be a standard or a guideline? Kathleen- they will go out through DOIT.

Could the guidelines be implemented like the building code? If a site is changed or updated it must meet the new guidelines. Existing sites could stay as they are until they are updated.

Brian will bring up Web Accessibility at the next DAS committee on getting people with disabilities hired in the state regarding the need for disabled.

November 8, 1999

Web Site Accessibility Committee Meeting Minutes, November 8, 1999, 2 p.m., Office of Protection and Advocacy for Persons with Disabilities, 60B Weston Street, Hartford, Connecticut.



There are 14 items listed in the Web Content Accessibility Guideline 1.0 W3C Recommendation 5-May-1999

  1. Provide equivalent alternatives to auditory and visual content.
  2. Don't rely on color alone.
  3. Use markup and style sheets and do so properly.
  4. Clarify natural language usage.
  5. Create tables that transform gracefully.
  6. Ensure that pages featuring new technologies transform gracefully.
  7. Ensure user control of time-sensitive content changes.
  8. Ensure direct accessibility of embedded user interfaces.
  9. Design for device-independence.
  10. Use interim solutions.
  11. Use W3C technologies and guidelines.
  12. Provide context and orientation information.
  13. Provide clear navigation mechanisms.
  14. Ensure that documents are clear and simple.

It was agreed that for the next month, committee members would focus on Guideline 1. Provide equivalent alternatives to auditory and visual content.

Need to develop a test center and user community.

Test center is just about complete - the following software and tools are installed:

Prior to development of a user testing community, it was agreed that a checklist should be developed for testers to use during the process.  Anita Cox will work on this checklist, for discussion at the January meeting.

October 6, 1999

Web Site Accessibility Committee Meeting Minutes, October 6, 1999, 1:30 p.m., State Comptroller's Office, 55 Elm Street, Hartford, Connecticut, Conference Room B

The following people were in attendance:

A mission statement for the CMAC Accessibility Committee will be drafted by Kathleen Anderson and posted to the list for discussion and approval, prior to the CMAC meeting on October 28th.

A draft revision of the Purpose of the existing Universal Website Accessibility Policy, which can be found at   will be written and posted to the list by Kathleen Anderson.

Demo at the October 28, 1999 CMAC meeting
JAWS Bobby WebTV Viewer

Volunteer web sites for demo (tentative):

Location of future meetings
Two locations were offered: Connecticut State Library for the Blind and Physically Handicapped in Rocky Hill Office of Protection and Advocacy for Persons with Disabilities in Hartford Those present felt that the Hartford location was more convenient for most committee members and we would accept their offer. Anita Cox will 'poll' the list to find an agreeable, monthly, date or day on which to meet. Note: the cmac-ac reply to option should be changed to "reply to list".

Other Topics

Meeting Announcements and Minutes from other years

HTML 4.01 - Follow this link to view the page validation results|Valid CSS - Follow this link to view the page validation results