Discussion on:
View:
Show:
Does anyone have any recommendations for free (or inexpensive) screen reader software? It'd be nice to see how my pages are "seen" (heard) in a screen reader. Thanks
Start here:
http://www.w3.org/WAI/References/Browsing.html#2
This page leads to below websites, I am intentionally not pointing to exact product URLs, because of frequent changes.
http://www.dolphinuk.co.uk/
http://www.hj.com/ - click on JAWS
http://www.aagi.com/
http://www.w3.org/WAI/References/Browsing.html#2
This page leads to below websites, I am intentionally not pointing to exact product URLs, because of frequent changes.
http://www.dolphinuk.co.uk/
http://www.hj.com/ - click on JAWS
http://www.aagi.com/
Our government organization uses IBM Home Page Reader. A trial version is available at IBM's site:
To purchase the software is relatively inexpensive. Of course, Microsoft also has a wealth of information regarding impairment accessibilities, software suggestions, etc. at:
Hope this helps.
To purchase the software is relatively inexpensive. Of course, Microsoft also has a wealth of information regarding impairment accessibilities, software suggestions, etc. at:
Hope this helps.
In the bullets list of 12 tips, last tip, the correct text is: "Use icon in addition to red color in error situations." There are some people, who can't see red color as "RED", so designers have to use some graphical WARNING ICON, in addition to red color.
Providing an alternate navigation system for Javascript and other client-side technologies is an important accessibility requirement. For example, many people have difficulty using a mouse, such as persons with visual or motor disabilities.
Ensuring that form labels and fields are correctly associated is also very important for users of assistive technologies like screen readers. Ignoring this requirement can make a Web form very difficult to use, if not totally unusable for certain users.
Finally, avoiding the use of obsolete code and cleaning up programming errors will ensure that assistive technologies (much less tolerant than most browsers) properly render web pages for disabled users.
Ensuring that form labels and fields are correctly associated is also very important for users of assistive technologies like screen readers. Ignoring this requirement can make a Web form very difficult to use, if not totally unusable for certain users.
Finally, avoiding the use of obsolete code and cleaning up programming errors will ensure that assistive technologies (much less tolerant than most browsers) properly render web pages for disabled users.
The following bullet point is exactly opposite to the way it should be
- Use text presentation via , , etc.
You should AVOID using text presentation tags such as these and use CSS to do all formatting and positioning of text. Using bold formatting has significance and this may not be transmitted to screen reader users unless the strong tag is used.
- Use text presentation via , , etc.
You should AVOID using text presentation tags such as these and use CSS to do all formatting and positioning of text. Using bold formatting has significance and this may not be transmitted to screen reader users unless the strong tag is used.
Why no popups? Popups can be very useful in comparing two sets of data or providing extra information/capability without having to leave the page (consider the "help" link on a form with opens popup window with detailed instructions on how to complete the form)
Although there are lots of examples of inaccessible and generally annoying popups out there, there's a way to do it better. The best way I've seen is to use the tag with the target attribute set. If you prefer the window to have a specific initial width/height, you can also have a Javascript function that gets called by the <nclick attribute. This function would return false so 2 windows don't pop up. This way, you support the average Javascript-enabled user while keeping it accessible for the others.
Example:
Help
Although there are lots of examples of inaccessible and generally annoying popups out there, there's a way to do it better. The best way I've seen is to use the tag with the target attribute set. If you prefer the window to have a specific initial width/height, you can also have a Javascript function that gets called by the <nclick attribute. This function would return false so 2 windows don't pop up. This way, you support the average Javascript-enabled user while keeping it accessible for the others.
Example:
Help
I'm just starting in accessible web design and I find that laying out the content in a text processor, such as notepad, helps me get the 'flow' right..(main content first followed by other sections ,under a heading, picture placements etc...) I then attempt to tart it up with CSS!
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
