WWW2007: Bert Bos on “CSS, 10 Years After”

Note: These are rough notes from the WWW2007 conference.

CSS Level 2 will next week be a candidate recommendation.

The future of the Web page is mobile.  There are 2 mobile profiles.  The new W3C CSS Mobile Profile will be the same as OMAs.

With Print CSS, the goal is to give users the control over the Web page to do the same things you’d normally do with a print document.

The future of css will allow for a grid layout in the design.

CSS is becoming more internationalized.  There are things like vertical text or right to left.

WWW2007: Dave Raggett on “Next steps for HTML Forms”

Note: These are rough notes from the WWW2007 conference.

Now is a good chance to fix mistakes of the Web.

What do people use forms for?  What are the new things?  We need to enable people.

Now to author a web page, you have to be an expert in a lot of things.  What about authoring for normal people?

Today we don’t have an easy way to do required fields, validity tests, simple sums, or dynamic html.   Regular expressions scripting is too difficult.

In 1998, there was the idea of moving towards XML for forms.  This led to XForms.  It used to the MVC, data was XML, and used declarative form logic.   It has been too radical for browser vendors.

There is a new proposal for Web Forms 2.0  Its based around graceful degradation. There is rich controls and many data types.

Most people aren’t Web programmers.  There is the need for high level authoring tools.

HTML is a huge success.  Scripting is powerfull but too difficult.  We need incremental improvements.

Join the HTML WG.

WWW2007: Michael Cooper on “Accessibility Practices for Rich Internet Applications”

Note: These are rough notes from the WWW2007 conference.

Assistive technologies are tools that PWD use.  They transform content, accept input from alternative devices, and require particular semantics.

There aren’t enough semantics in todays languages.  Things other then links and forms need tab order.  Some of these issues have been caused by AJAX and flash.

One practice is to make sure keyboard support is available.  You need to be able to navigate through elements by giving them focus.  Users with disabilities don’t often seen a whole page.  They need to be able to get to another part of a page.

AT needs to be able to gain access to complex widgets, like tree controls, grids, and menus.

AT needs to know about the classic organization of the page, like sections, headers, and groupings.

There needs to be a way to know that content has been updated.   The users should be updated in an effective but non-obtrusive way.

There needs to be a way to identify widgets.

WWW2007: Art Barstow on “Widgets and Web Applications”

Note: These are rough notes from the WWW2007 conference.

The WAF WG started in December 2005.  Its mission is to develop specifications which all for better client-side applications.

Everyone uses widgets.  They’re now coming to the mobile space. They use the massive base of Web developers.  The degree of resources needed is low compared to a java application.

Widgets are client side Web applications that use HTML, CSS, JavaScript, and AJAX.  The W3C is working on defining the packing format, probably ZIP.

There is going to need to be a manifest for whats in the package, like Widget name and permissions.  It’d be helpful to come up with a localization model.   They’re working on how to sign a widget.

Its not in the WAF WG scope to look at platform APIs or mandating the UI.

There has been some gathering of requirements for Widgets.  They did this by looking at the existing Widget Platforms and Engines.  They’ve looked at the current design principles.

There is the Packaging Format spec.  There is also a commitment to make a packaging primer.

WAF WG is also working on XML Binding Language.  It binds some XML to another chunk of XML.  This is codifying existing practices.

XBL could be used to reorder content.  There could be content adaptation for smaller screens or refactored for accessibility reasons.

WAF WG is also working on Read Access for Web Resources.  The problems is that browsers don’t allow cross-site scripting.

A WaSP Interview with W3C’s Judy Brewer on the Status of WCAG 2.0

The W3C‘s Web Content Accessibility Guidelines (WCAG) 2.0 are going to be a great step towards making it easier for people to make Web sites accessible to people with disabilities.

The questions that have been on everybodys mind about WCAG 2.0 are, “When will WCAG 2.0 be finally done? Will normal people be able to read it? How can I better keep track of whats going on with WCAG 2.0 or maybe even get involved?”

W3C Web Accessibility Initiative (WAI) Director Judy Brewer recently did an interview with Jared Smith of the Web Standards Project (WaSP) Accessibility Task Force.

Have you read the interview? What are your thoughts on WCAG 2.0?

Digital Web Article on the Future of HTML

I have to admit that I’ve only half paid attention to and understood the various debates that have been going on about the future of HTML. Most of what has been written has been pretty cryptic, until now. David Andersson wrote a great piece for Digital Web Magazine called, “HTML5, XHTML2, and the Future of the Web.” It’s worth a read.

Have you read the article? What are your thoughts on the future of HTML?