I just found this through one of the mailing lists I subscribe to. It’s a map that covers technologies on the web. It mentions Mordorsoft and Google’s All Seeing Eye, it’s worth checking out:
http://www.flickr.com/photos/psd/1805709102/
http://www.flickr.com/photos/psd/sets/72157602805227511/
http://www.archive.org/details/TheWebIsAgreement
PDF
http://www.archive.org/download/TheWebIsAgreement/web.PDF
This video is a must see (no pun intended) for all who are interested in learning how to build 508 compliant code.
Yahoo! engineer Victor Tsaran introduces you to the fundamentals of the screen reader experience and to his own strategies for accessing web content via the screen-reader interface.
The thing is getting swamped at the moment, but I hadn’t seen this option before but theres “Clean up Markup with HTML Tidy” available.
What is P3P?
P3P is a combination of a machine-readable and human-readable website privacy policy. The standard today is to publish a text privacy policy, but in reality who reads them? They are almost always hard to find and lengthy to read. P3P is supposed to solve this problem.
A P3P implementation consists of two files, an XML formatted document that will be read by the web browser. This XML file contains machine readable statements about how and why the website needs you to accept cookies. The other part consists of a regular, compact, privacy statement formatted in regular HTML.
How does a policy affect the web browser?
When the web browser is presented with a cookie (1st or 3rd party) that either does not have a P3P policy, or if the P3P polity does not match the user’s privacy preferences, the user will be alerted and the cookie will be blocked.
IE6/7 Red Eyeball
Both versions of IE come with a medium privacy setting. A medium setting is described as:
When any of the above items gets triggered, the user gets prompted, IE6 and 7 both flash a red eyeball icon located in the status bar:
For Intervals, we wanted it to disappear, simply because our application is a hosted solution and required cookies in order to function properly. Implementing P3P allowed us to extend our normal HTML privacy policy as well as giving our customers a little more flexibility on what cookies they want to accept.
Our solution consisted of the addition of an HTTP P3P header which points to an XML Reference file. The HTTP header itself contains the compact version of the XML policy, it usually transforms into something like:
“NON DSP ADM DEV PSD IVDo OUR IND STP PHY PRE NAV UNI NOI”
Each code corresponds to a certain statement. NOI for example means: No personally identifiable information (PII) collected.
Implementation
There are many ways to get this implemented, you can either do it yourself or go the service route. I’d say the biggest task is getting your actual privacy policy settings into an XML reference file. Visit some of the links below for more information, the implementations link especially.
Useful Links
I am currently writing this post on Safari on XP. The first thing I did was to check the navigator.userAgent js property.
I don’t know about everyone else out there, but seeing “Windows NT” and “Safari” in a userAgent property is something that I didn’t expect. It gives me both the creeps as well as a little excitement on what’s to come. Excitement would be more users submitting bugs to apple on this browsers crappy editable html javascript implementation, maybe this will get AppleWebKit to fix the bugs faster. What gives me the creeps is it gives me another platform our websites should run under… bittter sweet.
You can download the public beta here.
Update: It seems like most of the showstopper bugs are fixed with this version. With just a little push this very might well be a very good release.
UPDATE II: So I can’t maximize Safari on my RIGHT MONITOR… it just dissapears. Is that Apple trying to send a political subliminal message? ;)
Here’s a great primer for developers who are interested in writing compliant css and html:
…the best thing you can do is give yourself a clean slate. Throw out your assumptions and expectations. For that matter, throw out everyone’s assumptions and expectations. Roll up your sleeves and learn something new. When it comes to layout and production, resolve to remove “but”? and “should”? from your professional vocabulary for a while. Replace them with “how”? and “why”? and commit to meeting your project objectives.
Listamatic is a list definitions repository.
You can view many different types of list definitions here. It just goes to show you the many different ways in which you can write a list through CSS. You can submit your own for others to use as well.
In the latest versions of Microsoft Internet Explorer, Netscape Navigator, and Mozilla (the Open Source, Gecko-based browser whose code drives Netscape Navigator, CompuServe, and other browsing environments), carefully constructed layouts have begun falling apart and expensively engineered behaviors have stopped working. As these leading browsers evolve, site performance continues to deteriorate.
http://www.digital-web.com/articles/999_of_websites_are_obsolete/
A common misconception among many web developers, especially those in the library community, is that a web site must sacrifice a highly designed look in order to be accessible. This is not true. In fact, many sophisticated design elements subtle use of color, multimedia, careful use of large images that some accessibility advocates reject can be profound accessibility enhancements for a general audience. They do not diminish a disabled user’s experience if they are handled properly. If developers build a highly designed site according to web standards and accessibility guidelines, the site will still be accessible.
http://www.libraryjournal.com/index.asp?layout=article&articleid=CA232338&publication=libraryjournal
PROBLEM: DREAMWEAVER 4 FALLS SHORT in its ability to produce wellformed, standardscompliant markup.
SOLUTION: You can easily harness Dreamweaver’s two greatest strengths, its flexibility and its user community, to make it one of the best tools on the market for producing good XHTML. This article will tell you how. With a few tweaks, hacks and extensions, you’ll be able to produce sites that validate, and to clean up legacy pages. Set aside an hour or two, follow these directions, and fall in love with Dreamweaver all over again.
Having wrestled with the best way to track time and manage work at Pelago, we understand how processes should work. We built Intervals to manage chaotic work loads — and to help others do the same.
