QnECMS: Quick & Easy Accessible CMS, Weblog and Podcasting Software.

You are here: QnECMS Content Mangement System : About : 50 hot to touch accessible web design tips - the tips no web developer can do without

50 hot to touch accessible web design tips - the tips no web developer can do without

STOP PRESS: QnE is no longer a commercial product - and is no longer being sold from this website.

  • QnE will continue to be developed, though not as a commercial product.
  • Existing clients and licenses will continue to be supported - and all existing agreements will be honoured.
  • if you have any questions about this change please get in touch via the contact form.

Image: 50 hot to touch accessible web design tips. 50 hot to touch accessible web design tips ebook Contents Page

  • Welcome and thanks
  • publisher information
  • about jim byrne
  • 1. Design for machines first, people second!
  • 2. Test the accessibility of your web page with your own web browser.
  • 3. Use relative units when setting css text sizes
  • 4. Don't rely on colour alone to provide important information
  • 5. Ensure links work when javascript doesn't
  • 6. Link text should describe the content linked to
  • 7. Html 4.01 Is the final version of html and it will be around for a while yet
  • 8. Introduce yourself to the web content accessibility guidelines
  • 9. Add a full stop to end of alt attributes and list items
  • 10. Making pdfs more accessible
  • 11. Add alt attributes to spacer images
  • 12. Make forms easier to use by creating a logical tab order
  • 13. Give visitors your content first (not your navigation)
  • 14. Accessible web design is not about creating boring sites
  • 15. Provide additional keyboard access to your web pages
  • 16. Expand your use of abbreviations and acronyms
  • 17. Make a start on those 'legacy' pages
  • 18. Get your 'character encoding' sorted
  • 20. Don't try to control visitors to you site
  • 21. Add structural meaning to image based headings
  • 22. Decide whether your non-text elements are functional, decorative or providing content?
  • 23. How to make printable characters between adjacent links invisible
  • 24. Use absolute size keywords to set the text size on your pages
  • 25. Use favelets to check validation and accessibility of your web pages
  • 26. Structure your menus by marking them up as lists
  • 27. Use html attributes, or css to set web page colors, but don't use both
  • 28. If you need help, ask an expert!
  • 29. Understanding colour contrast and accessibility
  • 30. Use alternative style sheets to give users control of critical elements such as text size or colour on your web pages
  • 32. Check colour contrast by creating a greyscale image of your web page
  • 33. Make html pages created from ms word more accessible
  • 34. Use the free waizilla accessibility checker
  • 35. Use acrobot to catch you acronyms and abbreviations
  • 36. Get the web accessibility toolbar for internet explorer
  • 37. Adding tags to pdf documents improves accessible
  • 38. Use javascript to add default text to input fields
  • 39. Download ready-made style sheets to meet your access needs
  • 40. Associate form fields explicitly with their labels
  • 41. Layout your forms using css instead of tables
  • 42. Web accessibility for deaf people - adding captions or providing transcripts isn't always enough
  • 43. Don't rely on automated tools for checking web accessibility
  • 44. Don't use the statistics defence as a reason to exclude people from your content
  • 46. When a link falls at the end of a sentence always put the full stop outside the anchor tag
  • 47. Start with the assumption that you cannot predict the access needs of your audience
  • 48. How to get your xhtml pages to validate when using blockquote
  • 49. What is the object element for? And what's it got to do with accessibility?
  • 50. How to hide a flash movie from screen readers and keyboard users
  • 51. How to make client-side image maps accessible
  • 52. Develop your sites for a standard compliant browser first then modify for ie/win
  • 53. How to make your pages validate when they include urls with ampersands (&'s) in them
  • 54. The flash satay method to embed flash in your pages and support standards
  • 55. Use a content management system that helps you build an accessible website