I do get what you're saying but I think you're using a much too narrowly defined definition of semantics when you describe it as defining "core meaning". This is going to just sound like so much bike shedding but semantics is more than just the core meaning and semantics also doesn't mean that an element's meaning is carved in immutable stone. Semantics is actually about deriving the intended meaning using the available rules of a given language. One to the sets of rules we have to clarify intended meaning of an HTML element is the WAI-ARIA specification. In the same way that Microdata may alter or refine the "core meaning" (or, initial meaning) so too can we use wai-aria to bring greater clarity to our intended usage for a given element. That it's implemented primarily by assistive technologies doesn't alter the fact that it's a clearly defined specification that does alter the semantic meaning of its element. In fact refining "core meaning" of different elements is exactly what wai-aria roles are designed to do.
Using the standardised toolsets for the jobs they are designed to do is exactly the point of having these new toolsets in the first place. See also: Microdata. Cheers, S -----Original Message----- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Russ Weakley Sent: Monday, 5 March 2012 4:47 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] list heading - best practice? > <h1 id="list_title">The list title<h1> > <ul aria-labelledby="list_title"> > <li>...</li> > </ul> > That way the semantic connection between the list and the heading is kept > which I think is the purpose of what you're wanting, yes? > Cheers, > S > I hate to nit-pick, but I'd argue that the aria-labelledby does not really change the semantics of an element. The "semantics" of an element is about defining the element's "core meaning". The core meaning of an <h1> is that it is a level 1 heading. In the case above, the labelledby attribute "exposes" the content inside the heading (via the accessibility API) and associating this content with the unordered list. So, these elements will now have additional meaning for Assistive Devices that support ARIA. However, the attribute does not change the "core meaning" of either of the elements. Does this make sense? Russ ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ******************************************************************* - Please consider the environment before printing this e-mail. The information contained in this email and any attachment is confidential and may contain legally privileged or copyright material. It is intended only for the use of the addressee(s). If you are not the intended recipient of this email, you are not permitted to disseminate, distribute or copy this email or any attachments. If you have received this message in error, please notify the sender immediately and delete this email from your system. The ABC does not represent or warrant that this transmission is secure or virus free. Before opening any attachment you should check for viruses. The ABC's liability is limited to resupplying any email and attachments. ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
