Tuesday, July 27, 2010
Below are suggestions to improve accessibility Web new Web site for section 508 of the Government of the United States. Well, in the analysis, at least, the home page. This is basic thing and I'm very disappointed that the site leaves much to be desired. The site, which is the law of the u.s. Government with Web accessibility rules, should be an example of a Web site accessible. And with the recent anniversary of THE ADA, this was a great opportunity to advance in the field of Web accessibility. But instead, unfortunately, this was a failed attempt. The u.s. Government has much work to do.
No positions! Not one. Need titles in markup, period. There are many titles indicated visually, but improperly encoded using strong or div tags. Labels for text entries are incorrect. There is a label tag, but no text label! See the search text and email to signup text. Alternative news to many images need improvement, how to remove "chart for". Better yet, do not use a graphic when not needed. the text is very well in the following two cases. (Lose the inline style would also be good). Example 1:
Example 2:
No keyboard focus to match the mouse hover effect. In addition, a focus & focus can be added in several places to make it more usable, such as the top-level items in resource navigation left/main menu "AddThis" media requires JavaScript and in both cases is not keyboard accessible. ARIA implemented, even Marco functions to help with navigation links like "read more > >" have no context; is not unique. We also recommend that you remove the ">" character (better use CSS for these types of markers/symbols). text links are unclear. The underscores are removed and dark blue not distinct enough text of progressive improvement. Poor black. With JavaScript turned off, totally not display the options menu and the contents of the feature of the slider isn't title displayed. Redundant attributes must go! I'm so tired of seeing this. It is not helpful, but instead gets in the way. and it creates code bloat. Example:
link policy e-mail content placeholder is confusing. The example is not a valid email address (top level domain is missing). The resource can be done with unobtrusive JavaScript and even use the label text, if it existed. Horizontal scroll bars on resolution 1024. Need better resizing/design width. Lots of CSS in the header (and inline). much better to use external file attribute language = "JavaScript" not necessary in XHTML. Why display the date? Only adds Print screen button. not necessary cluttered. Only adds the screen disordered. Requires JavaScript. Conditional comment for IE6 CSS should be in the head, body not .text resizing tool is not required. Let the browser do that! And disorders screen. Some navigation items use lists while others do not ButtonType.image need better optimization/compression. Alone in a feature image slider is more than 150 k and can easily be compressed to 35 k. 67 XHTML validation errors. Labels: analysis, gov, law
Please consider donating to Web axe. Funds required for captions.
Vote or accompany on Podcast Alley:
Dennis Lembree is the founder, author and presenter main web axe. He owns the web development company specializing in Web reviews, usability, web standards and accessibility. Follow Dennis on Twitter: @ dennisl
Ross Johnson runs a Web design company (3.7 designs) that takes a holistic view of the web and the art of building pages. They strive to be creative and original. Follow Ross on Twitter: @ 3pointross
