Hi,
I think we all agree that library software is immensely complicated and will continue to increase in complexity. However, my understanding is that the NDE was always intended to be built with accessibility
in mind. Testing after a general release seems like an afterthought unless substantial accessibility work has already been happening. Have unit tests and code reviews been checking for, and fixing, accessibility issues all along?
On one hand, I understand not wanting to be overwhelmed with customer feedback. However, the product is suppose to work for us. Based on my experience with consortia functionality in Primo VE, I fear that
by the time we're allowed to provide feedback the design will be too inflexible and fixing our issues will require substantially more work than if issues were caught earlier.
It seems like more two-way communication with Ex Libris customers could save everyone time and frustration in the long run.
--Gem
-------
Gem Stone-Logan
Senior Systems Analyst
California Digital Library, UC Office of the President
(she/her/hers)
From: Nili Natan <Nili.Natan@Clarivate.com>
Sent: Wednesday, April 2, 2025 7:36 AM
To: Mark Weiler <mweiler@wlu.ca>; Ex Libris user community discussion list for Primo/VE <primo@exlibrisusers.org>; eluna-accessibility@exlibrisusers.org
Subject: [Eluna-accessibility] Re: [EXTERNAL *] RE: Accessibility and rollout for Primo NDE
CAUTION: EXTERNAL EMAIL
Hi all,
We have published a phased accessibility plan for the NDE UI, working in an agile approach with an external company to ensure compliance. The March release referred
below was intended as a work-in-progress preview, not a finalized, compliant version.
The skip links support mentioned is planned in the August release, as mentioned in the
release plan . This information was also shared in a dedicated Q&A webinar we hosted this week for the early access group, which also included you Mark.
Feedback on accessibility related will be provided once our work with the external company reaches its final stages, not in the middle of it.
Best Regards
Nili Natan
Primo Product Manager
From: Mark Weiler <mweiler@wlu.ca>
Sent: Tuesday, April 1, 2025 10:02 PM
To: Ex Libris user community discussion list for Primo/VE <primo@exlibrisusers.org>; Nili Natan <Nili.Natan@Clarivate.com>;
eluna-accessibility@exlibrisusers.org
Subject: RE: [EXTERNAL *] RE: Accessibility and rollout for Primo NDE
I meant to write “The ‘Collection Discovery’ link at the cannot be accessed with the tab key”
From: Mark Weiler via Primo <primo@exlibrisusers.org>
Sent: March 31, 2025 3:36 PM
To: Nili Natan <Nili.Natan@Clarivate.com>; Ex Libris user community discussion list for Primo/VE <primo@exlibrisusers.org>;
eluna-accessibility@exlibrisusers.org
Cc: Mark Weiler <mweiler@wlu.ca>
Subject: [Primo] Re: [EXTERNAL *] RE: Accessibility and rollout for Primo NDE
Hi Nili, and everyone,
Based on the
link, I understand that there is a two-phase audit. The first phase should be done and inform the VPAT which is to be published by the end of May.
The second phase will happen in July-Sept, which will assess all resolved issues and evaluate additional page developed after general availability.
However, I was surprised when I found obvious issues in the version made available at this stage for customer feedback
- Language of the page seems to default to English. I tried toggling to French, but the text-to-French synthesizer wasn’t invoked
- JAWS can’t find headings on the search results page
- The “Collection Discovery” link at the can be accessed with the tab key
The video attached shows what I’m referring to. (And the Skip links to
bypass blocks seem to be gone; not shown in video)
I don’t see these issues mentioned in the
List of Known Issues.
So, here’s an outline of my concern:
- If the auditors spend their limited time catching obvious issues, then doesn’t it mean they won’t have time to identify some harder issues? Doesn’t that mean harder
issues will get through to customers and end-users?
- If Ex Libris developers didn’t catch the obvious issues (based on what’s in the List of Known issues), then how will the harder issues get identified by Ex Libris?
I would appreciate if Ex Libris could respond to these concerns and address any mistake I’ve made.
Sincerely,
Mark
From: Nili Natan <Nili.Natan@Clarivate.com>
Sent: March 20, 2025 4:07 AM
To: Ex Libris user community discussion list for Primo/VE <primo@exlibrisusers.org>;
eluna-accessibility@exlibrisusers.org
Cc: Mark Weiler <mweiler@wlu.ca>
Subject: [EXTERNAL *] RE: Accessibility and rollout for Primo NDE
Hi Mark, All,
We have published our
Accessibility
plan for the NDE UI in the
Available
Features, Functionality and Relase Plan for NDE UI.
We will continue to update this page with more information as our audit progresses and will publish the initial VPAT upon its completion.
Best Regards,
Nili Natan
Primo Product Manager
From: Mark Weiler via Primo <primo@exlibrisusers.org>
Sent: Wednesday, March 19, 2025 11:27 PM
To: 'primo@exlibrisusers.org' <primo@exlibrisusers.org>;
eluna-accessibility@exlibrisusers.org
Cc: Mark Weiler <mweiler@wlu.ca>
Subject: [Primo] Accessibility and rollout for Primo NDE
Hi Primo Product Team,
I had asked this question at the Primo NDE webinar today. Hoping the question can be responded here to the group:
What is the expected level of accessibility of the NDE for people with disabilities at each phase of the roll out (e.g., Generic Trial Environment; Managed General Release; General Release)? When I looked recently, there
were some obvious WCAG failures.
Thank you,
Mark
Mark Weiler, PhD (he & him)
JAWS certified and Web Accessibility Specialist
Web & User Experience Librarian
Wilfrid Laurier University
Waterloo, Ontario
548-889-5056
Notices
Upcoming
Laurier Library workshops & events
Confidentiality note: This e-mail may contain confidential information from Clarivate. If you are not the intended recipient, be aware that
any disclosure, copying, distribution or use of the contents of this e-mail is strictly prohibited. If you have received this e-mail in error, please delete this e-mail and notify the sender as soon as possible.
*
⚠ Notice:
This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Confidentiality note: This e-mail may contain confidential information from Clarivate. If you are not the intended recipient, be aware that any disclosure,
copying, distribution or use of the contents of this e-mail is strictly prohibited. If you have received this e-mail in error, please delete this e-mail and notify the sender as soon as possible.