background preloader

Rfc

Facebook Twitter

10 Ways To Make Your Site Accessible Using Web Standards | How-To | Smashing Magazine. Advertisement Without argument, one of the most important things to consider when creating a website is that it be accessible to everyone who wants to view it. Does your website play nice with screen readers? Can a user override your style sheet with a more accessible one and still see everything your website has to offer? Would another Web developer be embarrassed if they saw your code? If your website is standards-compliant, you could more confidently answer these questions. Let’s take a look at 10 ways to improve the accessibility of your XHTML website by making it standards-compliant. 1.

Criteria.The Document Type declaration (DOCTYPE) is an instruction that sits at the top of your document. Why do I need it? Okay, so what do I do? XHTML 1.1This is the cleanest way to code your website. Two other XHTML 1.0 declarations exist for niche uses. XHTML 1.0 TransitionalThis is used for pages that need to be viewed on legacy browsers that don’t support CSS. 2. Why do I need it? 3. 4. 5. 6. 7. Request for Comments (RFC) Editor Homepage. Most-Read RFCs. Request for Comments (RFC) Universal Plug and Play Forum.