From: Matthias Clasen Date: Tue, 13 Jun 2023 18:12:16 +0000 (-0400) Subject: a11y docs: Some updates X-Git-Tag: archive/raspbian/4.12.3+ds-1+rpi1~1^2^2^2~22^2~1^2~139^2 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=9831632fbd844c46fb088563d92d394e2a4c5f39;p=gtk4.git a11y docs: Some updates Clarify what UI properties go into the name computation, and mention the inspector tools for accessiblity. --- diff --git a/docs/reference/gtk/section-accessibility.md b/docs/reference/gtk/section-accessibility.md index 71ccd417ee..878a5d0e1f 100644 --- a/docs/reference/gtk/section-accessibility.md +++ b/docs/reference/gtk/section-accessibility.md @@ -204,19 +204,17 @@ you should ensure that: readable and localised action performed when pressed; for instance "Copy", "Paste", "Add layer", or "Remove" -GTK will try to fill in some information by using ancillary UI control -properties, for instance the accessible label will be taken from the label or -placeholder text used by the UI control, or from its tooltip, if the -`GTK_ACCESSIBLE_PROPERTY_LABEL` property or the `GTK_ACCESSIBLE_RELATION_LABELLED_BY` -relation are unset. Nevertheless, it is good practice and project hygiene -to explicitly specify the accessible properties, just like it's good practice -to specify tooltips and style classes. +GTK will try to fill in some information by using ancillary UI control properties, +for instance the accessible name will be taken from the label used by the UI control, +or from its tooltip, if the `GTK_ACCESSIBLE_PROPERTY_LABEL` property or the +`GTK_ACCESSIBLE_RELATION_LABELLED_BY` relation are unset. Similary for the accessible +description. Nevertheless, it is good practice and project hygiene to explicitly specify +the accessible properties, just like it's good practice to specify tooltips and style classes. Application developers using GTK **should** ensure that their UI controls -are accessible as part of the development process. When using `GtkBuilder` -templates and UI definition files, GTK provides a validation tool that -verifies that each UI element has a valid role and properties; this tool can -be used as part of the application's test suite to avoid regressions. +are accessible as part of the development process. The GTK Inspector shows +the accessible attributes of each widget, and also provides an overlay that +can highlight accessibility issues. ## Implementations