Home >
Accessibility is something that we all know is important when developing content for the Internet, however it is also something that has frequently been left out of a project development due to time constraints, technology challenges, or budgeting issues. I am interested in knowing how you develop your RIA content? Is accessibility something that you build into your applications currently? Is there a reason as to why you are not building RIA for accessibility? Please leave comments to this post and also please answer our poll question by voting here.
Tag Cloud
Podcasts & Screencasts
@InsideRIA on Twitter
Follow InsideRIA on Twitter
Facebook Application Development
I work in a consulting development organization, so in theory this depends on our customer and their requirements. That said, accessibility sadly doesn't seem to be a priority for any of my clients lately.
I think "not unless the client requires it" should be an option. Rightly or wrongly accessability will require more work at present and I can't see many devs swallowing that cost on morals alone.
We're developing applications that support people doing their job who have to have sufficient cognitive capabilities in order to qualify for that primary job. Still, for reasons of general usability, colors and font sizes have to fit into the target work environment.
Hi,
Working for government often comes with accessibility requirements, at least here in France. They don't often ask for RIAs, but it's starting.
Ariel
Well I think it's time to have this as standard implemented, it's often overlooked...
This could be construed as rude, but for all of the shortcut keys and ridiculous requests that we get from our users (that power users and analysts approve), I should vote yes, but "it's not that simple" will suffice.
[tab]
[type captcha]
[tab] [tab]
[space on submit]
or if you're one of our users:
[ctrl ctrl]
[c for captcha form field on keyboard shortcuts popup]
[type captcha]
[f10 for default form submit (doesn't work in browsers... we have to use a custom browser)]
I work for a government department here is Sydney Australia. We service public education. It is a requirement for us to have W3C accessibility. We try as best we can to comply. I run a small team of Flex and Flash developers and we constantly deal with support for keyboard tabbing, alt text/tool tips, video captioning, audio transcripts, alternative text/non-Flash versions, assistive technology support, colour contrast and other similar tasks for our rich Internet apps that we develop.
As a consultant, my answer depends on the client.
But I would like to be more knowledgeable in my recommendations. Can you please steer us in the direction of some resources for Flex or other RIAs and accessibility best practices?
As a consultant, my answer depends on the client.
But I would like to be more knowledgeable in my recommendations. Can you please steer us in the direction of some resources for Flex or other RIAs and accessibility best practices?