Commentary

InformationWeek
InformationWeek  

FEMA Fixes Its Web Site

FEMA apparently got the message that its online aid application for hurricane survivors, which previously worked only on Windows PCs and Internet Explorer browsers, had to change. Actually, I suspect it got a few thousand messages, after the story appeared here and elsewhere. In any case, FEMA has now posted a statement on the Web site, stating that it is "in the process of modifying the application" so that people using other browsers and systems can access it.

FEMA apparently got the message that its online aid application for hurricane survivors, which previously worked only on Windows PCs and Internet Explorer browsers, had to change. Actually, I suspect it got a few thousand messages, after the story appeared here and elsewhere. In any case, FEMA has now posted a statement on the Web site, stating that it is "in the process of modifying the application" so that people using other browsers and systems can access it.This isn't the first time a government agency has dropped the ball on building accessible, standards-based Web sites. A Copyright Office site being built so that content creators can pre-register certain works for copyright protection will also require Internet Explorer, at least for the time being. In that case, the problem reflected the government's decision to integrate its online tool with a back-end CRM system that won't work with other browsers.

FEMA's restrictions were, of course, both more onerous and less justifiable: By also shutting out Mac users, no matter which browser they used, the site could have caused problems for a small but significant number of Katrina survivors. Corporate politics and technology dogma aside, this was unacceptable.


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

It's both practical and, in many cases, easier for developers to build standards-based Internet applications. Besides making life easier for everyone by allowing access from a veriety of systems and client apps, standards-based sites are far more accessible to people who rely on screen readers and other assistive technologies. In a nation with an aging population and where 10 percent of Internet users rely on some sort of assistive technology, this is a critical issue for any government agency with an online presence.

For most government Web sites, and even for some private-sector sites, accessibility isn't just common courtesy and common sense -- it's also the law. Last month, Tim Berners-Lee and Daniel Weitzner of W3C noted this fact in a letter to the U.S. Copyright Office, regarding its planned pre-registration tool. And while most of us would be content to wait until the next software upgrade allows the office to fix the problem, it seems like only a matter of time before someone with less patience gets a federal judge involved in settling the issue.

Thankfully, common sense prevailed at FEMA: People with enough to worry about won't find themselves jumping through hoops just to fill out a form on a Web site. I hope the Copyright Office follows suit as quickly as possible, and I especially hope other government agencies will take a more far-sighted view when it comes to selecting, buying, and building standards-based Internet technologies.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links