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

RE: non-landmark forms

From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Date: Wed, 2 Aug 2017 16:55:38 +0000
To: ALAN SMITH <alands289@gmail.com>, "Gunderson, Jon R" <jongund@illinois.edu>, Phill Jenkins <pjenkins@us.ibm.com>
CC: Jonathan Avila <jon.avila@levelaccess.com>, Taliesin Smith <talilief@gmail.com>, "tink@tink.uk" <tink@tink.uk>, Tobias Bengfort <tobias.bengfort@posteo.de>, WAI IG <w3c-wai-ig@w3.org>
Message-ID: <BN6PR03MB27855646F4B5321B73A1AC93F2B00@BN6PR03MB2785.namprd03.prod.outlook.com>
Hi,
During the API mapping meeting we decided not to include native form elements in the mapping unless they were explicitly labelled via aria-label or aria-labelledby, which would them map to role=”form”. This was to prevent all of the forms around the web that only include one form field and the like from automatically becoming landmarks.

So here is what the breakdown is:


  1.  Any container element including role=”form” is mapped as a Form landmark.
http://whatsock.com/training/matrices/#form


<div role=”form”>

As a best practice, if multiple instances of role=”form” exist on the same page, they should include unique labels via aria-label or aria-labelledby to differentiate them.


  1.  Any instance of a native HTML form element that also includes a valid aria-label or aria-labelledby attribute is also automatically mapped to role=”form”.

<form aria-label=”Shipping”> Or the same with aria-labelledby instead.


  1.  All other native form elements are ignored and are not mapped to role=”form”.

<form>

All support issues that exist with these combinations should be reported to the browser if not mapped properly in the accessibility tree, or to the AT vender if not announced properly.

All the best,
Bryan



Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com

From: ALAN SMITH [mailto:alands289@gmail.com]
Sent: Wednesday, August 02, 2017 9:05 AM
To: Gunderson, Jon R <jongund@illinois.edu>; Phill Jenkins <pjenkins@us.ibm.com>
Cc: Jonathan Avila <jon.avila@levelaccess.com>; Taliesin Smith <talilief@gmail.com>; tink@tink.uk; Tobias Bengfort <tobias.bengfort@posteo.de>; WAI IG <w3c-wai-ig@w3.org>
Subject: RE: non-landmark forms

I was wrong about the html <form> working as a region/landmark.
And, I can understand and appreciate the confusion it could cause if used without the intent of it being a true region/landmark.

However, I did notice that aria labeling was not required as stated so there is something to discuss.

All that was required was role=”form” in a <form> or <div>.


What I just tested was the following:

Div with  <DIV  role=”form”> only (no aria labeling) = WAS considered a region/landmark in FF, Chrome and IE with JAWS and NVDA
HTML <form> only (no aria labeling) =  WAS NOT  considered a region/landmark in FF, Chrome and IE with JAWS and NVDA
HTML <form role=”form”> only (no aria labeling) = WAS ALSO  considered a region/landmark in FF, Chrome and IE with JAWS and NVDA
HTML <form role=”form” aria-label=”my form region”> = WAS ALSO considered a region/landmark in FF, Chrome and IE with JAWS and NVDA

<h2>Regions by HTML form element only</h2>
<form>
  First name: <input type="text"><br>
  Last name: <input type="text"><br>
</form>
</h2>
<h2>Regions div with role=form</h2>
<div role="form">
  First name: <input type="text"><br>
  Last name: <input type="text"><br>
</div>
</h2>
<h2>Regions by HTML form element and role=form</h2>
<form role="form">
  2nd First name: <input type="text"><br>
  2nd Last name: <input type="text"><br>
</form>
</h2>
<h2>Regions by HTML form element, role=form and aria labeling</h2>
<form role="form" aria-label="my form area">
  2nd First name: <input type="text"><br>
  2nd Last name: <input type="text"><br>
</form>
</h2>>
</h2>

Alan Smith

From: Gunderson, Jon R<mailto:jongund@illinois.edu>
Sent: Wednesday, August 2, 2017 11:17 AM
To: Phill Jenkins<mailto:pjenkins@us.ibm.com>; ALAN SMITH<mailto:alands289@gmail.com>
Cc: Jonathan Avila<mailto:jon.avila@levelaccess.com>; Taliesin Smith<mailto:talilief@gmail.com>; tink@tink.uk<mailto:tink@tink.uk>; Tobias Bengfort<mailto:tobias.bengfort@posteo.de>; WAI IG<mailto:w3c-wai-ig@w3.org>
Subject: Re: non-landmark forms

Alan,

There were discussions in the ARIA working group that ROLE=FORM would only be considered a landmark if it had an accessible name, similar in concept to the ROLE=REGION.

I will ask the ARIA working group about it at the next meeting and I submitted a comment to the HTML working group related to the ARIA in HTML spec.
https://w3c.github.io/html-aam/#form


The main concern, like all HTML5 elements that have default landmark roles (e.g. MAIN, NAVGATION, ASIDE..) that people will be accidently be defining landmarks that will not be confusing or clutter then landmark navigation of a website.

Jon


From: Phill Jenkins <pjenkins@us.ibm.com<mailto:pjenkins@us.ibm.com>>
Date: Wednesday, August 2, 2017 at 10:01 AM
To: ALAN SMITH <alands289@gmail.com<mailto:alands289@gmail.com>>
Cc: Jonathan Avila <jon.avila@levelaccess.com<mailto:jon.avila@levelaccess.com>>, Taliesin Smith <talilief@gmail.com<mailto:talilief@gmail.com>>, "tink@tink.uk<mailto:tink@tink.uk>" <tink@tink.uk<mailto:tink@tink.uk>>, Tobias Bengfort <tobias.bengfort@posteo.de<mailto:tobias.bengfort@posteo.de>>, W3C WAI-IG <w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>>
Subject: RE: non-landmark forms
Resent-From: W3C WAI-IG <w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>>
Resent-Date: Wednesday, August 2, 2017 at 9:57 AM

I'm reading contradicting statements in this thread, can someone point me to a page that has both
        HTML form without aria role="form",
        and a aria role="form".
so it can be tested with JAWS, NVDA, and various browsers such as Chrome and Firefox?

what is in the spec and what is implemented and what is desired can often be three different things.  So I'm trying to understand all three regarding this topic of forms and landmarks/regions.
___________
Regards,
Phill Jenkins
pjenkins@us.ibm.com<mailto:pjenkins@us.ibm.com>
Senior Engineer & Accessibility Executive
IBM Research Accessibility
linkedin.com/in/philljenkins/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_in_philljenkins_&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=XINj3hdu4L4zmT5xwyCKleO71pumsfUMMRU5gRp42d4&e=>
ibm.com/able<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibm.com_able&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=w3n0HLs1ejurFphOojuRt3VfUQ1Gw2xNnk57an3XcTY&e=>
facebook.com/IBMAccessibility<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_IBMAccessibility&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=y3Ay6Y8XsPkY4cuh8pM_t0y7B7PTlqJFEqRmNdptviU&e=>
twitter.com/IBMAccess<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_IBMAccess&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=PWuxwJb6UuQT-1YcmLlYQL85VORJKx0SJC0AWOSrSPs&e=>
ageandability.com



From:        ALAN SMITH <alands289@gmail.com<mailto:alands289@gmail.com>>
To:        Jonathan Avila <jon.avila@levelaccess.com<mailto:jon.avila@levelaccess.com>>, Taliesin Smith <talilief@gmail.com<mailto:talilief@gmail.com>>, "tink@tink.uk<mailto:tink@tink.uk>" <tink@tink.uk<mailto:tink@tink.uk>>
Cc:        Tobias Bengfort <tobias.bengfort@posteo.de<mailto:tobias.bengfort@posteo.de>>, WAI IG <w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>>
Date:        08/02/2017 09:31 AM
Subject:        RE: non-landmark forms




Please be aware that you can use an HTML <form> without an aria role=”form” and this area will still be a Form region which is also translated “landmark”.

Therefore, it can be without an explicit ARIA form role attribute and it would still be a region or landmark form.


Alan Smith

From: Jonathan Avila<mailto:jon.avila@levelaccess.com>
Sent: Wednesday, August 2, 2017 10:16 AM
To: Taliesin Smith<mailto:talilief@gmail.com>; tink@tink.uk<mailto:tink@tink.uk>
Cc: Tobias Bengfort<mailto:tobias.bengfort@posteo.de>; WAI IG<mailto:w3c-wai-ig@w3.org>
Subject: RE: non-landmark forms


  *   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?

That is correct.

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access, inc.(formerly SSB BART Group, inc.)
(703) 637-8957
Jon.avila@levelaccess.com<mailto:Jon.avila@levelaccess.com>
Visit us online: Website<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ssbbartgroup.com_&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=2ZFwHykfuU56x8FScC8iihO7hjC47pu9pOMeioVsqCA&e=>| Twitter<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_SSBBARTGroup&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=cWZPBuWKgGwkESrBDmRPEUynN6tLzmKeKjvLCMqpCPo&e=>| Facebook<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ssbbartgroup&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=6FwLEl_a4uHnyBIkxFJgcdtZLJUxEaOpl9Od4t5GbYw&e=>| LinkedIn<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_355266-3Ftrk-3Dtyah&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=x3ftpTyD6S01T03NsDkg18U6Gn8zHyQTNlbnMwCyFts&e=>| Blog<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ssbbartgroup.com_blog_&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=hbIB9hRrdzYWLEhY88qpSccEphsy72EVYuwUYf_-QaM&e=>
Looking to boost your accessibility knowledge? Check out our free webinars!<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ssbbartgroup.com_webinars_&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=cFmHBaD-aA9-R2ze8Ajre8NjTlA-EsVXBgD0ZVGzBes&e=>

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.

From: Taliesin Smith [mailto:talilief@gmail.com]
Sent: Wednesday, August 2, 2017 9:57 AM
To: tink@tink.uk<mailto:tink@tink.uk>
Cc: Tobias Bengfort <tobias.bengfort@posteo.de<mailto:tobias.bengfort@posteo.de>>; WAI IG <w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>>
Subject: Re: non-landmark forms

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?

I was looking at the ARIA Landmark exmples<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_TR_wai-2Daria-2Dpractices-2D1.1_examples_landmarks_form.html&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=KrqXokD9obPvD11uilk7TDqtdUJP-q8aeMHIuTpZ7VM&e=> for ARIA Practices 1.1

Taliesin
On Aug 2, 2017, at 06:22, Léonie Watson <tink@tink.uk<mailto:tink@tink.uk>> wrote:

The form role only becomes a landmark when it's explicitly applied. Using the <form> element maps the form role implicitly, but does not turn every form into a landmark. I believe that's what you want in this situation.

--
@LeonieWatson @tink@toot.cafe<mailto:tink@toot.cafe>tink.uk<https://urldefense.proofpoint.com/v2/url?u=http-3A__tink.uk_&d=DwMFAw&c=8hUWFZcy2Z-Za5rBPlktOQ&r=bZujjczVTYPMSQ4uugSQLQ&m=B3zpHRUyIn7li-0r2MCht99tAKfLI05UZdMj5JNGhKQ&s=nNSzfwQghzrgDZ4kukOEsf1Sq2C927obQ9YoDjB-AZ4&e=>Carpe diem






image002.png
(image/png attachment: image002.png)

Received on Wednesday, 2 August 2017 16:56:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 August 2017 16:56:07 UTC