Accessibility on the web - making your sites available for everone and every technology. Something that developers need to keep in mind from the ground up.
A nice overview of forms from the accessibility perspective, with examples of how to layout and markup a form, the appearance and how the layout appears when using a screen reader. If you have never experienced the web from a screen reader, be sure to check out these examples.
A nice first overview for making accessible forms, covering ideas like using labels, using a logical flow to your html and using a title tag for elements that don't have labels (most often search boxes - a search button is not a label!).
A thourough discussion from 2004 on the state of accessiblity of PDFs, including advice on creating accessible PDFs amd alternatives to PDF files.
Christian Heilmann writes about some of the difficulties surrounding selling accessibility to clients. He really nails this piece in my opinion, and it's worth having this background if you plan on talking to your clients about accessibility.
Picking up where part 1 left off, this instalment deals with grouping information into logical chunks with fieldsets and using the rarely seen <optgroup>.
An overview, some links and a slightly lively discussion on understanding color and accessibility.
From the article:
There are lots of reasons to use accessible design practices in every project. One is that it's simply good design. Sites with consistent design and code and that adhere to Web standards are not only easier to maintain, they're easier to use.
WATS.ca provides Web Accessibility Testing and Services (WATS) and offer a selection of articles from an introduction to accessibility to validation to the use of tabindex and accesskeys. Worth a read for an authoritative point of view.
A nice summary of how, when building an accessible website, you are actually increasing the search engine friendliness of your site. The article outlines 10 different "areas of overlap" between SEO and accessibility.
Charl van Niekerk talks about the little thought about <lang> attribute, discussing how it can be used to increase the accessibility of, and add semantic value to, a document.
I started freelancing by diving in head first and getting on with it. Many years and a lot of experience later I was still able to take away some gems from this book, and there are plenty I wish I had thought of beforehand. If you are new to freelancing and have a lot of questions (or maybe don't know what questions to ask!) do yourself a favor and at least check out the sample chapters.
Like the other books listed here, this provides a great reference for the PHP developer looking to have the right answers from the right people at their fingertips. I tend to pull this off the shelf when I need to delve into new territory and usually find a workable solution to keep development moving. This only needs to happen once and you recoup the price of the book in time saved from having to develop the solution or find the right pattern for getting the job done..