I'm about to go into a series of form redesigns within a section of
my company's corporate site. We've mandated that any new forms or
form redesigns should comply with WCAG 2.0 AA recommendations.
Most of the 2.0 criterion and techniques seem reasonably clear and
I'm not finding it too difficult to find examples of their
application, but I can't seem to locate a clear rule around the use
While I feel quite confident with HTML and CSS, it seems to take a bit of
pain to use Dreamweaver for wireframing, perhaps because it tends to force
you into detail too early, when you are still on the "vision" stage of the
process, and feel like a WYSIWYG tool would be more appropriate.
On the other hand, wireframing in the WYSIWYG way entirely without HTML also
feels wrong, because first, the target medium is Web so it's closer to the
reality to think in HTML, and second, HTML is a powerful and expressive
language, and quite a mature one.
Since today seems to be an introductory day, I'm relatively new to
the list as well.
I noticed there was finally a ruling on this case. Not sure of the
ramifications yet though, but this may be a major shift for any web
business, at least in California. Instead of accessibility being a
best practice issue it may become a legal one even outside of
I am currently working out a GUI concept for a windows software that should (among a 1000 other things) also be accessible in the sense that one should control the interface entirely by keyboard.
Though I know a variety of tools and standards to check and implement good accessibility on the web, I never came across any guidelines or recommendations on how to make a software accessible.
Can anyone name me some (non-technical) sources?
Andreas Bleiker, Usability Consultant,
I am doing some research to see if it is possible to write
usability/accessibility checklists split up on all the layers in a web
project: Design (layout, typography, colors), frontend coding(semantics,
standards), backend considerations (web friendly urls etc),
content(writing strategies), etc.
Each and one of the checkpoints for each list will then be split up in
importance, what is recommended, what would require extra time, when in
the project it should be implemented (try to implement userfriendly urls
a week after launch), aswell as references to section 508 and WCAG etc.
We develop a web application which is used by government users, as such it
is 508 compliant...
According to 508 checkpoint 10.4, text boxes should be filled with text,
advising the user how to fill the text box
For example a search text box will present "Enter Search Terms" (see http://www.us.gov/)
My hesitation is about combo box (drop down lists). Until now I've always
presented a default value in the combo box and it still seems to be the
right way. Is it a problem for reading-aid tools? I don't know.