E-mail List Archives
Re: Required VS Optional
From: Birkir R. Gunnarsson
Date: Sep 1, 2020 7:47AM
- Next message: glen walker: "Re: Accessibility for a data processing button"
- Previous message: Birkir R. Gunnarsson: "Re: Accessibility for a data processing button"
- Next message in Thread: None
- Previous message in Thread: Murphy, Sean: "Required VS Optional"
- View all messages in this Thread
I think the reason there is no aria-optional (or an optional HTML
attribute) is that all form fields are, by default, optional. Making
them required is a design decision.
To meet this requirement, just make sure you indicate which fields are
required, you can do it by indicating which fields are optional. The
specific technique, to my mind, doesn't matter, it's the intent.
If there is usability research to recommend a particular approach,
that's always a good thing.
On 9/1/20, Murphy, Sean < <EMAIL REMOVED> > wrote:
> Team,
>
> WE are in the process of building components for our design system and come
> across a difference of opinion on the use of required VS Optional.
>
> The current trend from the research we have undertaken thus far is towards
> only providing required fields with optional fields sparingly. The optional
> fields will have the word at the end of the label. Discussion surrounding
> having instructions stating all fields are required, otherwise stated, or
> words to that fact. UX research which has been found states only required
> fields should be on the form, as this assists with cognitive load and
> optional fields reduce usability of the form.
>
> 3.3.2Labels or
> Instructions<https://www.w3.org/WAI/WCAG21/quickref/#labels-or-instructions>
> states:
> In a form which contains both required and optional fields, the required
> fields and/or the optional fields are clearly labelled as such.
>
> The techniques do not reference the use of labels with option in them. Only
> reference providing clear labels and instructions for required.
>
> Thus, you could argue if the form clearly indicates "Optional" for the
> fields. You don't need the "required" indicators at aria or the UI level.
> Since it is implicit any field without "Optional" is required. Hence using
> that design, the form fields pass this SC.
>
> * Is there any accessibility research out there why the trend is to use
> required over optional on forms?
> * Any research why ARIA-required is present and there is no
> ARIA-Optional?
>
> Thoughts on this are more than welcomed.
>
>
>
>
> Regards
> Sean Murphy
>
> [cid:image001.png@01D68069.8684CD60]
>
> Sean Murphy | Senior Digital System specialist (Accessibility)
> Telstra Digital Channels | Digital Systems
> Mobile: 0405 129 739 | Desk: (02) 9866-7917
> Digital Systems Launch
> Page<https://confluence.in.telstra.com.au/display/DCSYS/Digital+Systems+-+Able+Home>
> Accessibility Single source of
> Truth<https://confluence.in.telstra.com.au/display/DCSYS/Accessibility+Resources>
>
>
--
Work hard. Have fun. Make history.
- Next message: glen walker: "Re: Accessibility for a data processing button"
- Previous message: Birkir R. Gunnarsson: "Re: Accessibility for a data processing button"
- Next message in Thread: None
- Previous message in Thread: Murphy, Sean: "Required VS Optional"
- View all messages in this Thread