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:
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?
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:
- Blocks third-party cookies that save information that can be used to contact you without your explicit consent
- Restricts first-party cookies that save information that can be used to contact you without your implicit consent
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:
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.
I am currently writing this post on Safari on XP. The first thing I did was to check the navigator.userAgent js property.
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.
- Everything you know is wrong… sort of…
- It’s not going to look exactly the same everywhere unless you’re willing to face some grief… and possibly not even then
- You will be forced to choose between the ideal and the practicable
- Perfection is not when there’s nothing to add, but when there’s nothing to take away
- Some sites are steaming heaps of edge cases
- Longer lead times are inevitable
- Coherent and sensible source order is the best of Good Things
- Descendant selectors are the beginning and end of genuinely powerful CSS rules
- In the real world, stylesheet hacks will get your project across the finish line
- Working around rendering bugs is like playing Whack-a-Mole
- When you’re drowning in CSS layout problems, make sure of the width and height of the water, float without putting up a struggle, and get clear of the problems
- Background images will make the difference between the plain and the tastefully embellished
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.
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.
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.