WebAIM - Web Accessibility In Mind

E-mail List Archives

How to make the text label for radio button?

for

From: UYEN THAI
Date: Jun 19, 2019 8:35AM

Hello all,
I have one this scenario that i do not know how to code complaint with JAWS - the text before the radio buttons "Corrected Case"??And they put them (the form) inside the layout table.

This is for example:
<table summary ="layout table">
<tbody>
<tr>
<th>Corrected Case</th>
<td><input type="radio" name=xyz.abc" id="abc-tru" value="true">
<label for ="abc-true">Yes</label>
<td>...</td>
</tr>
</tbody>
</table>

Please let me know how to make the text before Yes/No read by JAWS.

Thanks much!

Uyen

> On Jun 19, 2019, at 6:27 AM, Karlen Communications < <EMAIL REMOVED> > wrote:
>
> Duff:
>
> I've started documenting some of the "crappy" tagging we're seeing from all applications:
> https://www.karlencommunications.com/DocumentRemediation.htm
>
> I'll send you as many examples as you need. Am currently working on how Footnotes/Endnotes are being lumped together and read as a single unit when you land on the first one in a document. Am seeing if this tagging behaviour is unique to the Microsoft and Acrobat Pro DC tagging tools or if Foxit Phantom for Business and Nuance PowerPDF also produce this type of accessibility barrier.
>
> For the scanned documents, I can send you all the sample files off list as there are about 15 of them and they won't fit in an e-mail, even attached to the PDF document about scanned documents.
>
> Phillip and I have chronicled the problems in response to the original post with this subject line. He did list some of the things I missed so merging the lists will give you a good idea on the problems we are encountering.
>
> Cheers, Karen
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Duff Johnson
> Sent: Tuesday, June 18, 2019 9:15 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Word To PDF Accessibility: What Does and Does Not Transmit From Word To PDF
>
>> We're seeing a regression in accessible PDFs from any source program
>> using any of the available tools, not just Adobe's PDF Maker plug-in,
>> Microsoft's built-in converter, Fox It, Nuance Power PDF, or Axes4 PDF's utility.
>> The biggest problems are with Tables of Content, footnotes, and
>> regular tables.
>
> Can you describe the problems you are encountering now in detail?
>
>> Part of this comes from the development of the forthcoming PDF UA-2
>> standards, which are not yet completed nor published by the ISO. But
>> companies are beginning to build UA-2 "stuff" into their programs now,
>> in today's versions.
>
> Really? Can you provide examples?
>
>> Essentially, they are jumping ahead of the standard and consequently,
>> no A T knows how to process this stuff and present it to the human
>> being using the A T.
>
> Most AT hasn't caught up with ISO 32000-1 (2008) yet… so ISO 32000-2 (2017) doesn't really surprise me...
>
>> The main questions this community needs to ask and get answers for:
>>
>> 1. Why are we going backwards? Why are PDFs exported from Word today,
>> with the latest software releases, less accessible than they were 2 years ago?
>
> Examples, please. What exactly are they doing wrong today?
>
>> 2. Why do different companies interpret the standards differently?
>
> It's a human thing. :-)
>
>> Aren't
>> standards supposed to, well, standardize things?
>
> Let's first ascertain that this is, in fact, happening...
>
>> 3. Any why are companies programming for UA-2 before it's ready and
>> released? Or even the law? Sec. 508 requires only PDF UA-1, not UA-2.
>>
>> Any answers?
>
>
> PDF/UA-2 doesn't really exist yet. It's hard for me to believe that anyone has attempted to implement it at this stage.
>
> If they are writing PDF 2.0 tag structures ok… but then there's the rest of the toolchain (accessibility APIs and AT) needed for consumption. It seems unlikely that Adobe (to take one example) would implement features that its own software could not consume… but maybe.
>
> Examples would be good!
>
> Duff.
>
> > > >
> > > >