Comments on: Signpost forms with headers http://accessibilitytips.com/2008/03/10/signpost-forms-with-headers/ A collection of tips, guidance and practical suggestions in developing accessible websites Thu, 14 Jan 2010 17:51:43 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Isofarro http://accessibilitytips.com/2008/03/10/signpost-forms-with-headers/comment-page-1/#comment-43 Isofarro Sat, 15 Mar 2008 19:02:36 +0000 http://www.wp-dev.isolutia.com/?p=14#comment-43 Kilian asks: "Excuse me, but isn't the legend element used for *exactly* this purpose?" No. Fieldset legends are not read out while the screen reader user is scanning the page in headers navigation mode. The fieldset legend comes into play when the user is in forms mode, and gets prefixed in-front of every field within the fieldset. Kilian asks: “Excuse me, but isn’t the legend element used for *exactly* this purpose?”

No. Fieldset legends are not read out while the screen reader user is scanning the page in headers navigation mode.

The fieldset legend comes into play when the user is in forms mode, and gets prefixed in-front of every field within the fieldset.

]]> By: Kilian Valkhof http://accessibilitytips.com/2008/03/10/signpost-forms-with-headers/comment-page-1/#comment-42 Kilian Valkhof Sat, 15 Mar 2008 16:12:12 +0000 http://www.wp-dev.isolutia.com/?p=14#comment-42 xcuse me, but isn't the legend element used for *exactly* this purpose? According to the html4.01 spec: "The LEGEND element allows authors to assign a caption to a FIELDSET. The legend improves accessibility when the FIELDSET is rendered non-visually." xcuse me, but isn’t the legend element used for *exactly* this purpose?

According to the html4.01 spec: “The LEGEND element allows authors to assign a caption to a FIELDSET. The legend improves accessibility when the FIELDSET is rendered non-visually.”

]]> By: Andrew Green http://accessibilitytips.com/2008/03/10/signpost-forms-with-headers/comment-page-1/#comment-41 Andrew Green Tue, 11 Mar 2008 12:20:08 +0000 http://www.wp-dev.isolutia.com/?p=14#comment-41 That's the first time I've heard the suggestion to have an h2 before an h1 -- I'd always assumed such a thing would count as skipping a level. In fact, to be honest, I'm still not sure that it doesn't. I have, however, heard the recommendation to only have a singe h1 per page before, but I've never seen a really compelling rationale for it, other than the notion that a hierarchy only has a single root. Let's say you had a blog post, and had marked up the title of the post in an h1. Let's further say that you had a footer listing other posts on the site, in categories, or by popularity, or whatever. The footer has a heading "Other posts on this site". On the one hand, you could mark up that heading as an h2, since you've already used an h1 on the page. On the other, it's not exactly a subheading of the main topic of the page, more an adjunct to it, so it seems (on the face of it) meaningful to use another h1 instead. I'm genuinely unsure which side of that fence I'm on. Cheers Andrew. That’s the first time I’ve heard the suggestion to have an h2 before an h1 — I’d always assumed such a thing would count as skipping a level. In fact, to be honest, I’m still not sure that it doesn’t.

I have, however, heard the recommendation to only have a singe h1 per page before, but I’ve never seen a really compelling rationale for it, other than the notion that a hierarchy only has a single root.

Let’s say you had a blog post, and had marked up the title of the post in an h1. Let’s further say that you had a footer listing other posts on the site, in categories, or by popularity, or whatever. The footer has a heading “Other posts on this site”.

On the one hand, you could mark up that heading as an h2, since you’ve already used an h1 on the page. On the other, it’s not exactly a subheading of the main topic of the page, more an adjunct to it, so it seems (on the face of it) meaningful to use another h1 instead.

I’m genuinely unsure which side of that fence I’m on.

Cheers Andrew.

]]>