Re: [g-a-devel]Accessibility support in Glade



On Wed, 2002-03-13 at 13:35, Bill Haneman wrote:
> Damon Chaplin wrote:
> 
> > I can't see any libglade code to handle nested <accessibility> elements.
> > 
> > It only keeps one array of actions/relations/properties for each widget,
> > and adds them to the widget in glade_xml_add_accessibility_info().
> 
> I think we are talking at cross purposes; I don't understand at all 
> what the atkaction stuff has to do with nested <accessibility> elements.
> atkaction elements are rightfully children of one accessibility element,
> and they are applied to that element.

I mean for the table row & column descriptions, like your example:

[... XML for the GtkTreeView widget goes here]
<accessibility>
        <atkproperty name="AtkObject:accessible-table-column-header"
index=2>
                <accessibility>
                        <atkproperty name="AtkObject:accessible-name">
                        "February"
                        </atkproperty>
                        <atkproperty>
                        "Accounts receivable entries for Feb, 2002"
                        </atkproperty>
                </accessibility>
        </atkproperty>
</accessibility>


I can't see any code in libglade to handle this.
I'm not entirely sure what it should do, but I need to study the ATK API
a bit more.


  
> > I've added a libglade bug about making action descriptions translatable:
> > 
> > http://bugzilla.gnome.org/show_bug.cgi?id=74412
> > 
> > We either move the description text to the contents of the atkaction tag
> > and mark it with a 'translatable' attribute, or we update intltool so it
> > copies the description attribute to the pot file.
> 
> I think I don't understand what you mean here, at least in the
> first part of the sentence.  However we do it, the atkaction
> description tags should be translated and translatable.

We mark translatable string properties in Glade XML files with a
'translatable' attribute, so intltool can find them. But currently the
atkaction description is an attribute, so we can't mark it.

 
> > (By the way, do you have an a11y icon I can use for the notebook tab?)
> 
> No; as I said I am not keen on using an icon here.

What would you prefer?


>  We don't have any good 
> ones... and AFAIK there are no universally accepted ones in the 
> accessibility community.  The ole' wheelchair logo looks pretty
> dumb in this context I think.

That's a shame. I thought that one would look good, and be fairly
obvious to most people (and get more attention!).

There are several good icons here, including the wheelchair symbol:
http://www.gag.org/resources/das.html

Damon





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]