[Accessibility] Agenda for April 30 Meeting

Janina Sajka janina at rednote.net
Tue Apr 29 06:35:42 PDT 2003

Please RSVP ...
Also, please note the attachment.

Announcing the 30 April 2003 meeting of the Accessibility Workgroup

 Wednesday,  April 30,  18:00 GMT
   --   20:00 CET??  (Berlin)
   --   19:00 WET??  (London)
   --   14:00 EDT  (New York)
   --   13:00 CDT  (Chicago)
   --   12:00 MDT  (Salt Lake City)
   --   11:00 PDT  (San Francisco)
   --   04:00 JST??  (Tokyo) (03/21/03)

 Dial-in North America...800.664.6895
 Dial-in International...719.955.1126
 passcode................3 6 6 5 8 0


1. Welcome and review of minutes from our last meeting

2. Ask for a volunteer scribe to minute this meeting.

3. Old Business

	a.)  Finalize Mission Statement

	b.)	Proposed "Road Map" Document -- What's missing? What needs restating? Are the timelines and priorities appropriate? This discussion was
deferred from our earliest meetings while we examined opportunities arising from AT-SPI;

	---- A draft document is attached ----
	c. Web page progress -- The page is up but not linked. Do we need a policy regarding sites we point to?

4. New Business

7.	Confirm our next meeting is Wednesday, May 7.

				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina at afb.net		Phone: (202) 408-8175
-------------- next part --------------

1 year plan:
        AT-SPI as a means of working towards US section 508, Europe's CEN,
	 Japan's ???, and Australia's ??? programs.
		(or part thereof that could agreed on with perhaps some
                minor exclusions.)
                This will gain us - key components for
                 desktop/windowing environments.
                Lays out the responsibilities of the application vs
                 the AT layer and the kernel.
                We have early signs that major Xwindow environments
                 (GNOME and KDE at least) will both be able to adopt
                 this without major disagreement.
                This can be made to work with Internationalization.
                The Service Provider Interface is more generic than
                 just a program interface. Between the AT-SPI and the
                 ATK we should be able to implement the libraries in a
                 number of environments.

        Develop the guidelines for use of the standards to allow
         better utilization of a device by multiple apps to reduce the
         cost of ownership to the end user while maximixing all
         available compliant applications. (Hardware is expensive, but
         our software could be made less expensive.) This would make
         the technology more readily available to more people.

        AccessX Standard for Accessibility

        SMIL Libraries

2 years out:
        Textmode Only Boot for Accessibility
         This will require some kernel, bios, and bootloader

        Guidelines for Accessibility Standard for Administrators

        Structured Navigation Standard
         Important for voice driven devices in the car, etc.
          Ties into international DAISY Consortium.

3 years out:
        Voice based I/O standard
	 This is to be coordinated with OpenI18N and other groups
	  dealing with various I/O methods.

        Work to adopt portions of INCITS/V2 as appropriate
                Needed for servers driving kiosks

        Accessibility Standard for Administrators - to the extend
         possible. This involves possible kernel modifications, (how
         do devices plug in), that should be doable by this time frame.

        Installation Standard for Accessibility
         This involves cursor tracking, etc.

        Comprehensive Braille Standard

        Text To Speech (TTS)
         Could involve XML in terms of what gets sent when and how

5 years out:
        Magnification Support Standard -- Although pieces may be
         worked earlier, even in the first year, this will take a
         number of years to complete. This is not a time concern
         because of technology, but because of its overall size.

Other items we can help facilitate:

        Hardware device interfacing standard--perhaps even a Major/Minor

        Some of this item is included above--but we need more on the
	input side,+especial console level.

More information about the Accessibility mailing list