RE: Released AccDC Enterprise API V1.1 for automatically accessible RIA development
- From: "Homme, James" <james.homme@xxxxxxxxxxxx>
- To: "programmingblind@xxxxxxxxxxxxx" <programmingblind@xxxxxxxxxxxxx>
- Date: Mon, 10 Jan 2011 07:04:16 -0500
Hi Brian,
Could Java be used on the back end of this? If so, maybe it would be more
palatable for corporate folks.
Thanks.
Jim
Jim Homme,
Usability Services,
Phone: 412-544-1810. Skype: jim.homme
Internal recipients, Read my accessibility
blog<http://mysites.highmark.com/personal/lidikki/Blog/default.aspx>. Discuss
accessibility
here<http://collaborate.highmark.com/COP/technical/accessibility/default.aspx>.
Accessibility Wiki: Breaking news and accessibility
advice<http://collaborate.highmark.com/COP/technical/accessibility/Accessibility%20Wiki/Forms/AllPages.aspx>
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Bryan Garaventa
Sent: Monday, January 10, 2011 4:06 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Released AccDC Enterprise API V1.1 for automatically accessible
RIA development
I released it in November of 2010, and most of the time since has been spent
debugging and beta testing all of the features.
It does work, the API is completely stable.
You can download the WhatSock Clone Sample from the Getting Started tab at
WhatSock.com, which is an exact clone of the WhatSock.com user interface, all
of which is powered by this API.
The front-end aspects of the API are powered by jQuery, and the backend is
powered by PHP. However the API is entirely client side, so that anyone using
the API can run applications on websites or on personal computers with the same
level of functionality. For example, the WhatSock Clone Sample can be run from
a local computer and doesn't require any server side support to operate.
Since the AccDC Enterprise API is only about 4 months old at this point, it is
still technically in the beta phase. Even so, whatever version is used from
this point forward will always be consistent, and all of the documented
functionality is fully stable.
----- Original Message -----
From: qubit<mailto:lauraeaves@xxxxxxxxx>
To: programmingblind@xxxxxxxxxxxxx<mailto:programmingblind@xxxxxxxxxxxxx>
Sent: Sunday, January 09, 2011 8:40 PM
Subject: Re: Released AccDC Enterprise API V1.1 for automatically accessible
RIA development
This sounds great if it works. It's the first I've heard of it. Have you posted
it before? How long has it been around and is there any app that uses it that
we could try?
Just curious.
What language is it in?
--le
----- Original Message -----
From: Bryan Garaventa<mailto:bgaraventa11@xxxxxxxxxxxxxx>
To: programmingblind@xxxxxxxxxxxxx<mailto:programmingblind@xxxxxxxxxxxxx>
Sent: Sunday, January 09, 2011 9:51 PM
Subject: Fw: Released AccDC Enterprise API V1.1 for automatically accessible
RIA development
In case it's of interest.
----- Original Message -----
From: Bryan Garaventa<mailto:bgaraventa11@xxxxxxxxxxxxxx>
To: dev-accessibility Firefox<mailto:dev-accessibility@xxxxxxxxxxxxxxxxx>
Sent: Sunday, January 02, 2011 10:24 PM
Subject: Released AccDC Enterprise API V1.1 for automatically accessible RIA
development
Hello, in case it's of interest, V1.1 of the AccDC Enterprise API has been
released at www.WhatSock.com<http://www.WhatSock.com> .
Change Log
1. Added internal processes to make drag and drop functionality accessible to
screen reader and keyboard only users without ARIA dependencies.
2. Added the "accDD" object to allow for screen reader and keyboard accessible
drag and drop to be configured at runtime.
3. Added the "accDD.dropAnchor" property to specify custom locations for screen
reader and keyboard only user targeted drop links within the DOM.
4. Added the internal drag and drop handlers "init", "dropInit", and "override"
to allow for custom processing.
5. Added the "drop" object to support drop zones when dragging.
6. Added the "confineTo" and "minDistance" properties to restrict dragging to a
specific container or range.
7. Added the "morph" method so that standard DOM elements can be converted into
AccDC Dynamic Content Objects at runtime.
8. Added the "destroy" method so that AccDC Dynamic Content Objects can be
converted into standard DOM elements at runtime.
9. Added the "setFocus" method so that keyboard focus can be set to any DOM
element at runtime.
10. Converted the AccDC Slider Control into a downloadable plugin to reduce API
overhead.
11. Added server side version tracking to prevent conflicts.
I've added a working sample of the keyboard accessible drag and drop
functionality to the Live Demo tab page at WhatSock.com.
For those who may be unfamiliar with the project, I've pasted the executive
summary below.
In a nutshell, the AccDC Enterprise API automates dynamic behaviors to create
powerful Rich Internet Applications.
Since I still need to add a bug tracking system to the site, please address any
bugs to me directly, and I'll add them to the queue.
Sincerely,
Bryan Garaventa
Executive Summary
The AccDC Enterprise API is a scalable dynamic content management system that
powers complex behaviors in Rich Internet Applications while ensuring automatic
accessibility for Assistive Technology users to maximize consumer marketability.
The AccDC Enterprise API saves time, costs, and resources by
1) Streamlining dynamic behavior related processes for development teams,
2) Providing flow-controlled processes for simple debugging,
3) Utilizing interchangeable component objects for easy code manageability,
4) Exposing property-controlled behavior switches for programmatic
configuration,
5) Supporting cross-browser compatibility for PC and mobile device
browsers, and
6) Automatically including accessibility features for screen reader and
keyboard only users.
Nestable AccDC Dynamic Content Objects (automatically generated by the AccDC
Enterprise API) are used to render any type of UI component, including form
components, dialogs, toolbars, menus, prompts, tooltips, tab pages, navigation
panels, draggable windows, or any other visually displayed UI component; all of
which are configurable by changing or invoking properties and methods within
each object during setup or at runtime.
To ensure accessibility, the Automatic Accessibility Framework provides
automated accessibility features for every AccDC Dynamic Content Object.
Benefits:
> Differing programming tasks can now be delegated to multiple development
> teams to assemble component objects with reliable results.
> Progress flags can now be set within component objects to indicate
> processing milestones for error handling and bug reporting during quality
> analysis.
> Flexible interfaces can now be created by cloning the behaviors and
> functionalities of other component objects.
> Behaviors and functionalities of component objects can now be invoked by
> external scripting processes.
> Component objects can now be passed to other pages as JSON strings, and
> then converted back to component objects to share data and resources.
> The behaviors, functionalities, appearances, and content of component
> objects can now be modified or enhanced at runtime.
> Dynamic component objects can now be used in all major browsers or
> within the web browser components of software applications.
> Screen reader and keyboard only users can now access the functionality
> of component objects automatically.
Rich Internet Applications are the way of the future for providing feature
rich, interactive user experiences for consumers in all markets and industries,
and the AccDC Enterprise API is designed to be a platform where the future of
automatically accessible Rich Internet Applications will grow and evolve into
reality.
©2010-2011 WhatSock, LLC; All rights reserved.
________________________________
This e-mail and any attachments to it are confidential and are intended solely
for use of the individual or entity to whom they are addressed. If you have
received this e-mail in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this e-mail without the author's prior permission.
The views expressed in this e-mail message do not necessarily represent the
views of Highmark Inc., its subsidiaries, or affiliates.
Other related posts:
