W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2017

RE: non-landmark forms

From: Jonathan Avila <jon.avila@levelaccess.com>
Date: Wed, 2 Aug 2017 18:43:57 +0000
To: "tink@tink.uk" <tink@tink.uk>, Taliesin Smith <talilief@gmail.com>
CC: Tobias Bengfort <tobias.bengfort@posteo.de>, WAI IG <w3c-wai-ig@w3.org>
Message-ID: <CY1PR0301MB209044863B2EC576FA92DF10F1B00@CY1PR0301MB2090.namprd03.prod.outlook.com>
> and neither will a <form> element with an accessible name. So <form aria-label="this form"> or <form aria-labelledby="that"> will not create landmarks either.

The ARIA working group is claiming this will create a landmark.  This is something we need to provide clear guidance on for the community.

Best Regards,


Jonathan Avila
Chief Accessibility Officer
Level Access, inc. (formerly SSB BART Group, inc.)
(703) 637-8957
Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

-----Original Message-----
From: Léonie Watson [mailto:tink@tink.uk] 
Sent: Wednesday, August 2, 2017 1:27 PM
To: Taliesin Smith <talilief@gmail.com>
Cc: Tobias Bengfort <tobias.bengfort@posteo.de>; WAI IG <w3c-wai-ig@w3.org>
Subject: Re: non-landmark forms

On 02/08/2017 14:56, Taliesin Smith wrote:
> Hi Léonie,
> So just to be clear so that I understand, too.
> In Tobias’s case using the form element without an explicit 
> aria-labelledby attribute, or without an explicit aria form role 
> attribute, would keep the form as a non-landmark form?


The only way to create a form landmark is to use role="form". So <form role="form">, <div role="form">, or (if you're using SVG) <g role="form">, will all create form landmarks.

Using the <form> element on its own does not create a landmark, and neither will a <form> element with an accessible name. So <form aria-label="this form"> or <form aria-labelledby="that"> will not create landmarks either.

It is worth mentioning that using <form aria-label="This form"> or <form aria-labellledby="that"> will not give the form an accessible name either.

So for Tobias' use case, the <form> element on its own is the right solution, unless there is a good reason for giving each form on the page an accessible name in order to tell them apart.

If that is the case, then the only solution is to use the form role, then aria-label or aria-labelledby to provide the accessible name. This will turn every form into a landmark though, which may well turn out to be more hinderance than help to screen reader users!

The code would be something like <form role="form" aria-label="This form">.

Bear in mind that the ARIA design patterns are not talking about situations where implicit element semantics apply. When it talks about a form landmark, it assumes you are using role="form" to explicitly set the role using ARIA. The advice to provide accessible names is therefore also based on the assumption the form role will have been explicitly set.


@LeonieWatson @tink@toot.cafe tink.uk Carpe diem

Received on Wednesday, 2 August 2017 18:44:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 August 2017 18:44:25 UTC