Hello James, do you have any updates on a VPAT for OJS? I also just had an inquiry from a library interested in our journal that would like to know if we have an accessibility statement. We don’t have one independently, so it would be great to have one from PKP.
Amy Christian
amy@lysoncenter.org
Hi Amy, we don’t have a VPAT or a statement yet, but one of our staff is moving into a UI/UX role with that as part of his mandate, starting in April (which would be Monday). Our broad goal is to be able to have a certified review/audit of OJS and any necessary changes made for WCAG 2.0 compliance ASAP. Our staffer’s first task will be to outline a roadmap on this. That said, OJS already does quite well in terms of general accessibility compliance, and our developers work with accessibility in mind and part of the regular dev and review process. So long story short - we don’t have an official, certified statement yet, but we’re working on it and will have a roadmap soon; and in the meantime, OJS does perform to a high (if uncertified) accessibility standard by default.
Also - as you are a client of ours, please let me know via our support system if you’d like something like the above statement in a more formal way to pass on to the library. (If you email our support system with this request, just include a link to this thread and ask to be passed on to me.)
Cheers,
James
Hello James,
I was wondering how the accessibility work was going on the OJS 3.0 platform. We are a blindness organization that is current using the 2.0 platform for our Journal and would like to upgrade to 3.0.
I have been doing some initial testing of the site with a screen reader and have run into some issues. I will be asking our internal Accessibility specialists to take a look at what may be going on. If they are able to expand the issues that i found with this site would you be open to some feedback on accessibility for the next build?
Thanks,
Ross
Hi Ross - good to hear from you! Our accessibility work is proceeding in OJS 3. Right now we’re focusing on one of the common front-end themes, but we have plans for working on the admin back-end as well. The work we’re doing here consists of 1) a third-party audit of the work in question (again - first focus is on the front end, but next focus will be on the admin back-end); 2) a review of the audit by the PKP team, and outstanding issues addressed by the developers; 3) ongoing training and best practices implementation for the team. My colleague @israel.cefrin can provide more info on our work here. And we would 100% welcome feedback from your team. Israel can coordinate that (and make sure you are in the loop with respect to what we’re already working on, so that you don’t unnecessarily duplicate effort).
Thanks for reaching out!
James
Hi Ross, how are you?!
In my institution we are working on the W3c, applying them to our main web page and also others webs like OJS.
I am very gratefull to know that you have an Accessibility Statement and that you developed accessible front-end themes.
I want to know if you have any information about the admin back-end? Because we are going to be audited and it will be good to have some information about it.
Thank you very much for your answer!
Lorena