How to Select the Perfect Image Format to Optimize Your Website
Is Using SVG Images Good for Your Website's Performance?
What Sort of Hosting Should I Choose for My Website?
Five CSS Performance Tools to Speed up Your Website
Cut the File Size with These Three HTML Minification Tools
Seven Ways You Can Place Elements Using CSS Grid Layout
Increasing Productivity by Slowing Down, with Jason Lengstorf
Retrofit Your Website as a Progressive Web App
How You Can Use HTML5 Custom Data Attributes and Why
Why Every Business Needs a Website
What is HTTP/2?
I Need a Website. What Do I Need to Know About Hosting?
TestCafe: Easier End-to-end Web App Testing with Node.js
How to Order and Align Items in Grid Layout
Managing Code Components with Bit
Interview with Kris Borchers, JS Foundation Executive Director
Introducing Portfolio WordPress Theme – and the Design Decisions Behind it
Tech Stacks, Frameworks, Being Creative, and Being Real, with Tim Holman
The State of PHP MVC Frameworks in 2017
Front-End Tooling Trends for 2017
What Tutorials Don't Tell You: How to Approach Projects
Open Your Data Up to Bots Using Microdata
Microdata is another technology that’s rapidly gaining adoption and support, but, unlike WAI-ARIA, it’s technically part of HTML5. Although still early in development, it’s worth mentioning the Microdata specification here, because the technology provides a peek into what may be the future of document readability and semantics.
In the spec, Microdata is defined as a mechanism that “allows machine-readable data to be embedded in HTML documents in an easy-to-write manner, with an unambiguous parsing model.”
With Microdata, page authors can add specific labels to HTML elements, annotating them so that they can be read by machines or bots. This is done by means of a customized vocabulary. For example, you might want a script or other third-party service to be able to access your pages and interact with specific elements on the page in a certain manner. With Microdata, you can extend existing semantic elements (such as
figure) to allow those services to have specialized access to the annotated content.
This can appear confusing, so let’s think about a real-world example. Let’s say your site includes reviews of movies. You might have each review in an
article element, with a number of stars or a percentage score for your review. But when a machine comes along, such as Google’s search spider, it has no way of knowing which part of your content is the actual review—all it sees is a bunch of text on the page.
Why would a machine want to know what you thought of a movie? It’s worth considering that Google has started displaying richer information in its search results pages, in order to provide searchers with more than just textual matches for their queries. It does this by reading the review information encoded into those sites’ pages using Microdata or other similar technologies. An example of movie review information is shown below.