The Web should be made accessible to as many people as possible, regardless of any disabilities they might have.
Think very carefully before using -webkit-text-size-adjust:none since it will prevent people using WebKit-based browsers from resizing text. Needless to say, that is not user-friendly.
Highlighting some persistent myths about web accessibility.
WordPress likes to put title attributes on just about every link it outputs, which can be annoying and cause accessibility issues. Here is one way of removing them.
Browsers give visited and unvisited links different colours by default for a reason. Make sure you have a really good reason to make them look identical.
Internet Explorer 9 (in beta at the time of this writing), still does not let the user resize text whose size has been specified in pixels.
Does using CSS to hide text - any text, for whatever reason - result in an automatic search engine penalty?
iOS 4 for Apple’s mobile products have improved accessibility features, including support for navigating by WAI-ARIA landmark roles.
Since screen readers run alongside regular web browsers and have no user agent string of their own, there is no reliable way of detecting them.
The longdesc attribute, which can be used to provide a longer description of an image, is currently not included in the HTML5 specification.
If you use the accesskey attribute and specify the same value more than once, browser behaviour is unspecified and varies a lot. Make sure values are unique if you use accesskey.
The Web excels at enabling people to find and share information, but it is not a particularly good platform for creating and delivering “desktop-class applications”.
Having built-in semantics and accessibility in HTML5 is great, but I think we also need specifications like WAI-ARIA that let us add accessibility to less than ideal markup.
An absolute must read for any web designer or developer, even if you think you know everything about progressive enhancement already.
Specifying the natural language of complete and partial HTML documents really does make a difference to users of screen readers that support language switching.
Neglecting to style :focus when you style the :hover pseudo-class can lead to minor inconvenience at best and complete inaccessibility at worst for non-mouse users.
A selection of keyboard shortcuts used to control the VoiceOver screen reader in Mac OS X 10.6 (Snow Leopard).
Very few web browsers allow users to step through the headings on a page. This functionality would benefit keyboard users, so I would like to see more browsers implement it.
When an image is missing or images are disabled, web browsers should completely replace the image with its alt text.
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
- Front-End WordPress Dev: PSDs to Responsive WordPress Themes at 1123Interactive
- Web Developer / Programmer at Electric Pulp (Sioux Falls, SD, So, US)
- PHP Web Developer at Forepoint Ltd (Preston, GB)
- Front-End Developer at Happy Cog (Austin, TX or Philadelphia, PA, Pe, US)
DreamHost web hosting
Use the promo code 456BEREASTREET3 to save USD 20 when you sign up for DreamHost