W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2013

RE: Current suggestion for subheading isn't accessible

From: Ricci Angela <Angela.Ricci@atos.net>
Date: Tue, 7 May 2013 16:47:05 +0200
To: Ian Yang <ian@invigoreight.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <DEFDCD373CE6DC43AC2DC5ED7923DEE18B7286E90B@FRSPX100.fr01.awl.atosorigin.net>
I usually use <small> instead of <span> in similar cases. I believe it gives to the baseline (or sub-heading) a bit of semantic: it is still the title, but it has lower importance.
I'm not sure how screen readers will treat it, but it is still better than span.

Angela



Angela RICCI
Interaction Designer
(+33) 3 20 60 80 16
angela.ricci@atos.net
ZI Rue de la pointe,
59113 Seclin
FRANCE




-----Original Message-----
From: Ian Yang [mailto:ian@invigoreight.com]
Sent: mardi 7 mai 2013 16:39
To: w3c-wai-ig@w3.org
Subject: Current suggestion for subheading isn't accessible


Please refer to common idioms suggestion in HTML spec:
http://www.w3.org/html/wg/drafts/html/master/common-idioms.html#sub-head


The first example shows an image in which there is one line of text "The Lord of the Rings: The Two Towers". And its suggested HTML markup is <h1>The Lord of the Rings: The Two Towers</h1> The problems with that markup are:
1. It doesn't actually markup the subheading. There is only a heading element (<h1>). And that's because presentation didn't being separated from structure. How the markup was coded was affected by the design (but it shouldn't be). If the line of text consists of a heading and a subheading, then it should be markuped by using two particular HTML elements, and then use CSS to turn them into one line according to the design.
2. Screen reader users have no way to know the subheading. They will regard what they hear as a single heading.

The second example shows an image in which there are two lines of text. The first line is "Ramones" and the second line is "Hey! Ho!
Let's Go". And its suggested HTML markup is <h1>Ramones - <span>Hey! Ho! Let's Go</span> </h1> The problems with that markup are:
1. Still, it doesn't markup the subheading. There is only a heading element (<h1>). A <span> in a heading doesn't make the <span> a subheading. (although you could use CSS to make it looks like a
subheading)
2. Screen reader users have no way to know the subheading. They will regard what they hear as a single heading.


Sincerely,
Ian Yang


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité d'Atos ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Received on Tuesday, 7 May 2013 14:47:37 UTC

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