[Accessibility] Open A11y Teleconference, Tuesday 26 June at 15:00Z

Janina Sajka janina at a11y.org
Tue Jun 26 03:24:00 UTC 2012


Colleagues:

We will hold our next Open A11y teleconference on Tuesday, 26 June at
11:00 U.S. Eastern Daylight Time (EDT), which is currently 15:00 UTC.
You can check for the correct time in your time zone using the Fixed
Time Clock at:

http://timeanddate.com/worldclock/fixedtime.html?iso=20120626T11&p1=263

Main Topics

Teleconference Rescheduling
W3C Activities Update
Open Issues Checkin

Logistics

You are receiving this email individually because we're still
experiencing problems with the Linux Foundation list services for our
lists and domain.

Teleconference services for the Open A11y Work Group are now provided by
rednote.net. Three options for dialing in are described below.

NOTE:	No passcode is required for now.

1.)	Direct worldwide access using any SIP client:
	sip:2119 at freeswitch.rednote.net
If you need an accessible SIP client, try linphone (which can be
operated from either the GUI desktop or a text console).

2.)	Via any ITAD connected telephone system worldwide (such as the MIT campus telephone system):
	2119*984

	For the complete ITAD Directory, and To learn more about ITAD and TRIP, go to:
	http://www.iana.org/assignments/trip-parameters/

	Note that your ITAD installation may require an ITAD access service code.
	Example: At MIT first dial 48999 then 2119*984

3.)	Free of charge in many localities worldwide via SIP Broker's PSTN to SIP gateway service as follows:

	a.)	Find a local telephone number from the list provided at:
		http://www.sipbroker.com/sipbroker/action/pstnNumbers

	b.)	Dial that number from any telephone.

	c.)	At the SIP Broker prompt enter:
		*8390 2119

-- 

Janina Sajka,	Phone:	+1.443.300.2200
		sip:janina at asterisk.rednote.net

Chair, Open Accessibility	janina at a11y.org	
Linux Foundation		http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative	http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: diagram.odg
Type: application/vnd.oasis.opendocument.graphics
Size: 15254 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/accessibility/attachments/20120625/907e1675/attachment-0002.odg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diagram.pdf
Type: application/pdf
Size: 16757 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/accessibility/attachments/20120625/907e1675/attachment-0002.pdf>
-------------- next part --------------
ATK-AT-SPI and the Graphical Desktop
 Diagram By Joanmarie Diggs
 April 2012
At the bird's eye view, there are three conceptual sections:
1. Applications being accessed (at the top)
2. Accessibility libraries (in the middle)
3. ATs (at the bottom)

Taking each conceptual section in turn:

1. The applications-being-accessed section consists of three rows and
visually reminds me of six small layer cakes. Those apps/cakes are as
follows:

a. LibreOffice, VCL, ATK Support
b. Firefox, Gecko, ATK Support
c. GNOME Shell, Clutter, "Cally"
d. Epiphany, WebKitGtk, ATK Support
e. Gedit, Gtk+, "Gail"
f. KMail, Qt

Note: The Epiphany layer extends past its WebKitGtk layer so that a
small portion rests on top of the Gtk+ layer under Gedit. The idea is to
illustrate that Epiphany is mostly using WebKitGtk, but uses a bit of
Gtk+ for the application widgets.

The middle section is quite simple, with two layers: one for the bridges
(ATK Bridge and Qt-ATSPI2) and one for AT-SPI2. The ATK Bridge rectangle
spans the width of the ATK-implementing apps/toolkits. The Qt-ATSPI2
Bridge rectangle shares the same width as KMail/Qt. The AT-SPI2
rectangle spans the full width of the diagram.

The bottom section is also quite simple, consisting of the following
single-layer rectangles:

a. Screen Reader
b. Screen Magnifier
c. Speech for Users w/ LD
d. Speech Recognition
e. Testing Tools

There are arrows connecting each conceptual section to its neighboring
section(s). In between the applications being accessed and the bridges
are a set of double-headed arrows extending between each cake and the
corresponding bridge. This is meant to show that information between the
toolkits and the bridge flows both ways.

Similarly, there are arrows in between each AT and AT-SPI2. Some are
double-headed, some are not:

Screen reader: Double-headed, because screen readers not only receive
information about apps from AT-SPI2 but they also sometimes use AT-SPI2
to manipulate the app/environment. For instance, Orca repositions the
caret when the user navigates by heading in web content.

Screen Magnifier and Speech for Users with LD: Single-headed, pointing
to the ATs, because magnifiers and non-screen-reader speech output is
likely to be on the receiving end only: presenting information from the
environment rather than manipulating that environment.

Speech Recognition: Single-headed, pointing from the AT to AT-SPI2
because speech recognition tools are used for input which in turn acts
upon the environment being accessed.

Testing Tools: Double-headed for the same reason screen reader is,
namely both receiving input and potentially manipulating the environment.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: diagram.odg
Type: application/vnd.oasis.opendocument.graphics
Size: 15254 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/accessibility/attachments/20120625/907e1675/attachment-0003.odg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diagram.pdf
Type: application/pdf
Size: 16757 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/accessibility/attachments/20120625/907e1675/attachment-0003.pdf>


More information about the Accessibility mailing list