The Web should be made accessible to as many people as possible, regardless of any disabilities they might have.
Got a specific accessibility-related challenge that you’d like to tell others about?
Website navigation is a tool that should be kept simple to enable visitors to use it properly.
Please think twice before using multiple columns to display longer articles on-screen.
How to check and improve the readability of your texts.
Use CSS to make “read more” links more accessible to screen reader users.
I’m featured in the latest issue of Swedish design magazine CAP&Design.
Internet Explorer and Safari have similar problems with in-page keyboard navigation.
The Web Developer Toolbar can help you perform some manual accessibility checks.
Chris Heilmann makes a good analysis of most clients’ current attitude to web accessibility.
Screen readers speak content in the order it is in the markup, not in the order it is displayed on-screen.
Russ Weakley covers more than the basics in this one.
Read this if you use ASP.NET.
A discussion on whether it is acceptable for a website to be accessible to people with disabilities but inaccessible to people that use alternative browsing devices or operating systems.
Most PDFs on the web should not be PDFs. But they can be made accessible.
No longer necessary. In fact, don’t do it.
A series of articles on building websites for mobile devices.
Using server-side scripting to make your site faster on mobile devices.
Don’t mess with scrollbars if you want your site to be usable.
A very comprehensive article on the correct use of HTML tables.
Is web accessibility limited to supporting assistive technologies?
Page navigationPage 1 | Page 2 | Page 3 | Page 4 | Page 5 | Page 6 | Page 7 | Page 8 | Page 9 | Page 10 | Page 11 | Page 12 | Page 13 | Page 14 | Page 15 | Page 16 | Page 17 | Page 18 | Page 19 | Page 20 | Page 21 | Page 22 | Page 23
Subscribe / follow
DreamHost web hosting
Use the promo code 456BEREASTREET3 to save USD 20 when you sign up for DreamHost