Bug #13503

Redmine: commenting on a ticket using a screen reader seems broken

Added by intrigeri 2017-07-22 07:09:13 . Updated 2017-10-17 13:48:42 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Accessibility
Target version:
Tails_3.3
Start date:
2017-07-22
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

See the “cannot comment tickets on Redmine with user pzajda” thread.

Subtasks

Related issues

Blocks Tails - Feature #13242: Core work: Sysadmin (Maintain our already existing services) Confirmed 2017-06-29

History

#1 Updated by intrigeri 2017-07-22 07:09:26

  • blocks Feature #13233: Core work 2017Q3: Sysadmin (Maintain our already existing services) added

#2 Updated by intrigeri 2017-07-22 07:10:37

  • Target version set to Tails_3.1

bertagaz: what I expect on this ticket is an initial investigation, i.e. reproduce the problem, check if it’s known upstream and report it there if it’s not. I don’t expect you’ll patch Redmine yourself to fix this problem.

#3 Updated by intrigeri 2017-07-22 07:10:46

  • Category changed from Infrastructure to Accessibility

#4 Updated by bertagaz 2017-08-09 14:29:26

  • Target version changed from Tails_3.1 to Tails_3.2

#5 Updated by anonym 2017-09-28 18:29:40

  • Target version changed from Tails_3.2 to Tails_3.3

#6 Updated by intrigeri 2017-10-01 10:00:51

  • blocks Feature #13242: Core work: Sysadmin (Maintain our already existing services) added

#7 Updated by intrigeri 2017-10-01 10:00:54

  • blocked by deleted (Feature #13233: Core work 2017Q3: Sysadmin (Maintain our already existing services))

#8 Updated by bertagaz 2017-10-13 10:53:21

  • Status changed from Confirmed to In Progress
  • Assignee changed from bertagaz to intrigeri
  • % Done changed from 0 to 20
  • QA Check set to Info Needed

intrigeri wrote:
> bertagaz: what I expect on this ticket is an initial investigation, i.e. reproduce the problem, check if it’s known upstream and report it there if it’s not. I don’t expect you’ll patch Redmine yourself to fix this problem.

I’ve given a try, but I’m not so used to screenreader, so that’s a bit difficult to say (that’s why I pinged pzajda by email).

In the meantime, I’ve found out that there was a ticket about that on Redmine’s Redmines with a patch that has been merged in 3.3.0. We’re using 3.3.1, so I guess we should be good on this front?

#9 Updated by intrigeri 2017-10-14 07:15:51

  • Assignee changed from intrigeri to bertagaz

I don’t understand what work you’re expecting me to do here. Please clarify.

#10 Updated by pzajda 2017-10-15 09:32:56

bertagaz wrote:
> I’ve given a try, but I’m not so used to screenreader, so that’s a bit difficult to say (that’s why I pinged pzajda by email).
>
> In the meantime, I’ve found out that there was a ticket about that on Redmine’s Redmines with a patch that has been merged in 3.3.0. We’re using 3.3.1, so I guess we should be good on this front?

Sorry for the delay.
As you can see, I can quote now.
I have an explicit link I hadn’t before to quote message.
The edit link is also OK.

#11 Updated by bertagaz 2017-10-17 13:48:42

  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • % Done changed from 20 to 100
  • QA Check deleted (Info Needed)

pzajda wrote:
> Sorry for the delay.
> As you can see, I can quote now.
> I have an explicit link I hadn’t before to quote message.
> The edit link is also OK.

No problem§ Happy to read that it is usable now. Closing this ticket then.