This slideset is designed for Opera, some features may only be available in the Opera Video Builds. However the basic content should work in any browser.
To see this in presentation mode using Opera, simply select "View" ->"Full Screen". To see how all this is done, view the source...
Talk contents
Web history > pre-dotcom crash
<img>
in Mosaic beta. Now 99.57% (MAMA)Research by Opera's MAMA analyser shows that 99.57% of pages have an image applied by markup of some description
Web history > accessibility and HTML 5
2004: WHAT-WG is Web Hypertext Application Technology Working Group. "Work on HTML5 originally started in late 2003, as a proof of concept to show that it was possible to extend HTML4's forms to provide many of the features that XForms 1.0 introduced, without requiring browsers to implement rendering engines that were incompatible with existing HTML Web pages. At this early stage, while the draft was already publicly available, and input was already being solicited from all sources, the specification was only under Opera Software's copyright.
In early 2004, some of the principles that underly this effort, as well as an early draft proposal covering just forms-related features, were presented to the W3C jointly by Mozilla and Opera at a workshop discussing the future of Web Applications on the Web. The proposal was rejected on the grounds that the proposal conflicted with the previously chosen direction for the Web's evolution.
Shortly thereafter, Apple, Mozilla, and Opera jointly announced their intent to continue working on the effort. A public mailing list was created, and the drafts were moved to the WHATWG site. The copyright was subsequently amended to be jointly owned by all three vendors, and to allow reuse of the specifications.
In 2006, the W3C expressed interest in the specification, and created a working group chartered to work with the WHATWG on the development of the HTML5 specifications. The working group opened in 2007. Apple, Mozilla, and Opera allowed the W3C to publish the specifications under the W3C copyright, while keeping versions with the less restrictive license on the WHATWG site." http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#history0
Web standards > Opera involvement
25+ employees work on standards
The Web Standards Curriculum provides resources and Opera Labs examples of emerging technologies
Web standards > Why standards?
"The Web is the platform"
Developers can validate; separate content and presentation - means specialisation and maintainability.
For owners, more maintainability; smaller pages; better SEO
Users: light-weight; interoperable; more likely accessible
Web standards > Future contenders
And more!
Accessibility > Why bother
"For me being online is everything. It's my hi-fi, my source of income, my supermarket, my telephone. It's my way in." Mike, gamer and freelance technology writer with Cerebral Palsy
See AbilityNet video's of people with disabilities using the web
Accessibility > who, what how
Who it affects, how people access and what makes this work:
Accessibility > WCAG
A set of guidelines, not a specification, developed by the Web Accessibility Initiative (WAI)
See W3C's Web Accessibility Initiative for guidelines and details
.Accessibility > basics
Accessibility > Images
alt="xxx"
Accessibility > Headings
Accessibility > Ajax
HTML 4 designed for a mostly static web, doesn't scale to today's web
Accessibility > WAI ARIA
Web Accessibility Initiative Accessible Rich Internet Applications is the fix, it describes:
Accessibility > usability
Disabled users are the ultimate user tester
Accessibility > SEO
"SEO naturally takes care of accessibility because Google is the biggest blind user in the world" The Blind Billionaire?
See Legal and General case study in the UK
Technologies > HTML 5
HTML 4 great for documents...not suited for web apps
article
, footer
, aside
)<video>
<canvas>
<canvas>
Technologies > HTML 5 > Canvas
"Immediate" Vector Graphics
(You can't manipulate them)
HTML 5 > Web forms 2.0
More robust forms
Easier to put together standards control archetypes that are complicated with HTML 4.x.
<input type=date>
:
<input type=range>
:
HTML 5 <video>
Current way to embed video:
<object width="425" height="344">
<param name="movie" value="http://www.youtube.com/v/LtfQg4KkR88&hl=en&fs=1"></param>
<param name="allowFullScreen" value="true"></param>
<embed src="http://www.youtube.com/v/LtfQg4KkR88&hl=en&fs=1" type="application/x-shockwave-flash"
allowfullscreen="true" width="425" height="344"></embed>
</object>
HTML 5 <new code>
Badass sexy new way
<video src="video.ogv"
controls
autoplay
poster="poster.jpg"
width="320" height="240">
<a href="video.ogv">Download movie</a>
</video>
HTML 5 <video>
Technologies > New Opera builds
Some demonstrations need an Opera experimental build.
To learn more read All together now: Video, 3D, File access.
Opera Dragonfly > Inside Opera Dragonfly
Opera Dragonfly > What Opera Dragonfly does
Try it in Opera 9.5 +
Tools -> Advanced -> Developer Tools.
Also try the Debug Menu.
Opera education
End credits!