Thanks!,
I found these resources during my accessibility research, WAI-ARIA
seems to be "the standard" for the moment, Google is currently using
it experimentally for all search results, a free plugin (manual
install, but seems to work great) for Firefox called Fire Vox is
available.
ARIA Introduction provides background on the accessibility problem
space solved with ARIA.
http://www.w3.org/TR/wai-aria-primer/
ARIA Roles, States and Properties defines the ARIA syntax.
http://www.w3.org/TR/wai-aria/
ARIA Best Practices describes how to develop accessible rich web
applications using ARIA.
http://www.w3.org/TR/wai-aria-practices/
Dojo and YUI (2&3) seem to have "the best" support for WAI-ARIA.
Interestingly enough the concept of "regions" could provide for a lot
of assistance in the development of mobile and other "non-standard"
screen size application. Support for "standard" key combo's to save,
edit, open files and so on seems interesting as well. Perhaps the most
interesting "sleeper" item might be TTS (Text To Speech) applications
like news readers and so on.
Who Supports WAI-ARIA
http://wiki.codetalks.org/wiki/index.php/Who_Supports_WAI-ARIA
Browsers (I only checked the top 3)
Chrome
http://sites.google.com/a/chromium.org/dev/developers/design-documents/accessibility#TOC-WAI-ARIA-Support
FireFox
http://www.accessfirefox.org/Firefox_3_Accessibility_Features.php
IE
http://www.microsoft.com/windows/internet-explorer/readiness/developers-new.aspx
Todd Kloots: "Developing Accessible Widgets Using ARIA"
http://video.yahoo.com/watch/4073211/10996186
Welcome to Code Talks!
http://wiki.codetalks.org/wiki/index.php/Main_Page
http://www.w3.org/WAI/intro/aria
WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a
way to make Web content and Web applications more accessible to people
with disabilities. It especially helps with dynamic content and
advanced user interface controls developed with Ajax, HTML,
JavaScript, and related technologies.
http://developer.yahoo.com/yui/examples/menu/menuwaiaria.html
All YUI ARIA Plugins require the user's browser and AT support the WAI-
ARIA Roles and States. Currently only Firefox 3 and Internet Explorer
8 have support for ARIA, and are supported by several screen readers
for Windows that also offer support for ARIA. For this reason the YUI
ARIA Plugins are only enabled by default for these browsers. To enable
the ARIA plugin for other browsers, simply the set the usearia
configuration property to true. For example:
Applying WAI-ARIA to Yahoo! Mail
http://www.paciellogroup.com/blog/?p=45
The Future ???
http://www.firevox.clcworld.net/demos/css_demo.html
http://www.firevox.clcworld.net/demos/multilang_hello.html
On Nov 6, 8:14 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
> perhaps this may be useful to you.
>
> http://webrocket.ulmb.com/ability/
>
> On Nov 6, 6:36 pm,ChristopherSteel<chris.st...@gmail.com> wrote:
>
> > I am in the middle of "recreating" menu's for a high accessibility
> > site, As long as it is easy to turn off and / or to redirect flash
> > messages to a fixed status area I have no objections.
>
> > At the moment I am wishing for global switch or flag that would put
> > web2py in to a high efficiency / accessible mode, although I am still
> > in the process of working out exactly what that would look like, but
> > we are getting there.
>
> > Our second beta will have zero "drop down" menu's at the request of
> > our blind users, and a minimal "site", "page/content" menu with some
> > experimental access keys.
>
> > Ironically, dealing with css and menus seems to be taking way more
> > time than regular programming stuff with Web2py. Hoping to contribute
> > back anything that is useful, although I am really new to Python and
> > web2py. Web2py is simply stunning, I think the ability to flip a
> > switch for one level menu's and status area flash messaging in
> > addition to some working multi-lingual examples would put Web2py in a
> > position for total world domination...
>
> > Alpha baby, It's sooo ugly, but works sooo well.
>
> > http://myvishpala.appspot.com/init/default/index
>
> > (yea, it's the GAE wiki demo!)
>
> > Thanks for this most awesome application framework everyone!
>
> > Cheers,
>
> >ChristopherSteel
>
> > On Nov 6, 5:43 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > Two of the CSS are special. The one for flash and the one for error.
> > > They are special because most third party layouts do not define them
> > > but web2py needs them.
>
> > > I propose adding a <style>.flash {...} .error {..}</style> in
> > > web2py_ajax.html before including th CSS files. This way you can
> > > override them but you get a default even if you use an out of the box
> > > third party layout.
>
> > > Anyone opposed?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
