W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2012

Fw: Regarding AccDC

From: Bryan Garaventa <bryan.garaventa@whatsock.com>
Date: Sat, 12 May 2012 11:10:33 -0700
Message-ID: <5007F654B2584314B4C70B797C5CBEFB@WAMPAS>
To: <w3c-wai-ig@w3.org>, "WebAIM Discussion List" <webaim-forum@list.webaim.org>
I've recently updated the home page for AccDC at WhatSock.com to better reflect what it is, what it does, and how it works, with the information pasted below. 
(The term 'self-propagate' refers to social networking technologies, where the addition of encapsulated accessible user interface components would self-propagate across the web for everyone using these features.)

----- Original Message ----- 

AccDC is a scalable, cross-browser and cross-platform compatible Dynamic Content Management System that automates the rendering of dynamic content to ensure accessibility for screen reader and keyboard only users.

AccDC generates independent JavaScript objects, called AccDC Objects, that include customizable properties and methods which are used to control the functionality, content, and behavior of each AccDC Object at runtime.

This makes it possible to render any type of user interface component, including wizards, carousels, dialogs, toolbars, tooltips, popups, lightboxes, menus, banners, tab controls, drag and drop controls, toggles, sliders, calendar pickers, or any other type of fully functional accessible user interface component.

AccDC includes integrated ARIA support to enhance intuitive page structuring for screen reader users, as well as a recursive Announce method that
can be used to send textual messages to be dynamically announced for screen reader users. Additional ARIA attributes may be dynamically added to enhance advanced controls using AccDC's in-built Flow Control methods.

AccDC renders HTML/XHTML valid markup, HTML5, DOM nodes, JavaScript output, XML node content, JSON object data, and content from remote API callbacks.

AccDC automates accessibility by managing the processes associated with dynamic content rendering, so that the majority of common accessibility issues are automatically addressed when DOM manipulation occurs.

Since AccDC Objects are code structures for encapsulated objects, they can be redistributed as fully functional components that include in-built accessibility for screen reader and keyboard only users, so that accessible user interface components can self-propagate across various web technologies.

When AccDC Objects are opened in the DOM, the specified content is surrounded by a framework of supporting Divs that convey important role and state information for screen reader users. Based on the customizations within the AccDC Object, the content is then inserted into the DOM in an accessible location, supporting accessibility markup is added, display styling is set, behavioral settings are applied, and Flow Control methods are executed.

Additionally, AccDC Objects can be interfaced with other AccDC Objects to perform complex tasks, or nested within one another to preserve parent/child relationships.

AccDC is a closed system, and functions as a standalone API, or may be used in conjunction with any library or framework without conflict.

Since the EPUB3 specification supports the use of JavaScript, AccDC may also be included within EPUB3 compliant eBook publications to automate accessible dynamic behaviors within browser based eBook readers.

Bryan Garaventa
Received on Saturday, 12 May 2012 18:11:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:44 UTC