Over the years of being a freelance web designer, I've been developing my own processes for the business of designing websites. One of those processes has been compiling a list of tasks that need to be completed before launching a website, whether it be a new site or a redesign. This list is kept in a spreadsheet which I work through, ticking off each item after the client has given final sign off for the site to go live. I view it as my final quality control procedure and I usually find that the process will highlight a few of the 'little things' that I might have overlooked in general development. Usually nothing too major; more a case of 'dotting all the Is and crossing all the Ts'.
Entries tagged ‘html’
Which is better in links from the search engines' point of view: plain text or images with an
alt attribute that says the same thing? For example, is
<a href="">This is a link</a> better than
<a href=""><img alt="This is a link" src=""></a>?
The technique he outlines makes use of the same image replacement method as outlined in ALA's original Sprites article. The problem with this method however is that it uses a large negative
text-indent to remove the default text from screen, and with images turned off in the browser, you don't see anything. This has accessibility implications not only from the perspective of those with disabilities, but also for those who deliberately turn images off, i.e. people on slower connections or those using handheld devices who are trying to limit the amount of information downloaded to their phone.
When I wrote the original article on how to achieve cross-browser consistency when styling form legends, I noted that there was a bug in the way Firefox handled legends which required an additional
div to be wrapped around the
fieldset with positioning and other styling applied to the
div rather than the
fieldset. The bug appears to still have not been resolved, but as Thierry Koblenz pointed out in the comments on the original article, there is a way to achieve the same effect across browsers that doesn't require the additional
After spending a while on web development forums, you start to see the same questions being asked regularly. So here I'm going to answer some of these common beginner questions and hopefully save me typing answers out repeatedly in the future because I can just refer the poster to here or copy it myself. ;)
Recognise this? Chances are you do. Even if you don’t own a copy of Dreamweaver, it’s likely you would have come across the code it outputs for creating image rollovers in your travels looking at the code of other sites.
I've just written an article on a technique which can be used with column layouts which has been published on Search-This: Two Column Layout With A Twist.
I've been a subscriber to the site for a while (a lot of its contributors and readers also frequent Sitepoint) and a regular commenter, but this is my first published article. Search-This also publishes a range of articles dealing with the spectrum of web development topics, so it's worth checking out.
Following on from my last post in which I mentioned screenreaders (or alternatives) that people might like to try for checking their own sites' accessibilty, and an earlier post in which I listed the extensions I use for web development with Firefox, I thought I'd also list the different tools I use for testing website accessibility.
Last year, Nick Cowie created a podcast on the
<button> and how it is the Open Mobile Alliance (OMA) (authors of the XHTML-MP specification) who have forgotten about it as well.
- Mobile browser usage almost set to overtake desktops
- CMS Review: Processwire
- Get yourself mobile — it’s not as difficult as you think
- More Stash examples
- The Redesign Details — ExpressionEngine
- Relaunch Special
- Have you done something different with the place?
- I’ve got a new blog!
- Adding a link list to TinyMCE with ExpressionEngine
- Redesigning ExpressionEngine sites