Daniel Beck commented on Improvement JENKINS-26503

Andreas Mandel Thanks for the reminder. I'm still reading the longer report. I'm afraid that there's so much in Jenkins that just isn't designed with blind users in mind that I doubt we'll ever make significant progress there. Maybe once the forms are fully off tables, if we ever get to that.

I assume you're working with Michael? Are you or he one of the authors? If so, could you please clarify finding 2/9 (which links are not recognizable as such? Is color not sufficient?) and Seven Of Nine (Save/Apply work just like OK/Apply in tons of Windows config dialogs)


I just saw the following on the dev list:

For documenting purposes, we need to show internally that we have at least reported the issues back to the "tool vendor", I would like to create a JIRA ticket in the Jenkins JIRA. To this ticket I would like to attach the documents and for each finding from the report we could create a sub-task or a separate task where each issue can be discussed.

Is this already sufficiently done, or what's needed here?

We could also discussion of this report to the agenda of the next project governance meeting. Especially wrt. blind users, maybe we can decide on how much we want to do there. The meetings are public (on IRC), and publicly archived (http://meetings.jenkins-ci.org/jenkins/).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to