Aurora and WCAG 2.2 AA: Designing Accessible Digital Repositories from the Ground Up
Accessibility is no longer optional for digital repositories. For libraries, archives, and museums, it is both a legal expectation and a mission-driven responsibility. Digital collections exist to broaden access to knowledge and cultural heritage. If those collections are not accessible, the mission is incomplete.
Aurora was built with that responsibility in mind.
This article explains what WCAG 2.2 AA compliance means in practice, how Aurora approaches accessibility, and what institutions should understand about shared responsibility when deploying an accessible repository.
What WCAG 2.2 AA Actually Means
The Web Content Accessibility Guidelines version 2.2 define standards for making web content accessible to people with disabilities. Level AA conformance is widely considered the benchmark for public-facing institutional websites and digital platforms.
WCAG 2.2 AA addresses areas such as:
- Keyboard accessibility
- Screen reader compatibility
- Color contrast
- Focus visibility
- Error identification
- Accessible navigation and structure
For institutions operating public digital archives, meeting these standards is not simply about compliance. It is about ensuring equitable access to research materials, special collections, and institutional memory.
Aurora’s Accessibility Foundation
Aurora is built on Islandora and Drupal, both of which provide strong accessibility foundations when implemented thoughtfully. From the beginning, Aurora’s design has emphasized accessible structure, semantic markup, and compatibility with assistive technologies.
The accessibility of Aurora is documented through an Accessibility Conformance Report (ACR), based on the Voluntary Product Accessibility Template (VPAT®), which evaluates conformance against WCAG 2.2 Level A and AA criteria.
The most recent ACR evaluates the Islandora theme as deployed within Aurora. That testing reflects a fresh installation with representative sample content and outlines how specific success criteria are supported.
Accessibility is not a marketing claim. It is a documented, tested commitment.
Designing for Real Users
Accessibility is not just about passing technical checks. It is about real-world usability.
Aurora supports:
- Logical heading structures for screen readers
- Consistent keyboard navigation
- Proper focus indicators
- Accessible form labeling
- Color contrast that meets AA standards
- Clear error messaging
In repository environments, accessibility considerations extend beyond static pages. Digital objects often include images, PDFs, audio, video, and interactive viewers. Aurora’s architecture accounts for accessibility at both the interface and object-display levels.
In accessibility testing conducted as part of our ACR evaluation, certain interactive components such as viewers were assessed against WCAG 2.2 criteria. Where improvements were identified, they were documented transparently. Accessibility is treated as an ongoing engineering discipline, not a one-time checkbox.
Accessibility and Infrastructure
Accessibility does not operate in isolation from infrastructure.
Cloud-based hosting environments can support accessibility efforts through:
- Structured update cycles
- Predictable deployment processes
- Reduced dependency drift
- Consistent version management
When repository environments stagnate technically, accessibility improvements also stagnate. Modern infrastructure supports modern accessibility standards.
In modernization work we have supported, accessibility improvements often occur alongside platform upgrades and infrastructure redesign. An up-to-date system is easier to keep accessible than an aging one.
The Shared Responsibility Model
It is important to understand that accessibility is shared.
Aurora is designed to conform with WCAG 2.2 Level AA criteria as documented in its Accessibility Conformance Report. However, repository accessibility can be influenced by:
- Client-provided content
- Uploaded PDFs or media files
- Custom modules
- Client branding and color configuration
- Third-party integrations
For example, an inaccessible PDF uploaded into an otherwise accessible repository remains inaccessible content. Similarly, heavily customized front-end modifications may affect compliance if not implemented carefully.
This is why accessibility must be integrated into governance, not just technology.
Governance and Ongoing Accessibility
Institutions committed to accessibility should incorporate:
- Accessible content creation guidelines
- Regular review of uploaded materials
- Periodic accessibility testing
- Clear ownership of accessibility oversight
Aurora provides an accessible framework. Institutions strengthen that foundation through accessible content practices and governance.
In our work supporting institutional repositories, we have seen that the most successful accessibility outcomes occur when accessibility is embedded into both technology and workflow.
Why Accessibility Matters Strategically
Beyond compliance, accessibility supports:
- Broader research reach
- Inclusive community engagement
- Reduced legal exposure
- Stronger institutional reputation
Digital repositories often serve as public-facing windows into an institution’s intellectual and cultural assets. Accessible design ensures that those assets are available to the widest possible audience.
Accessibility also aligns with the core values of libraries and archives. Access is central to the mission. WCAG 2.2 AA is a modern expression of that mission in digital form.
Aurora’s Commitment
Aurora is designed to support WCAG 2.2 Level AA criteria, as documented in its Accessibility Conformance Report. Accessibility considerations are integrated into theme design, structural markup, navigation patterns, and component testing.
At the same time, we recognize that accessibility is an ongoing responsibility. Standards evolve. Technologies change. Institutional needs grow.
Discovery Garden works with institutions to ensure that accessibility is considered during implementation, migration, and modernization. We view accessibility not as a feature, but as part of responsible digital infrastructure.
If your institution is evaluating repository platforms and would like to review Aurora’s Accessibility Conformance Report or discuss how accessibility is addressed within your specific configuration, we are always open to a structured conversation. Accessibility is not an afterthought. It is foundational to sustainable digital collections.
Ready to see what Islandora can do for your Organization?
Whether you’re managing a single repository or supporting a multi-institution consortium, Islandora offers the flexibility, scalability, and support you need. Contact Discovery Garden to schedule a demo, start a project discovery session, or learn more about how we can help you build a future-proof digital repository.
Saínchez, Zaragoza à Pamplona y Barcelona—Puente de Zuera, photograph, The Metropolitan Museum of Art, Public Domain, 1999.138
