Sorry for this question. Anybody Can help me with some documentation or article about the difference between achecker and w3c validator?
Any info?
thanks
w.
W3C validator checks the markup validity of Web documents in HTML, XHTML, SMIL, MathML, etc. This tool checks the grammar of the document.
achecker is a basic tool to check a website according to WCAG recommendations (web content accessibility guidelines). As WCAG testing requires a lot of manual testing, and there is currently no good accessibility checker, those tools must be considered as indicators.
Related
The data markup Schema.org for search sites like Google, Yahoo!, Bing and Yandex is great for snippets. However, I perceive that most of webmasters use Microdata and almost never use JSON-LD. I learned about JSON-LD recently and I have some doubts:
Could I use it without compability problems with search engine?
There can’t be a general answer:
Each consumer (search engine, tool, etc.) has its own conditions (what it supports for which feature).
Each syntax (JSON-LD, Microdata, RDFa, etc.) has its own advantages and disadvantages.
Specific example to illustrate the problem: Google recommends to use JSON-LD for some of their features, but doesn’t support it for some others (e.g., for their Products Rich Snippet).
For what it’s worth, JSON-LD and RDFa are both W3C Recommendations (while Microdata is part of WHATWG’s Living HTML standard, but no longer under development at W3C). So if you care about this, you might want to consider using RDFa instead of Microdata (see my comparison). RDFa and JSON-LD are, of course, quite different: with JSON-LD you’d have to duplicate your content, while you can reuse it with RDFa.
I wonder why techie giants like Facebook shows many errors when validated in W3C (Link)
Is W3C required?
W3C validation is a good idea, but it is not "required". What could "required" possibly mean? I could call my ISP, get a static IP, set up a server, buy a domain, and configure HTTP to return anything I want and call it HTML if I like.
If you're doing web development and have no reason not to get it to pass W3C validation, then you should. Presumably, Facebook had a reason to ignore it - either they wanted to do something that wouldn't pass, or they didn't want to pay their engineers to make it pass, or the engineers who were responsible for it were incompetent, etc.
It's a good idea to get it to validate to ensure that you're conforming to applicable standards so that your site works well in as many standards-compliant browsers as possible.
You think the W3C validation is bad? Tell your browser to always alert you to Javascript errors, enable Javascript debugging, and go to your favorite sites.
I'd like to tap your experience regarding the use/deployment of a JavaScript powered framework to implement a GUI frontend for different backend tasks.
The framework would have to provide a managable way of displaying arbitrary data fetched from a database (data can be provided in every thinkable way JSON, XML etc.) and allow the manipulation of that data by means of a clean and RESTful API. Prebuilt widgets (tables/lists/dashboard) and UI (drag'n'drop/sorting) would be nice to have but aren't mandatory.
The requirements are:
Open Source (obligatory)
clean and RESTful API to fetch, display and manipulate data
Ability to extend the functionality thru plugins
Standards-compliant (IE does not have to be supported)
Thorough documentation and/or helpful community
I've figured that jQuery's UI framework comes very close to the ideal, though it lacks a decent support of general structures to master a full-fledged application.
I'm interested of what you guys would recommend.
Thanks in advance.
After years of using several of the available frameworks I now use Yahoo's YUI3 (3 - not the older 2) if I can - for "serious" apps. For HTML page enhancements I'm indifferent and may sometimes prefer jQuery.
http://developer.yahoo.com/yui/3/ (BSD license)
What I like about YUI3 are the very "deep" concepts behind it for serious "enterprise level" software development. Regardless of what framework one uses, EVERYONE seriously developing in JS should have viewed (and understood!) the videos on Yahoo Developer Theater, especially the presentations by Douglas Crockford.
http://developer.yahoo.com/yui/theater/
Whenever I want to study a new language, the best way IMO is to see how expert writes code in that language, that is always effecient.
I am looking for that :)
First you should understand that what is AJAX
Ajax is a way of developing Web
applications that combines:
XHTML and CSS standards based presentation
Interaction with the page through the DOM
Data interchange with XML and XSLT
Asynchronous data retrieval with XMLHttpRequest
JavaScript to tie it all together
Simple Ajax Example
AJAX isn't really a language in and of itself, it's used in tandem with other languages to create dynamic web applications. There isn't really a catch-all open source AJAX project that I'm aware of, although there may be some tailored to specific languages. Perhaps if you update the tags to elaborate on the language I can offer some suggestions.
Some resources you may be interested in:
http://api.jquery.com/category/ajax/
http://www.w3schools.com/ajax/default.asp
http://code.google.com/edu/ajax/tutorials/ajax-tutorial.html
Are there any services out there, that can parse a website and give some sort of feedback to how search-engine friendly that website is? And perhaps even suggest changes to the mark-up to improve indexing?
Think W3Cs validation services.
Try Google Webmaster Tools. After you add your site, it will often list "problems" with your site, such as duplicate title tags and meta descriptions, and also things like 404 errors.
If you are a GoDaddy customer you can validate web-crawler friendliness on your hosted sites.
Tools to automate alteration of markup code for any objective are a horribly frightful proposition. Simply write your code correctly the first time. If you have archaic code then it likely has many other problems in addition to SEO, and automatically imposing global changes can expose problems you may not be prepared to address.