WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Does every field need a label in this instance?

for

From: Alan Zaitchik
Date: Feb 4, 2023 5:40PM

Speech recognition technology users (e.g,, Dragon) may have a hard time identifying an input control that has no uniquely identifying, visible label. Aria labels won't help such users.
A

> On Feb 4, 2023, at 10:18, Bettina Szekany < <EMAIL REMOVED> > wrote:
>
> Cool 🙂
> We're using ARIA labeling to identify the separate form fields as well as
> each and every field has an ARIA labeling to provide information for screen
> readers.
> Are these measurements sufficient?
>
> Kindly,
> Bettina
>
>> On Sat, Feb 4, 2023, 15:46 <EMAIL REMOVED> < <EMAIL REMOVED> >
>> wrote:
>>
>> Bettina
>> That sounds to me like it could work.
>> Have you tested it with a screen reader to see if you would be able to
>> identify each of the fields to know what information you needed to enter
>> there if you were not familiar with the page?
>> Dino
>>
>> 617-799-1162
>>
>> Dino's Canteen 1618
>> 11 Eglin St,
>> Hanscom AFB
>> Bedford, MA
>>
>> On Feb 4, 2023, at 9:14 AM, Bettina Szekany < <EMAIL REMOVED> >
>> wrote:
>>
>> Hi Dino,
>>
>> Thanks for the feedback!
>>
>> It is a webapp that you can build a matrix type questionnaire with.
>> The input fields are for labeling the rows and columns. The rows and the
>> columns are organised into two separated sections with respective heading
>> titles.
>> Every single input field in one section would either have the visible label
>> "row label" or "column label".
>> This would have a big impact on usability and scanability when we
>> considering the amount of fields (100+).
>> Based on my research I was thinking to add a short description under the
>> heading titles stating that the field inputs are for labeling the
>> rows/columns.
>>
>> Kindly,
>> Bettina
>>
>> On Sat, Feb 4, 2023, 14:32 <EMAIL REMOVED> <
>> <EMAIL REMOVED> >
>> wrote:
>>
>> In my opinion, I would guess that would depend on exactly what the field
>> is.
>> Each field should have a unique name.
>> However, if for some reason they have to be identical, it would probably
>> behoove you to indicate at the beginning of the page that each form field
>> is identical because it has a blind screen reader user when I tap into each
>> field. If it doesn't indicate what that field is, I will find it very
>> confusing.
>>
>> Dino
>>
>> 617-799-1162
>>
>> Dino's Canteen 1618
>> 11 Eglin St,
>> Hanscom AFB
>> Bedford, MA
>>
>> On Feb 4, 2023, at 7:14 AM, Bettina Szekany < <EMAIL REMOVED> >
>> wrote:
>>
>> Hello everyone,
>>
>> I'd like to get some input please.
>>
>> I'm designing a form that by default has
>> - a descriptive heading
>> - 3 input fields with hint text. Purpose of these input fields is the
>> same.
>> Number of fields can go up to 100
>> - aria labeling for fields
>>
>> Every single input field would have the same label, thus labels were
>> ommitted to avoid visual clutter.
>>
>> I have came across these suggestion on a website and I find them
>> conflicting. (
>>
>>
>> https://www.digitala11y.com/understanding-sc-3-3-2-labels-or-instructions/?unapproved698&moderation-hash70a52e52fd5aae9e43c4b6205b0b82#comment-90698
>> )
>>
>> • "content authors must ensure that information is not overwhelming and
>> thus do not clutter the page or even the memory of the users"
>> • "Always provide visible labels to every form fields and controls"
>>
>> I'd like to know in the instance described above do we need to add the
>> same
>> label for every single input field?
>>
>> Thanks very much in advance!
>> >> >> >> >> >> >> >> >>
>> >> >> >> >> >> >> >> >>
>