Bug#983353: gnome-control-center is still not accessible with Orca screenreader

[Paul Gevers]

Package: release-notes

Hi,

To avoid to forget it

One release further. Can somebody, e.g. from the Debian Accessibility
Team, please at least check if this is still an issue? If not, we can
close the bug, if so, we can document it *again* [1] as I'm not
expecting it to get fixed in these last months if it's not fixed already.

having to press right arrow twice, having to use control-f then esc to
get back to the panel list (not able to select a result element with the
keyboard). So the same text would be needed.

Paul

[Debian Bug Tracking System]

Your message dated Sat, 27 Feb 2021 22:08:02 +0100
with message-id <0ade5d3d-221b-d57f-0571-***@debian.org>
and subject line Committed release-notes changes
has caused the Debian Bug report #983353,
regarding gnome-control-center is still not accessible with Orca screenreader
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sat, 27 Feb 2021 22:08:02 +0100
with message-id <0ade5d3d-221b-d57f-0571-***@debian.org>
and subject line Committed release-notes changes
has caused the Debian Bug report #981582,
regarding release-notes: bullseye to be the last release to support non-merged /usr layout
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sat, 27 Feb 2021 22:08:02 +0100
with message-id <0ade5d3d-221b-d57f-0571-***@debian.org>
and subject line Committed release-notes changes
has caused the Debian Bug report #947915,
regarding release-notes: Suggest cleaning up leftover *.dpkg-old etc. config files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sat, 27 Feb 2021 22:08:02 +0100
with message-id <0ade5d3d-221b-d57f-0571-***@debian.org>
and subject line Committed release-notes changes
has caused the Debian Bug report #948445,
regarding release-notes: aptitude search for not-from-Debian package has false negatives
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

Your message dated Sat, 27 Feb 2021 22:08:02 +0100
with message-id <0ade5d3d-221b-d57f-0571-***@debian.org>
and subject line Committed release-notes changes
has caused the Debian Bug report #945960,
regarding removal of src:lilo from bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)