[This is the reply post to shanX's reply post regarding my "Making Websites for ALL" post.]
This will be a short & sweet post as I’m struggling with time these days. Lots of work to finish but still have 24 hours per day. Now the time is 12.58 am, and I have to get up early in the morning.
Here goes my 10 points…
- Web standards are standards that reduce the cost and complexity of development while increasing the accessibility and long-term viability of any site published on the Web.
- Yes, I also prefer to code by hand.
- Per HTML and XHTML standards, a DOCTYPE (short for “document type declarationâ€) informs the validator which version of (X)HTML you’re using, and must appear at the very top of every web page. DOCTYPEs are a key component of compliant web pages: your markup and CSS won’t validate without them.
- An especially useful feature XHTML inherits from its XML underpinnings is XML namespaces. With namespaces, authors or communities of authors can define their own XML elements, attributes and content models to mix within XHTML documents. This is similar to the semantic flexibility of the ‘class’ attribute from HTML, but with much more power. Some W3C XML namespaces/schema that can be mixed with XHTML include MathML for semantic math markup, Scalable Vector Graphics for markup of vector graphics, and RDFa for embedding RDF data.
- HTML Versus XHTML
- HTML 5 is still a working draft with major knows issues.
- When consider mobile web browsers table layout is way out.
- Semantic markup is the future today
- We are fighting for standards which ensure simple, affordable access to web technologies for all.
- We have to think as a user not as a developer when making a website as end of the day site is access by different type of users.
To learn more about web standards go to my Web standards round-up post.
I’m not good at writing at ALL, but hope my series of posts regarding web standards will help anyone who want to make a web better place for ALL.
Sri lanka Web Standards
Looks like you have got into a little fight. I like standards. It helps me read code/html easier. I even hope there is a formatting standard for html so I can read it more easily.
Convincing web developers is one thing. Most WYSYWIG developers will fight before they edit html my hand. I have been editing html in eclipse ide and notepad . I need a bit of color than notepad.
I haven’t used Dreamweaver or consider creating a site with plain html files in ages. Its just too painful.
The second thing is showing higher level users the benefits of web standards. If I tell a client that I could spin off a few of their web application screens over to a mobile phone view in no time they appreciate it.
Developers can nit pick for ages on small things like inline or second line curly braces. Pick your fights, convince who you can and keep learning.
@Dilantha
Yes, when you use it you will experience actual benefits of those
Me also not much good at writing and yeah, your posts will be enlightening to webmasters