W3C

Browsers and Authoring Tools

Web agents are intended to serve users. In this section you will find information useful when designing browsers and authoring tools, as well as search engine bots, aggregators, and inference engines.

Browsers Header link

The most common tool to access the Web is the browser. This is the focal point of many technologies.

Authoring Tools Header link

The Web gave the possibility for each of us to create content at a low cost and without too much constraints.

News Atom

An updated Authoring Tool Accessibility Guidelines (ATAG) 2.0 Working Draft was published 29 October 2009. It includes a revised supporting note "Implementing ATAG 2.0". ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content Accessibility Guidelines (WCAG) 2.0. ATAG also defines how to make authoring tools accessible so that people with disabilities can use them. WAI encourages you to review ATAG 2.0 and submit any comments. See: Call for Review: ATAG 2.0 Working Draft updated, Authoring Tool Accessibility Guidelines (ATAG) Overview. Please send comments by 30 November 2009. (2009-10-29)

WAI has published a Last Call Working Draft of the Evaluation and Report Language (EARL) 1.0 Schema, updated Working Drafts of HTTP Vocabulary in RDF 1.0, Representing Content in RDF 1.0, Pointer Methods in RDF 1.0, Evaluation and Report Language (EARL) 1.0 Requirements, and a First Public Working Draft of the Evaluation and Report Language (EARL) 1.0 Guide. EARL provides a format for expressing test results, such as those generated by Web accessibility evaluation tools, using a vendor-neutral and platform-independent format. WAI encourages you to review EARL 1.0 documents and submit any comments. See: Call for Review: EARL 1.0 Last Call Working Draft e-mail, Evaluation and Report Language (EARL) Overview. Please send comments by 30 November 2009. (2009-10-29)

Richtlinien für barrierefreie Webinhalte (WCAG) 2.0, the German Authorized Translation of Web Content Accessibility Guidelines (WCAG) 2.0, is now available, following completion of the W3C Authorized Translations process. WAI encourages translating WAI documents in all languages. See: WCAG 2.0 Translations for a list of other completed and planned translationsWCAG 2.0 German Authorized Translation Published e-mail (2009-10-29)

Version 5.2 of the Unicode Collation Algorithmhas been released. This version resynchronizes the Unicode Collation Algorithm with all of the updates for the Unicode Standard, Version 5.2.

The rest of this post is taken from the Unicode Consortium's release notification and details changes and issues for implementations.

  • The text of UTS #10 has been updated. Among other changes, the revised text for UTS #10 makes it clear that the BASE for implicit generation of weights for Han characters does not include unassigned code points.
  • There are small changes in Gujarati, Telugu, Malayalam (including weighting for chillus), Tamil, and Sinhala. While these changes move in the direction of expected behavior, good results will only come from tailoring for particular languages, such as with CLDR.
  • There have been significant changes to the ordering of many combining marks. Many combining marks that are not in customary use in modern languages now have the same secondary weight, and will only be distinguished on a fourth level, by code point ordering. This can be seen by looking at the Unicode Collation Charts (http://unicode.org/charts/collation/). In 5.2, many characters now have a white background, indicating that they sort exactly the same as the previous character, unless a 4th (codepoint) level is used.
  • Implementations of UCA should take note that the increased number of characters may cause overflows if the implementing code makes certain assumptions or optimizations. This can result either from the new character additions (which increase the number of distinct weights in the table) or because of changes in the way the weights, particularly for secondary weight values, are assigned in the table. The latter change may result in unexpected numbers of characters having the same weight.

Along with the redesigned W3C website, we have a new Accessibility page that introduces the what, why, where, and how of web accessibility. Read what it says about how the impact of disabilities can be radically changed for people using the Web when websites, web technologies, and web tools are properly designed. (2009-10-14)

Comments are being sought on this article prior to final release. Please send any comments to www-international@w3.org( subscribe). We expect to publish a final version in one to two weeks. [search keys: qa-choosing-language-tags]

This tutorial was updated to incorporate changes made to BCP 47 by the recent publication of RFC 5646. Changes to BCP 47 include the introduction of extended language subtags, and the addition of ISO 639-3 language subtags, bringing the total number of subtags in the registry to almost 8,000.

Translators should consider retranslating the whole tutorial. [search keys: article-language-tags]

In order to help the community provide accessible multimedia, W3C made public it's internal Multimedia Accessibility FAQ. The FAQ provides some practical advice on: What do I need to do to make audio and video accessible? How do I get a transcript for my media? How do I do captions? Where can I get more information? W3C's formal guidance on accessible multimedia is provided in Web Content Accessibility Guidelines (WCAG) 2.0. (2009-10-08)

On 1st October, Unicode 5.2 was released! The data files, code charts, and Unicode Standard Annexes for this version are final and are posted on the Unicode site.

For Unicode 5.2, the core specification is no longer just a delta document applied to the book; instead, the entire core specification,with all textual changes integrated, will be available on the Unicode site. As of this announcement, the first five chapters are available; the other chapters will follow soon

For full details about what is new or changed in this release, see the version documentation for Unicode 5.2.

Thanks to the Spanish Translation Team, Spanish Translation US, the following articles have been translated into Spanish.

[search keys:  qa-what-is-encoding qa-setting-encoding-in-applications]

Talks and Appearances Header link

  • 2009 27 NOV

    Reaching Your Audience with an Accessible CMS

    by Shadi Abou-Zahra

    DrupalCamp Vienna

    Vienna, Austria

  • 2010 28 JAN

    Web Accessibility Promotion and Advocacy: Approaches and Resources

    by Shawn Henry

    ATIA 2010 Orlando

    Orlando, FL, USA

  • 2010 29 JAN

    Web Accessibility Standards and Guidelines Update 2010

    by Shawn Henry

    ATIA 2010 Orlando

    Orlando, FL, USA

See also the full list of W3C Talks and Appearances.