WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: form accessibility

for

From: Angela French
Date: Aug 10, 2016 4:55PM

I have fieldset and legend around each group but moved the legend off the visual field. Are they not perceivable by screen readers?

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Jim Homme
Sent: Wednesday, August 10, 2016 2:17 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] form accessibility

Hi,
My bad. Please do what Jamous said with the radio buttons. Also, if possible, put fieldset and legend around them each group.

Jim


=========Jim Homme,
Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
<EMAIL REMOVED>
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Jim Homme
Sent: Wednesday, August 10, 2016 5:14 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] form accessibility

Hi,
You definitely need the id attribute. For the label tag, you need the for attribute. Let me advise you to make the id attribute and as soon as you make it, get the value from the quotes, and make the for attribute, then paste the value. HTML wants them to be exactly the same, including case. And make sure that the id's are unique. Regarding the name attribute, you need it if scripting refers to it.

Thanks.

Jim


=========Jim Homme,
Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
<EMAIL REMOVED>
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Angela French
Sent: Wednesday, August 10, 2016 4:41 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] form accessibility

It isn't necessary to have either the "name" or "title" attribute, correct? Should id and for suffice?

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Jamous, JP
Sent: Wednesday, August 10, 2016 12:01 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] form accessibility

Angela,

It is a mess for JAWS 17. JAWS 17 keeps reading what is in the name="".

Give your radio button an ID and use for="RadioButtonID". Inside that label put what you want the caption to be for the radio button.

The way you have the labels wrapped around the check boxes and radio buttons are causing major accessibility issues. I can only tell what the radio button or check box is by down-arrowing through the form.
-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Angela French
Sent: Wednesday, August 10, 2016 1:38 PM
To: WebAim Forum ( <EMAIL REMOVED> ) < <EMAIL REMOVED> >
Subject: [WebAIM] form accessibility

I have created a from using a form building tool in the CMS that we use. I'm not convinced the end results are accessible, though achecker.ca did not throw an error on my radio buttons and checkboxes.

Doesn't there need to be matching "for" and "id" attributes in the <label> and the <input>? Otherwise how does the screen reader users know which labels go with which radio buttons/checkboxes?

Here is my test form.

http://www.dev.sbctc.edu/_testing/site-satisfaction-survey-2.aspx

Thank you for any advice on how to make this form more accessible. I am aware of the error thrown on the hidden field for bots. Am working on that.


Angela French
Internet/Intranet Specialist
Washington State Board for Community and Technical Colleges
360-704-4316
<EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
www.sbctc.edu<;http://www.sbctc.edu/>;