Re: Cafecito Sprint Rosario: semantic markup, usability, a11y and so on…

we finally managed to push some of the work done during Cafecito Sprint 
to include initial support for WAI-ARIA relationships on Plone's 
z3c.form based forms.

can someone take a look on this and make comments?

https://github.com/plone/plone.app.z3cform/pull/7

once we figure out what's the best way to solve this, is going to be 
easier to include more a11y attributes in the forms.

why do we need this?

TL;DR: Accessibility deficiencies in today's markup render rich internet 
applications unusable by people who use assistive technologies or who 
rely on keyboard navigation, the W3C plans to address these deficiencies 
through several W3C standards efforts and WAI-ARIA is one of them.

aria-describedby property is applied to a form element to identify the 
element that describes the field form.

aria-required property is applied to a form element to indicate that it 
is required to complete the form.

http://www.w3.org/TR/wai-aria-practices/#relations_labeling

best regards

Héctor Velarde

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers