Re: [Tutorial Feedback] - WCAG 2.0 Level a certification

Hi Sandeep,

There is no way to detect if a screen reader is used or what screen 
reader is used. The same goes for other assistive technology.

That’s why the recommendation is to put an (invisible) hint into the 
first label of the group:

“In case the <legend> is not read by screen readers, labels for the 
first form control in each group should include the group’s name. This 
name can be hidden visually.”

```
<label for="shipping_name">
   <span class="visuallyhidden">Shipping </span>Name:
</label><br>
<input type="text" name="shipping_name" id="shipping_name">
```

https://www.w3.org/WAI/tutorials/forms/grouping/#related-fields

Screen readers then consistently read “Shipping Name” for the first 
field.

I’ll check back with the WCAG WG on Technique 
[H71](https://www.w3.org/TR/WCAG20-TECHS/H71.html).

Eric

On 25 Jan 2017, at 18:09, Shetty, Sandeep wrote:

> Hi,
>
> I am working on a html5/css/java-script website for WCAG 2.0 Level a 
> certification.
>
> Need clarification on grouping.
>
> https://www.w3.org/WAI/tutorials/forms/grouping/
>
> On this link for field set / legend implementation there is a note as 
> below..
>
> In case the <legend> is not read by screen readers (see note below), 
> labels for the first form control in each group should include the 
> group's name. This name can be hidden visually.
> [cid:image001.png@01D27759.D31FD880]
> Note: Depending on the configuration, some screen readers read out the 
> legend either with every form element, once, or, rarely, not at all. 
> To accommodate this consider the following:
>
>   *   Make the legend as short as possible for situations in which it 
> is read together with the label each time.
>   *   Make the individual labels sufficiently self-explanatory for 
> situations in which legends are not read aloud, without repeating the 
> legend in every label.
>
>
> Here is it possible to know whether the screen reader reads the legend 
> or not to decide to include visually hidden group name for first form 
> control or all form controls or implement something else?
>
>
> I have tested the sample code for the above screenshot on mobile 
> browsers.
>
> In Windows OS - jaws 18 - IE 11 browser - the legend text is announced 
> by the screen reader for each form control
> In windows OS - chrome-vox - chrome browser - the legend text is not 
> announced by the screen reader
>
> In Android 5 - talkback 5 - chrome browser - the legend text is not 
> announced by the screen reader.
> In IOS 9 - voice over - safari browser - the legend text is not 
> announced by the screen reader.
>
> In IOS 10 - voice over - safari browser - the legend text is announced 
> by the screen reader for the first form control.
>
> As far as I am aware through java script the user agent check can tell 
> us only what browser and whether its desktop or mobile browser. We 
> can't know whether grouping with field set works or not!
>
> Here if https://www.w3.org/TR/WCAG20-TECHS/H71.html technique doesn't 
> work then only possible solution is to have a descriptive label 
> itself.
>
> Please let me know how I can go about getting this working in all 
> screen readers / to pass certification.
>
> Regards,
> Sandeep
>
>
> [http://bridge.nextgen.com/Media/3140]
> ________________________________
>
>
> Sandeep Shetty
> Technical Specialist
> NEXTGEN HEALTHCARE
> +9180 49072400 x 27658
>
>
> This message, and any documents attached hereto, may contain 
> confidential or proprietary information intended only for the use of 
> the addressee(s) named above or may contain information that is 
> legally privileged. If you are not the intended addressee, or the 
> person responsible for delivering it to the intended addressee, you 
> are hereby notified that reading, disseminating, distributing or 
> copying this message is strictly prohibited. If you have received this 
> message by mistake, please immediately notify us by replying to the 
> message and delete the original message and any copies immediately 
> thereafter. Thank you for your cooperation.





--

Eric Eggert
Web Accessibility Specialist
Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)