OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office-accessibility message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office-accessibility] ODF radio button groups



Here's the core markup...

radiogroups.odt - frame with two button groups - this is the one sent by Malte the first time.

<form:form form:name="Standard">
 <form:frame form:name="GroupBox" form:id="control1" form:label="Just a Box/Frame - 2 groups" form:for="control2,control3,control4,control5" />
   <form:radio form:name="RadioGroup1" form:id="control2" form:label="TEST1" > </form:radio>
  <form:radio form:name="RadioGroup1" form:id="control3" form:label="TEST2" > </form:radio>
  <form:radio form:name="RadioGroup2" form:id="control4" form:label="Grp2-A" > </form:radio>
  <form:radio form:name="RadioGroup2" form:id="control5" form:label="Grp2-B" > </form:radio>
</form:form>

radiogroups2.odt - two radio button groups labeled with static text - the frame is removed; the labels are added

<form:form form:name="Standard" >
  <form:fixed-text form:name="LabelField1" form:for="control3,control4" form:id="control1" form:label="LABEL 1" />
  <form:fixed-text form:name="LabelField2" form:for="control5,control6" form:id="control2" form:label="LABEL 2" />
  <form:radio form:name="RadioGroup1" form:id="control3" form:label="Grp1-1" > </form:radio>
  <form:radio form:name="RadioGroup1" form:id="control4" form:label="Grp1-2" > </form:radio>
  <form:radio form:name="RadioGroup2" form:id="control5" form:label="Grp2-A" > </form:radio>
  <form:radio form:name="RadioGroup2" form:id="control6" form:label="Grp2-B" > </form:radio>
</form:form>

radiogroups2b.odt - contrived test case where each label has form:for for buttons from different groups; like the prior one but see small change in red on 2nd and 3rd radio butons.

<form:form form:name="Standard" >
  <form:fixed-text form:name="LabelField1" form:for="control3,control4" form:id="control1" form:label="LABEL 1" />
  <form:fixed-text form:name="LabelField2" form:for="control5,control6" form:id="control2" form:label="LABEL 2" />
  <form:radio form:name="RadioGroup1" form:id="control3" form:label="Grp1-1" > </form:radio>
  <form:radio form:name="RadioGroup2" form:id="control4" form:label="Grp1-2" > </form:radio>
  <form:radio form:name="RadioGroup1" form:id="control5" form:label="Grp2-A" > </form:radio>
  <form:radio form:name="RadioGroup2" form:id="control6" form:label="Grp2-B" > </form:radio>
</form:form>

radiogroups3.odt - like the second case but with an outer frame

<form:form form:name="Standard" >
  <form:frame form:name="GroupBox" form:for="control1,control2" form:id="control7" form:label="Group Box" />
  <form:fixed-text form:name="LabelField1" form:for="control3,control4" form:id="control1" form:label="LABEL 1" />
  <form:fixed-text form:name="LabelField2" form:for="control5,control6" form:id="control2" form:label="LABEL 2" />
  <form:radio form:name="RadioGroup1" form:id="control3" form:label="Grp1-1" > </form:radio>
  <form:radio form:name="RadioGroup1" form:id="control4" form:label="Grp1-2" > </form:radio>
  <form:radio form:name="RadioGroup2" form:id="control5" form:label="Grp2-A" > </form:radio>
  <form:radio form:name="RadioGroup2" form:id="control6" form:label="Grp2-B" > </form:radio>
</form:form>

Either a form:frame with a single group or a group with a label (form:fixed-text form:for) would be the best practice on the ODF side.  The a11y implementation would provide labeledBy/labelFor relations.  In the last case it would be ideal if ATs would read both the immediate static text label and the frame label but I suspect they won't and this would be a work item for the ATVs.  Some testing would be required as the typical situation on Win is a single radio button group per group box and a parent/child relation between the groupbox and the radio buttons.

Pete Brunet
                                                                         

IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, Cell: (512) 689-4155
Ionosphere: WS4G



Malte Timmermann <Malte.Timmermann@Sun.COM>
Sent by: Malte.Timmermann@Sun.COM

10/08/2008 01:02 AM

To
Pete Brunet/Austin/IBM@IBMUS
cc
office-accessibility@lists.oasis-open.org
Subject
Re: [office-accessibility] ODF radio button groups





Hi...

> Malte, Please tweak your test case to add two static text labels
> labeling the two button groups so we can see how ODF labels them, i.e.

Since OOo's UI doesn't allow me to do that, I could only guess how it
should like in ODF.

See attached documents.

Please notice (in OOo) that grouping logic still uses the form:names,
not the form:for.

PDF Export and using Adobe Reader has exactly the same grouping
behaviour, but I don't know how the PDF Tags look like...

> during the meeting you mention that labelFor/labelledBy relations would
> be used but I think the spec indicates that form:fixed-text with a
> form:for attribute would be used.

Sorry for creating confusion.

What I meant was: When using "form:for" in ODF, it should be reflected
via Accessibility API "LabelFor", which then means the
labeled/referenced elements should report a "LabeledBy", which has no
equivalent attribute in ODF (would be redundant).

Malte.
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

radiogroups2.odt

radiogroups2b.odt

radiogroups3.odt



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]