[Glade-devel] Implementing accessibility non-regression check tool

[Samuel Thibault]

Hello,

In the context of LibreOffice, the Hypra company will work on an
accessibility non-regression check tool.

Basically, the idea is to design a tool which will check .ui files for
accessibility issues: missing relations between widgets and labels,
notably. The tool would just use libxml to parse the files and emit
warnings for the found issues.

Such a tool could be called by application build system so that
developers get the warnings along other compiler warnings, and treated
the same way. It could also be used in Continuous Integration reports.

Of course, there are a lot of existing issues, so we plan to add support
for suppression rules, so that when the tool invocation is integrated,
one can integrate an initial set of suppression rules which allows to
start with a zero-warning state, and then for a start developers will
try to stay without warning, and progressively fix existing issues and
their corresponding suppression rules.

One of the remaining questions we have (it's not blocking for our
immediate development, though) is whether this tool should be integrated
within LibreOffice, or within glade. The latter would both allow more
widespread use of the tool by other projects, and make the maintenance
happen there, thus less work for LibreOffice :)

What do glade people think about this question?

Samuel
_______________________________________________
Glade-devel maillist - Glade-***@lists.dot.net
http://lists.dot.net/mailman/listinfo/glad

[l***@gmail.com]

Post by Samuel Thibault
Hello,
In the context of LibreOffice, the Hypra company will work on an
accessibility non-regression check tool.
What do glade people think about this question?

I don't know what people think about this, but GMail thinks that your message
was a spam. I saw it only by pure luck.

[Samuel Thibault]

Hello,

Post by l***@gmail.com

Post by Samuel Thibault
In the context of LibreOffice, the Hypra company will work on an
accessibility non-regression check tool.
What do glade people think about this question?

I don't know what people think about this, but GMail thinks that your
message was a spam. I saw it only by pure luck.

Ew... I don't see what is wrong there, spamassassin only scores it
BAYES_50...

Did other people have issues receiving that
mail too? The content is available on
http://lists.dot.net/pipermail/glade-devel/2018-January/002121.html

Samuel
_______________________________________________
Glade-devel maillist - Glade-***@lists.dot.net
http://lists.dot.net/mailman/listinfo/glad

[Samuel Thibault]

Hello,

As part of implementing an accessibility non-regression check tool, we
want to make sure that widgets have proper labelling. E.g. GtkEntry
basically always need a labelled-by relation. Some other widgets don't
necessarily need one, but very often need one (such as radio buttons),
so we want to emit a warning if there is none, unless it was marked as
not needing one.

Conversely, labels are most often introduced for a reason, and they
should thus almost always have a label-for relation, except for
exceptions which need to be marked as such.

The question is then how we should mark them. Perhaps we could use e.g.

<accessibility>
<relation type="no-labelled-by" />
</accessibility>

for widgets, and

<accessibility>
<relation type="no-label-for" />
</accessibility>

for labels?

Samuel
_______________________________________________
Glade-devel maillist - Glade-***@lists.dot.net
http://lists.dot.net/mailman/listinfo/gl