debcrafters-packages team mailing list archive

[Sergio Costas <2116954@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The "Restrict Applications" button lacks the corresponding role,
so an user using a screen reader won't be able to know that they
can push it to expand the list of applications.

[ Impact ]

An user that depends on the screen reader won't know the associated role
of the button, which can be misleading and make use more difficult.

[ Test plan ]

* In a virtual machine, open a terminal
* type `export XDG_CURRENT_DESKTOP=GNOME` and `export UNDER_JHBUILD=1` to set debug mode and pure-gnome mode in gnome-initial-setup.
* enable the screen reader (Super+Alt+S)
* launch `/usr/libexec/gnome-initial-setup`
* advance until the `About you` page
* add an user, different of the current one
* enable the `Parental control` checkbutton
* go to the next page
* insert a password
* go to the next page (parental controls)
* move the cursor, using the TAB key, to the `Restrict applications` button
* without the patch, it will be read as `Restrict applications. Prevents specified...`, without a role.
  Instead, with the patch, it should be read as `Restrict applications Pressbutton. Prevents specified...`

[ Where problems could occur ]

Since this patch only adds A11Y info, the only possible problem is that
incorrect accessibility information would be sent to the screen reader.

** Affects: malcontent (Ubuntu)
     Importance: Undecided
     Assignee: Sergio Costas (rastersoft-gmail)
         Status: New

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to malcontent in Ubuntu.
https://bugs.launchpad.net/bugs/2116954

Title:
  A button lacks the A11Y role

Status in malcontent package in Ubuntu:
  New

Bug description:
  The "Restrict Applications" button lacks the corresponding role,
  so an user using a screen reader won't be able to know that they
  can push it to expand the list of applications.

  [ Impact ]

  An user that depends on the screen reader won't know the associated
  role of the button, which can be misleading and make use more
  difficult.

  [ Test plan ]

  * In a virtual machine, open a terminal
  * type `export XDG_CURRENT_DESKTOP=GNOME` and `export UNDER_JHBUILD=1` to set debug mode and pure-gnome mode in gnome-initial-setup.
  * enable the screen reader (Super+Alt+S)
  * launch `/usr/libexec/gnome-initial-setup`
  * advance until the `About you` page
  * add an user, different of the current one
  * enable the `Parental control` checkbutton
  * go to the next page
  * insert a password
  * go to the next page (parental controls)
  * move the cursor, using the TAB key, to the `Restrict applications` button
  * without the patch, it will be read as `Restrict applications. Prevents specified...`, without a role.
    Instead, with the patch, it should be read as `Restrict applications Pressbutton. Prevents specified...`

  [ Where problems could occur ]

  Since this patch only adds A11Y info, the only possible problem is
  that incorrect accessibility information would be sent to the screen
  reader.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/2116954/+subscriptions