When you build websites that rely on cookies and they are expected to work with privacy settings other than default, you’ll have to deal with P3P. Read on to find out about the cornerstones of the Platform for Privacy Preferences, and get your hands dirty with an example guiding you from empty hands to a complete basic implementation.
The World Wide Web Consortium (W3C), along with other groups and standards bodies, has established technologies for creating and interpreting web-based content. These technologies, which we call 'web standards', are carefully designed to deliver the greatest benefits to the greatest number of web users while ensuring the long-term viability of any document published on the Web. Designing and building with these standards simplifies and lowers the cost of production, while delivering sites that are accessible to more people and more types of Internet devices. Sites developed along these lines will continue to function correctly as traditional desktop browsers evolve, and as new Internet devices come to market.
Ever wonder about that mysterious Content-Type tag? You know, the one you're supposed to put in HTML and you never quite know what it should be? I've been dismayed to discover just how many software developers aren't really completely up to speed on the mysterious world of character sets, encodings, Unicode, all that stuff.
Accessibility is one of the fundamentals of the Web, so how people who claim to be passionate about the Web and say that they deliver high quality can choose to ignore it is beyond me.
Web developers interested in accessibility issues often look to WAI-ARIA to bridge the accessibility gap created by ubiquitous scripting and make web applications more accessible to blind and visually impaired users. But can we recommend WAI-ARIA without reservation? Are there times when appropriate semantic HTML elements are preferable to custom widgets?
It's been a long trip, but we’re almost out of the dark. We finally have browsers that offer substantial support for several technologies established by the World Wide Web Consortium (W3C) and other standards bodies. Designers and developers can use many core features of XHTML and CSS and sometimes DHTML without worrying about the hazards of cross–browser chicanery. As browsers have evolved, it’s become easier to comply with the W3C’s Web Accessibility initiative (WAI) and, in the United States, with the amendments to Section 508 of the Rehabilitation Act of 1974 (commonly called “Section 508”).
As published the W3C XML Schema specification references XML 1.0 explicitly, and incorporates by reference certain key definitions, in particular those of the 'Char', 'Name' and 'S' character classes. XML 1.1 changes the contents of these classes, so although nothing in the existing XML Schema specification specifically bars infosets produced by XML 1.1 conformant parsers, such infosets, if they exploit any of the relevant changes in XML 1.1, will not be accepted as valid by conformant XML Schema 1.0 processors.
I fully acknowledge that a whole lot of very clever thinking went into the construction of Acid3 (as was true of Acid2), and that a lot of very smart people have worked very hard to pass it. Congratulations all around, really. I just can’t help feeling like some broader and more important point has been missed.
It is six months since the release of WCAG 2.0 and I thought it might be interesting to see how extensively it has been adopted as a bench mark for determining web content accessibility. Over this time, I have felt that the rate of adoption has been relatively slow and the number of countries and other regulatory authorities now using WCAG 2 is lower than I expected.
XSLT stylesheets are designed to transform XML documents. Coupled with Java extensions, stylesheets can also be a powerful complement to XML Schema when grammar-based validation cannot cover all the constraints required. In this article, Peter Heneback presents the case for validating documents using XSLT with Java extensions and provides practical guidance and code samples.
The contribution deals with the transposition of projects on the basis of the AECMA-1000D-specification. The author explains problems which exist outside aeronautics with the application of this specification.
Please don't confuse affordance with perceived affordances. Don't confuse affordances with conventions. Affordances reflect the possible relationships among actors and objects: they are properties of the world. Conventions, on the other hand, are arbitrary, artificial and learned. Once learned, they help us master the intricacies of daily life, whether they be conventions for courtesy, for writing style, or for operating a word processor. Designers can invent new real and perceived affordances, but they cannot so readily change established social conventions. Know the difference and exploit that knowledge. Skilled design makes use of all.
On top of the usual frustrations with poor, incomplete, and incorrect implementation of standards and typically buggy and poorly-supported programs, add my frustration with trying to integrate these tools with other similarly joyful tools and you can see that my job is a recipe for bitterness and pain.
It has become evident to me that some of my previous comments about HTML 5 and what is going on in the HTML Working Group are the result of misunderstanding and overreacting on my part. I no longer think things are quite as bad.
When I first read about the AVCHD format with its use of MPEG4-AVC (H.264) video compression at a maximum of 24 mbps versus HDV which uses the older MPEG-2 format at 25 mbps, I was very excited about the new format. My enthusiasm dampened when I read the fine print that actual AVCHD implementation only uses 13 to 17 mbps MPEG4-AVC for compatibility with cheaper storage devices. Take a look at the screenshots below and it pains me to see how much detail is lost in the newer HD format.
I find that many designers give much more of their time to learning the latest standards trick than learning the latest “designing for users” trick. Here are a few reasons why this may be so.
The adhoc way in which much of the web was developed has created a dilemma for web designers: should websites comply with standards, ensuring accessibility, or break the rules and work with older browsers? At this moment, the answer is simple: Websites should work with older browsers.
Now that the release of ARIA is approaching, let’s take a look at how ARIA fits within progressive enhancement strategy. Can we use ARIA in a way that respects progressive enhancement? Can we use ARIA in ways that ensure we have a working solution at every level?
It was just two years ago that Microsoft’s Internet Explorer web browser controlled 67 percent of the worldwide market, according to data from web analytics company StatCounter. It has been all downhill from there. According to the the latest data from the company, last month, September 2010, marked the first time IE fell below the 50 percent share mark in the past decade.
User interface standards can be hard to use for developers. In a laboratory experiment, 26 students achieved only 71% compliance with a two page standard; many violations were due to influence from previous experience with non-standard systems. In a study of a real company's standard,developers were only able to find 4 of 12 deviations in a sample system, and three real products broke between 32% and 55% of the mandatory rules in the standard. Designers were found to rely heavily on the examples in the standard and their experience with other user interfaces.
Auditing and enforcing compliance with P&P content should not be the responsibility of a P&P group or included in the job description of a P&P practitioner. However, the charter or job description may state that P&P practitioners are responsible for supporting compliance efforts.
Managing flow content can get unwieldy—too many class selectors can become a specificity headache, nested styling can get redundant, and content editors don’t always understand the presentational markup. Heydon Pickering offers an unexpected option for handling cascading styles more efficiently: a variation on the universal selector.