W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2014

RE: Success criteria speak for themselves

From: Homme, James <james.homme@highmark.com>
Date: Fri, 21 Feb 2014 15:49:33 +0000
To: "Bourne, Sarah (ITD)" <sarah.bourne@state.ma.us>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <BF85B26B8ED7B647ACAD9C68E89DA55461B4EC9D@HMBREXMP03.highmark.com>
This post makes me think that I hope that there is support in screen readers for CSS content creation, because XSL could pass this stuff into the content and have it picked up by assistive technology. As a glorified user, I may be mixing up what technologies can do. I hope my shoe is clean, in case it's in my mouth.


-----Original Message-----
From: Bourne, Sarah (ITD) [mailto:sarah.bourne@state.ma.us]
Sent: Friday, February 21, 2014 10:31 AM
To: w3c-wai-ig@w3.org
Subject: RE: Success criteria speak for themselves

There are semantics and there are semantics.  The essence of this debate is that HTML has some very rudimentary handling of what I'll call "content semantics" - using tags to impart information about the nature of the content.  Headings, lists, tables, etc., deal with how the information is organized, which I'll call "architectural semantics".  (And I'm sure there are those in the semantics field who would like to debate those terms. <smile> But those are the terms I'm using here.)

Architectural semantics has very good support in screen readers overall, blithely ignoring product-specific glitches. General browser support - to benefit all users - is lagging, but there has been progress, such as Firefox extension(s?) to expose headings and ARIA landmarks.  And there have always been keyboard shortcuts to discover links and form fields.

Content semantics is not well supported by either AT or browsers. Serious use of content semantics - harvesting and analysis - is pretty much limited to machine use of content, rather than human use.  An example of this that should be familiar is Google and Bing using tagged content for enhanced content display in search results. The rudimentary tags in HTML are insufficient for anything very interesting.  For this type of use, other W3C specifications are pulled into play, such as RDF.  And work is continuing outside the W3C, as well.  See for instance schema.org and http://lov.okfn.org/ (Linked Open Vocabularies.)  The W3C recently re-organized some of their efforts in this area into a new "W3C Data Activity" (see at http://www.w3.org/2013/data/ .)

Rather than fretting about browser and AT handling of ancient but rudimentary content semantics tags, we might better look at what support for discovery and display of the more advanced technologies in the content semantics area would benefit any user, whether they use AT or not.

Sarah E. Bourne
Director of Assistive Technology
Information Technology Division
Commonwealth of Massachusetts
1 Ashburton Pl. rm 1601 Boston MA 02108


This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark, its diversified business, or affiliates.
Received on Friday, 21 February 2014 15:50:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:50 UTC