forked from AuroraMiddleware/gtk
docs: Add a section on accessible buttons
Anything that behaves like a button should do so at the accessibility level as well.
This commit is contained in:
parent
c5dc0e2e4c
commit
abd5383d40
@ -298,6 +298,16 @@ When creating custom widgets, following established patterns can help
|
|||||||
ensuring that the widgets work well for users of accessible technologies
|
ensuring that the widgets work well for users of accessible technologies
|
||||||
as well.
|
as well.
|
||||||
|
|
||||||
|
### Buttons
|
||||||
|
|
||||||
|
A button is a widget that enables users to trigger an action. While it is
|
||||||
|
recommended you use #GtkButton for anything that looks and behaves like a
|
||||||
|
button, it is possible to apply a button behavior to UI elements like images
|
||||||
|
by using a #GtkGestureClick gesture. When doing so, you should:
|
||||||
|
|
||||||
|
- Give your widget the role %GTK_ACCESSIBLE_ROLE_BUTTON
|
||||||
|
- Install an action with no parameters, which will activate the widget
|
||||||
|
|
||||||
### Custom entries
|
### Custom entries
|
||||||
|
|
||||||
For custom entries, it is highly recommended that you implement the
|
For custom entries, it is highly recommended that you implement the
|
||||||
|
Loading…
Reference in New Issue
Block a user