Projects

access.see.be

With access.see.be, a WAI-ARIA based Accessibility-Library, web developers can enhance their applications with accessible rich interface elements or can create full accessible rich internet applications without excluding users who depend on assistive technologies like screen readers. So the main aim ... [More] of universal design, the approach to design websites that can be used by all people without the need for adaptation or specialization, can be easily achieved. [Less]

aveghe-my-blog

Aveghe My BlogGoalsAveghe My Blog is a blogging platform for all user. The main goal is the creation of a blogging platform W3C-WAI compliant. The first stage is the creation of basic service completely server side, accessible and usable also by blind or visually impaired users. The second stage ... [More] , using progressive enhancement, is the creation of a Web 2.0 application (using Javascript and AJAX). The development cycle provides constant user test. TechnologyTo develop Aveghe My Blog I'm using: PHP 5; Zend Framework; XHTML 1.0 Strict and CSS; Javascript and AJAX; MySQL 5; Netbeans. [Less]

tcc-diego

Um modelo de desenvolvimento de sistemas web com foco na aplicação dos padrões da w3c: desenvolvimento e comparação de sites, antes e depois da padronização. Este trabalho consiste em um estudo da versão antiga e de um protótipo elaborado para o TCC, com base nas recomendações definidas ... [More] pela W3C. Vários aspectos foram analisados, a fim de averiguar qual a melhor forma de se desenvolver um site web, se de modo padronizado ou indiferente às propostas da W3C. Seguindo o checklist proposto por Russ Weakley (Reconhecido internacionalmente por suas apresentações em Workshops sobre o desenvolvimento de web sites.), se realizou a análise de inúmeros quesitos, entre eles: a qualidade do código escrito; o nível de separação entre o conteúdo e a apresentação; a acessibilidade para usuários, considerando inclusive problemas visuais, tais como cegueira parcial e daltonismo, e para dispositivos diversos; além de usabilidade e a administração do site. Após a aplicação dos testes propostos no checklist nos sites, verificou-se que, se padronizado, seguindo ao máximo as especificações propostas pela W3C, obtêm-se um desempenho superior em praticamente todos os aspectos analisados, sendo que o protótipo elaborado se mostrou 422% mais leve e rápido em relação ao antigo; compatível com navegador textual e, portanto mais acessível às pessoas com deficiência visual. Apresentou-se ainda compatível com os navegadores que seguem os padrões da W3C, e com alto nível de separação entre o conteúdo e o layout através de CSS e XHTML. Foi aprovado em testes de análise sintática de arquivos XHTML e CSS , resultando num código bem escrito e linguagem de marcação bem formada. O protótipo fora desenvolvido utilizando a linguagem de programação PHP; sobre o framework CakePHP; com SGBD MySQL e framework Javascript jQuery. [Less]

access-see-be

With access.see.be, a WAI-ARIA based Accessibility-Library, web developers can enhance their applications with accessible rich interface elements or can create full accessible rich internet applications without excluding users who depend on assistive technologies like screen readers. So the main aim ... [More] of universal design, the approach to design websites that can be used by all people without the need for adaptation or specialization, can be easily achieved. [Less]

eminds

Latex template to give format to the author contributions to eMinds (International Journal on Human-Computer Interaction) www.eminds.hci-rg.com

imoves

A system utilizing the accelerometer on the iPhone to recognize gestures. The goal is to allow the visually impaired to operate the iPhone with gestures (proprioception instead of sight), and perhaps help regular people driving, etc. better use the device.

qfocuser

QFocuser 0.95 - class for keyboard navigable AJAX widgets for better usability and accessibilityFeatures:allow to your widget listen key events when its focused focus can be enabled on any element fires focus and blur events (so your table row will NOT remain highlighted after click out of table for ... [More] example) make your widget to be accessible by tab key tiny and library agnostic this implementation could serve as a model for the others works also in Safari! (but with crazy workaround) Tested on: IE6/7, FF2/3, Safari, Webkit, Opera and Chrome Key navigation is important part in overall usability and accessibility of all applications. If you have only one widget, key events can be safely attached to document, but if more than one widgets are involved, each widget has to react to keyboard separately, which means when it has focus. Also, each widget has to react when focus is lost (remove highlighted row for example). There is no another solution than listen blur event. Any other solution based e.g. on mouseclick will fail with iframes. .. read this: http://dojotoolkit.org/book/dojo-book-0-9/part-3-programmatic-dijit-and-dojo/writing-your-own-widget-class/creating-accessi How it should work: Key tab switches between your widgets, in order defined by tabIndex. Focused widget can listen key events. How it work: To make elements focusable, set them tabindex. That will allow you to attach keyboard events to them too. The tabindex value can allow for some interesting behavior. If given a value of "-1", the element can't be tabbed to but focus can be given to the element programmatically (using element.focus()). If given a value of 0, the element can be focused via the keyboard and falls into the tabbing flow of the document. Values greater than 0 create a priority level with 1 being the most important. Safari issue: Current version of safari doesn't support tabIndex for regular elements. WebKit nightly build does. This library has a workaround for it, to have almost same behavior. Hiding the Browsers Focus Borders issue: All browser including IE6/7 will show pesky dotted borders around focused elements for accessibility reasons. The dotted visual clutters up the design. To remove them, use options doNotShowBrowserFocusDottedBorder. It has to be done in code, because Internet Explorer has no style property for that. If you are remove them, do not forget use own focused element highlighting. Example: var focuser = new QFocuser(widgetContainer, { onFocus: function(focusedEl) { .. add highlighted class or whatever } onBlur: function(focusedEl) { .. remove highlighted class or whatever } }); // attach your own keys listeners $(focuser.getKeyListener()).addEvent('keydown', e.g. handleArrows); // when your widget decided to set the focus (and then receive key events) focuser.focus(tableRowForExample);Demohttp://daniel.steigerwald.cz/qfocuser/default.htm Links: http://snook.ca/archives/accessibility_and_usability/elements_focusable_with_tabindex/ http://wiki.codetalks.org/wiki/index.php/Docs/Keyboard_navigable_JS_widgets http://dev.aol.com/dhtml_style_guide - recommended key shortcuts License: MIT-style license. Copyright: Copyright (c) 2009 Daniel Steigerwald, daniel.steigerwald.cz [Less]

rightlink

Proceed to RightLink installation page on Google Chrome extensions gallery.Right click for open link in new background tab. Useful for touchpads without middle button. Real context menu will be open on right click with Alt or Ctrl button pressed. This extension was modeled after RightLinks ... [More] Firefox extension. Extension changelog PLEASE NOTE: RightLink, like other extensions with content scripts, is disabled on the Chrome Extensions gallery (https://chrome.google.com/extensions) for security reasons. So RightLink will not be working on this site. [Less]