Community
Participate
Working Groups
There will be some efforts on the accessibility of Memory Analyzer. Let's use this message as a central place for tracking all accessibility related issues. If you find some - add it as a blocker here.
Below is the requirement for Helios. We'll use this message for documenting our compliance/activities in this area. Projects must document their accessibility work and compliance. Ideally this would be by using a publicly available checklists, such as * http://www.itic.org/resources/voluntary-product-accessibility-template-vpat/ * http://www.section508.gov/ * http://www.w3.org/TR/WCAG/ but, given the advice of the Accessibility Cross Project Team, for this year's Helios Simultaneous Release, projects can document their work or compliance as a negative, such as "we did not do any accessibility work or testing and do not know the degree of our compliance". But its important to document, so adopters know. If possible, and appropriate, accessibility testing tools can be leveraged such as NVDA. The main accessibility article at Eclipse Corner has been made current (thanks goes to Todd Creasey).
We at IBM are currently running accessibility testing on Memory Analyzer and will be submitting bug reports and patches. The first of these has been raised by Jonathan Lawrence here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=340196
The guidelines we aim to conform to are here: http://www-03.ibm.com/able/guidelines/software/accesssoftware.html
Thank you for the efforts in this area and for the (already done and upcoming) contributions! I will try to verify the patchens in reasonable time, and to include as much as possible in the Indigo release. Looking forward to working togehter on this topic. I added bug 340196 to the "depends on" list of this one. Let's use this one as a central place to track accessibility related fixes.
I think it doesn't make sense to keep this bug forever, as it is a central reference point for MAT's accessibility. I created a very short page in the Wiki, pointing to the guildlines which were used for the analysis and to a bugzilla query will all bugs containing the keyword "accessibility". https://wiki.eclipse.org/MemoryAnalyzer/Compliance_to_Accessibility_Guidelines I still have to mark all bugs referenced here. And in the future we should put the keyword, instead of marking the new bug as dependency for this one.
Closing the ticket. I moved the information from this bug into wiki, as menstioned in the previous comment.
