well, text only sites are fine, but hardly anyone codes that way anymore. a lot of modern websites use leveled headers, tables (mostly unlabeled), frames and content pop-overs. the last can be frustrating as the screen reader will not see those without being refreshed (in the case of voiceover, using VO-i to see all objects). dynamic content is, by far, the hardest to contend with. it causes the page to refresh frequently and will reset screen readers back to the top of the page.
my suggestions for websites: 1. alt-tagged descriptions of all pictures and videos 2. labeled frames and tables 3. framed organization where stable links are in one frame and the contents that are called from those links get displayed in another frame (look at some of the linksys routers for web page examples of this) 4. accessible controls (pop-up buttons and the like) 5. advertisements (such as flash with associated links) in separate frames (can have multiple in a single frame) 6 the about content (about us, contact, copyright, Terms of Use, etc) located in a bottom frame 7. use audio captchas as well as visual ones (have a button to select which one). this way, you don't lock out print impaired individuals. those are some of the big suggestions. frames don't have to be used, but they do make organizing the web site a damned sight easier. -eric On May 14, 2012, at 6:28 AM, Kevin Chadwick wrote: > On Sun, 13 May 2012 18:17:10 -0700 > Eric Oyen wrote: > >> there are 2 ways: using ORCA in the Gnome >> desktop environment (or XFCE) or a console based screenreader > > I try to use alt text and reasonable ordering but for me to test my > websites with. Do you use particular browsers with Orca or screen > reader. At the moment, I just look at it in a text browser? > > Alt text is something that is sometimes suggested to be used on > everything to keep Google happy or help site ranking. I'm thinking > over-usage could be annoying where it's not actually required such as > putting keywords in place of something purely visual. > > Thanks, Kc
