WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [External Sender]Instructions inside forms

for

From: Brian Lovely
Date: Nov 15, 2019 10:30AM

Thanks all, that's very useful.

On Fri, Nov 15, 2019 at 12:23 PM Birkir R. Gunnarsson <
<EMAIL REMOVED> > wrote:

> Patrick is correct (it happens quite often that he is).
> The form> elemet does not trigger a particular screen reader behavior,
> such as switching to forms mode, those behaviors are tied to
> individual form controls (e.g. radio buttons or text inputs trigger
> forms mode / application mode in screen readers).
> The document rol doesn't do anything other than forcing browse mode
> when encountered with a screen reader and should really only be used
> in combination with the application role that forces forms/application
> mode (and the use cases for such a combo are rare outside of a highly
> scripted interactive interface like a spreadsheet).
>
> I think the solution is a lot less complicated:
>
> Makesure the instructions are at the top of the form, before the
> interactive elements.
> Start the form (or the instruction section within the form) with a
> heading with text such as "important information".
> That's all you need to do.
> If you really need to make sure the user has read the instructions,
> put a checkbox at the end of the form with a label such as, "I agree I
> have read the instructions".
> You can use aria-describedby on that checkbox to the element with the
> important instructions.
> <form>
> <h3>Important information</h3>
> <p Id="x">You must specify the seat selection before your flight to
> guarantee your seat selection. Selecting your seat after the flight is
> pretty useless anyway.</p>
>
> ...the form
> ....
>
> <label for="readIt">I have read the instructions at the top of the
> form</label>
> <input id="readIt" type="checkbox" aria-describedby="x">
> <button>Submit reservation</button>
> </form>
>
>
>
>
> On 11/15/19, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> > On 15/11/2019 17:06, Brian Lovely via WebAIM-Forum wrote:
> >> These things are generally put inside the open and close form tags (in
> my
> >> experience), which is where my whole discoverability dilemma comes from.
> >> If
> >> they were simple text nodes in a non-semantic container outside the form
> >> I
> >> wouldn't have a problem.
> >
> > Not explicitly checked all combinations of browser/AT, but screen
> > readers (from memory) don't switch into forms mode when they first enter
> > a <form>, but upon entering the first form control, so don't quite see
> > this as a problem?
> >
> > P
> > --
> > Patrick H. Lauke
> >
> >
> https://urldefense.com/v3/__http://www.splintered.co.uk__;!0Ns9_1dOjwg!PIo0iZUbijVzO4ukCE2kHuN6dmxtU_VXibL6Drp19-W5HH7Ak3yqhg1FF_l3P2k-605-cA$
> |
> https://urldefense.com/v3/__https://github.com/patrickhlauke__;!0Ns9_1dOjwg!PIo0iZUbijVzO4ukCE2kHuN6dmxtU_VXibL6Drp19-W5HH7Ak3yqhg1FF_l3P2lR85cTRg$
> >
> https://urldefense.com/v3/__http://flickr.com/photos/redux/__;!0Ns9_1dOjwg!PIo0iZUbijVzO4ukCE2kHuN6dmxtU_VXibL6Drp19-W5HH7Ak3yqhg1FF_l3P2lyqma79A$
> |
> https://urldefense.com/v3/__http://redux.deviantart.com__;!0Ns9_1dOjwg!PIo0iZUbijVzO4ukCE2kHuN6dmxtU_VXibL6Drp19-W5HH7Ak3yqhg1FF_l3P2kd7UJTUA$
> > twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > > https://urldefense.com/v3/__http://list.webaim.org/__;!0Ns9_1dOjwg!PIo0iZUbijVzO4ukCE2kHuN6dmxtU_VXibL6Drp19-W5HH7Ak3yqhg1FF_l3P2ntfoWgrg$
> > List archives at
> https://urldefense.com/v3/__http://webaim.org/discussion/archives__;!0Ns9_1dOjwg!PIo0iZUbijVzO4ukCE2kHuN6dmxtU_VXibL6Drp19-W5HH7Ak3yqhg1FF_l3P2kQkAV2rQ$
> > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > https://urldefense.com/v3/__http://list.webaim.org/__;!0Ns9_1dOjwg!PIo0iZUbijVzO4ukCE2kHuN6dmxtU_VXibL6Drp19-W5HH7Ak3yqhg1FF_l3P2ntfoWgrg$
> List archives at
> https://urldefense.com/v3/__http://webaim.org/discussion/archives__;!0Ns9_1dOjwg!PIo0iZUbijVzO4ukCE2kHuN6dmxtU_VXibL6Drp19-W5HH7Ak3yqhg1FF_l3P2kQkAV2rQ$
> >


--
*Brian Lovely*
Capital One Digital Accessibility
804.389.1064




The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.