The WCAG (1.0) guideline 4, checkpoint 4.2, about ABBR and ACRONYM, has for a long time been too unclear to implement. The drafts for XHTML 2.0 and WCAG 2.0 seem to have solved most problems.
There is no question that the vast majority of tables on the Web are layout tables, used to structure the visual appearance of the page. Often the structure of tables is remarkably complex, with tables nested in tables as much as seven deep.
I have been playing around with scripting for about six months now. I would by no means call myself a programmer yet, but I have successfully added many scripts to various Web sites. How did I do it without attending any programming classes or immersing myself with programming books? I used free scripts from Web sites. I have found many Web sites that offer scripts for just about anything you can imagine.
HTML is made up of a great many elements, a lot of which are overlooked, forgotten or just unknown to many web designers. Although with a basic knowledge of HTML you can develop a website, to take advantage of many of the advanced features, and to make pages fully compatible, it is useful to learn these less popular tags.
With HTML5 markup in place I started wondering about how CSS would affect things. The first thing I discovered was that Firefox doesn't have much in the way of default styling for the new elements - so setting background colours doesn't have much effect until I added some default styles.
Unlike its predecessors, CSS3 is not a single, monolithic spec, but a collection of modules all of which are at different levels of completeness. For instance the selectors module became a candidate recommendation in November 2001 and is already widely supported. In this post I'm going to be experimenting with the Backgrounds and Borders module and the Transitions module, mostly because the recent Firefox 3.5 release includes improved (but still experimental) support for some of the more interesting bits of it.
There are some new CSS3 features supported in the latest Chrome release and Firefox alpha which make this worth a second post. This time I'm going to focus on background sizing, CSS gradients and RGBA colours.
Ajax is an awesome technology that is driving a new generation of web apps, from maps.google.com to colr.org to backpackit.com. But Ajax is also a dangerous technology for web developers, its power introduces a huge amount of UI problems as well as server side state problems and server load problems.
Many sites that present tabular data use alternating background colors to increase the readability of that data. And as I developed a site, I realised I wanted to do that, too. The problem? In my case the table was not generated by a server side application or script of which you can find numerous examples on the Web.
So you have an XML document. You’ve also been a good little web developer and used style sheets to control what your document looks like. You’ve even gone the extra mile and created several alternative style sheets to show how hardcore you are. Great. But now you need a cross–browser way to dynamically switch between the style sheets.
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.
For most end-users, the debate over Flash is largely a debate about web video. Yes, Flash is used in other ways — for web-based games and ever-decreasingly in website design — but thanks in large part to YouTube, Flash is most commonly associated with web video. Web video is overwhelmingly encoded in H.264. Not only is the H.264 codec the default encoding setting for practically every video service online, it is also by and large the default codec for raw video from digital video cameras.
This site offers a unique approach to contextual navigation, and one that has gotten the attention of many reviewers. From the site: 'ArtandCulture.com is a dynamic destination that delivers unique access to the best arts and cultural content and related products available on the web today....focused on creating the context that makes information truly meaningful.' In this review, I'll focus on some of the interesting navigation strategies the site presents.
My client wanted screen shots in their CHM, but the screens were very large thus creating problems when printing a topic. With some help from Dave Gash, I got the large screen shots to open at 50% size, with a function for the user to resize them to 100% either all at once or one at a time. The function also toggled back to 50% at the user's discretion. This solved the problem of large screen shots in the online help, while allowing error-free printing to occur.
Describes an alternative to automatic page refresh in HTML. Automatic page refresh can confuse users with cognitive disabilities when a page reloads without the user's request. This article provides you with instructions on how to apply explicit manual control of page refreshing.
Web documents are nothing more than Source. For all of the inspiration, thought, and sweat that might go into a page, it is merely a mess of characters that happens to contain a lot of brackets. After five and a half years of actively building pages, it's occurring to me that a lot of developers haven't figured this out. What I see is not what they get.