[Accessibility] minutes Open A11y call 2011-03-08 [draft]
Gregory J. Rosmaita
oedipus at hicom.net
Tue Mar 8 12:00:39 PST 2011
aloha!
minutes from the 8 March 2011 Open Accessiblity Teleconference
are available as hypertext at:
http://www.linuxfoundation.org/en/Accessibility/Minutes/Minutes20110308
and as plain text following this announcement -- please log any
errors, corrections, clarifications, mis-attributions and the
like by replying-to this announcement on-list
IMPORTANT LOGISTICAL NOTE: due to CSUN 2011, there will NOT be a
meeting on 15 March 2011; the next scheduled Open A11y meeting
will be held on 22 March 2011
http://www.linuxfoundation.org/en/Accessibility/Minutes/Agenda20110322#Agenda
IA2 SIG UPDATE: on 3 March 2011 the latest version of IAccessible2
(version 1.2.1) was released and is available at:
http://a11y.org/ia2-spec
congratulations to Pete Brunet and the IA2 SIG for all of their
hard work on IA2
gregory.
_________________________________________________________________
Open A11y Working Group Conference Call (8 March 2011)
Retrieved from:
http://www.linuxfoundation.org/en/Accessibility/Minutes/Minutes20110308
Contents
1 Open A11y Working Group Conference Call (8 March 2011)
1.1 Preliminary Items
1.1.1 Participants
1.1.2 For Reference
1.1.2.1 Agenda
1.1.3 Approval of Past Minutes
1.1.4 Announcements
1.2 Meeting Minutes
1.2.1 Topic 1: ISO Update: Document Status and Remaining
Work
1.2.1.1 Peter Korn's Proposed Definitions for CORBA,
D-Bus, and GNOME
1.2.2 Topic 2: Mapping ARIA to ATK/AT-SPI
1.2.3 TOPIC 3: 21st Century Video and Communications
Act Review
1.3 Wrap Up
Preliminary Items
Participants:
* Janina Sajka (JS/chair)
* Pete Bruent (PB)
* Mike Gorse (MG)
* Peter Korn (PK)
* Gregory J. Rosmaita (GJR/scribe)
* regrets: none logged
For Reference
Agenda
* Agenda for the 8 March 2011 Open A11y Call
* http://www.linuxfoundation.org/en/Accessibility/Minutes/Agenda20110308
Announcements
Due to CSUN 2011, there will NOT be an Open A11y Call on 15 March
2011; the next scheduled Open A11y Call will be held on 22 March 2011.
_________________________________________________________________
Meeting Minutes
Topic 1: ISO Update: Document Status and Remaining Work
FOR REFERENCE:
* Agenda for 8 March 2011/ISO Update (Janina Sajka)
https://lists.linux-foundation.org/pipermail/accessibility/2011-March/002710.html
* Updated drafts of the ISO document are available in tex,
xhtml, odf, and pdf:
* http://rednote.net/iso.html
* http://rednote.net/iso.pdf
* http://rednote.net/iso.odt
* http://rednote.net/iso.tex
* Re: Agenda for 8 March 2011/ISO Update (Peter Korn)
https://lists.linux-foundation.org/pipermail/accessibility/2011-March/002711.html
Peter Korn's Proposed Definitions for CORBA, D-Bus, and GNOME
* Common Object Request Broker Architecture (CORBA)
* an inter-process communication standard defined by the
Object Management Group that enables software components
to communicate with each other across processes, address
spaces, and even computers, in an object-to-object
fashion
* D-Bus
* an inter-process communication technology developed by
freedesktop.org that is the de facto standard of Linux /
UNIX graphical environments
* GNOME
* formerly an acronym meaning "GNU Network Object Model
Environment", it is both a common and accessible graphical
desktop for Linux / UNIX graphical environments, as well as
an open source project delivering a collection of software
libraries and applications
JS: assigned individuals to review our document; received number of
comments; began to make changes
JS: question about copyright -- can open a11y keep a copy of this
document ourselves - MG pointed out is one of best introduction to the
technology
JS: said at meeting, if open a11y published doc as submit to ISO, then
on separate path, but open a11y owns copyright, so if copyright and
submit copyrighted version to ISO -- may diverge, but 2 other modules
(UIA and IA2) will not diverge -- no comments when ballot taken;
advantage of owning copyright on it means we can change content if
necessary -- probably will be necessary -- things happen faster than
ISO time clock
JS: tricky part -- comments on ISO document -- process: committee
reviewed document, gave specific suggestions for changes, nothing
dramatic; requested to make changes and get final draft into ISO
secretariat for SC35 (in france) -- deadline: mid-May 2011 -- gives
them time to reformat to their "specifications" (convert to word
format and ISO-formatted version to distribute to all national bodies
in time for voting before next SC35 meeting slated for August 2011; if
approved in August, becomes an ISO technical report;
PB: IBM did document on IA2?
JS: yes
JS: asked Andi Snow-Weaver if could do same thing with that document
-- she indicated "too late in process to get necessary sign-offs in
IBM"
* TR13066-3 is IAccessible2 (ASW of IBM)
* TR13066-2 is UIAutomation (Microsoft)
PB: is IAccessible a.k.a. MSAA included in IA2 document IBM did for
ISO?
JS: referenced, but not discussed in any great degree
PK: reviewing document now -- document doesn't describe API in detail
-- links out to programming documentation for windows desktop --
describes in general MSAA server model, etc.; all using same style
guide: "this is how role/state boundaries are supported"
PB: references to MSAA documentation?
PK: yes
JS: comments: definitions need to be consistently formatted; suggested
that longer definitions/explanatory part might drop into footnotes;
significant concern about diagrams displaced in document, not where
discussed -- by-product of LaTeX (not uncommon problem); like to try
to get changes recommended incorporated into document by next week
JS: another comment: descriptions of diagrams didn't always use same
terms that are in the diagrams; need to ensure that they are sync-ed
up and contain identical wording
PK: which is most up-to-date?
JS: http://rednote.net/iso.tex or http://rednote.net/iso.pdf (22
February 2011)
PK: created own definitions
* Common Object Request Broker Architecture (CORBA): an
inter-process communication standard defined by the Object
Management Group that enables software components to communicate
with each other across processes, address spaces, and even
computers , in an object-to-object fashion
* D-Bus: an inter-process communication technology developed by
freedesktop.org that is the de facto standard of Linux / UNIX
graphical environments
* GNOME: formerly an acronym meaning "GNU Network Object Model
Environment", it is both a common and accessible graphical desktop
for Linux / UNIX graphical environments, as well as an open source
project delivering a collection of software libraries and
applications
JS: is corporate stuff distracting
GJR: could hand of to an appendix that list corporate info
JS: prefer use of footnote
JS: need to read through PKorn's document to sync them up -- no one
complained about AT-SPI terseness, but wonder if might be too terse
PK: came up with a diagram -- completely different style
JS: can PKorn send me latest copy
PK: waiting for one more round of internal review (required)
PB: would like to review IA2 documentation
JS: confirmed that these are public documents as long as they are
drafts
GJR: who maintains the IA2 ISO doc?
JS: Andi Snow-Weaver of IBM
GJR: PeteB you might want to contact ASW directly
_________________________________________________________________
Topic 2: Mapping ARIA to ATK/AT-SPI
FOR REFERENCE:
* WAI-ARIA 1.0 Candidate Recommendation Draft (2011-01-18)
http://www.w3.org/TR/2011/CR-wai-aria-20110118/
* WAI-ARIA 1.0 Authoring Practices: An Author's Guide to
Understanding and Implementing WAI-ARIA (latest editor's
draft)
http://www.w3.org/WAI/PF/aria-practices/
* WAI-ARIA User Agent Implementation Guide (latest editor's
draft)
http://www.w3.org/WAI/PF/aria-implementation/
* HTML to Platform Accessibility APIs Implementation Guide a
user agent developer's guide to understanding and implementing
accessibility support in HTML
http://dev.w3.org/html5/html-api-map/overview.html
JS: David Bolter created them inside of FireFox -- great that are
mapped, but is that where info should be -- should be more at API
level than wed to particular UA so all UAs can take advantage of them
PK: look at work going on in WebKit/GTK -- exposing events for Orca,
work fairly well together
JS: is that the richer model that ARIA requires?
PK: don't know details -- focused on GNOME desktops -- don't know
status of ARIA support for Webkit
GJR: need RichS input on this
JS: yes, adding that to what is available to us moving ARIA from CR to
PF
PK: to what extent does ARIA event model make sense outside of web --
if does, then makes sense, if not, doesn't
PK: ARIA concepts very useful concepts
MG: wonder if always mapping or if there are roles that don't have
mapping
MG: can ping dave or fernando -- may want to explore at may 2011
hackfest
PK: makes a lot of sense
MG: if they are significant need for this can schedule a dial-in
session for that
JS: may be predicated on how many people need it -- someone with SIP
on laptop can provide teleconference facilities
_________________________________________________________________
TOPIC 3: 21st Century Video and Communications Act Review
FOR REFERENCE:
* The main NPRM on Advanced Communication (PDF file)
http://www.fcc.gov/Daily_Releases/Daily_Business/2011/db0303/FCC-11-37A1.pdf
* Video Description NPRM (PDF file) contains scanned images in
Appendix C
http://www.fcc.gov/Daily_Releases/Daily_Business/2011/db0303/FCC-11-36A1.pdf
* Telecommunications Relay Fund NPRM (PDF file)
http://www.fcc.gov/Daily_Releases/Daily_Business/2011/db0303/FCC-11-38A1.pdf
PK: President Obama signed 21st century video and communications act;
last friday, FCC published 3 notices of proposed rule-making -- 300
pages worth of RPM in 3 document with 30 day turnaround
PK: might be interesting to review section around events and
notifications; also section on telecommunications probably of interest
to JS -- congress directed FCC to do this for interconnected and
non-interconnected VOIP -- freeswitch.rednote.net would thus have to
pay -- general question about free software services and
laws/regulations made by sole monopoly AT&T
PK: real-time text for at least (next generation) 911 calls
(electronic and voice)
PK: will asterisk need to support that? acquires audio portion of SIP
connection
JS: tend not to have omnibus applications in linux environment
PK: what impact does this have on open source community
PK: advanced communications: propose covers not just SMS, IRC but also
email, arguing every app should be accessible ,so when buying phone
that does SMS or email, needs to have built-in AT; but if on desktop,
what does "built-in" mean? whole model of desktop integration not
understood by politicians when law drafted
PK: pleased to see work by CodeFactory in this area -- they submitted
comment to FCC stressing importance of a11y APIs
FOR REFERENCE: CodeFactory products include:
* Mobile Accessibility
http://www.codefactory.es/en/products.asp?id=415
* TV speak
http://www.codefactory.es/en/products.asp?id=416
* Mobile Speak
http://www.codefactory.es/en/products.asp?id=316
+ MobileSpeak 4
http://codefactory.es/en/products.asp?id=318
* Mobile Magnifier
http://codefactory.es/en/products.asp?id=312
* Mobile DAISY player
http://codefactory.es/en/products.asp?id=314
* Color Recognizer
http://codefactory.es/en/products.asp?id=315
_________________________________________________________________
Wrap Up
* meeting adjourned 1657h UTC
* next Open A11y conference call: 2011-03-22
http://www.linuxfoundation.org/en/Accessibility/Minutes/Agenda20110322
_________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/accessibility/attachments/20110308/a6e9d7a5/attachment-0001.htm
More information about the Accessibility
mailing list