National Lottery Heritage Fund Digital Requirements: A Practical Guide for Applicants

LAST UPDATED: November 2026

Planning a heritage project? Learn how to meet the National Lottery Heritage Fund's digital requirements, what to include in your application and how to choose a cost-effective platform for your project.

 

 

If you're applying for funding from the National Lottery Heritage Fund to digitise historical collections, record oral histories, create an online exhibition or make local heritage more accessible, there's an important part of your application you need to plan for: what happens to the digital material your project creates.

The Fund wants the heritage it supports to remain accessible and useful long after the funded project has finished. That means applicants need to think about more than digitisation equipment, website development or the immediate costs of delivering their project.

You'll need to explain how your digital outputs will remain available, how people with disabilities will be able to access them, and how others will be permitted to use and share them.

These requirements can seem daunting, particularly for smaller museums, libraries, historical societies and community heritage groups without dedicated technical staff.

Much of the work comes down to making the right decisions early: choosing suitable technology, understanding copyright and permissions, planning for accessibility and allowing for ongoing costs.

This guide explains the Fund's digital good practice requirements, what they mean for your project and how to address them in your funding application. We've also included a practical checklist and an accompanying briefing showing how YourArchive can support these requirements.

What counts as a digital output?

The National Lottery Heritage Fund defines digital outputs broadly. Essentially, if your funded project creates something in digital form that gives people access to heritage or helps them learn about it, it's likely to count.

Examples include:

  • Digitised photographs, documents, newspapers and historical records

  • Oral history recordings, interviews and video

  • Online exhibitions, learning resources and digital publications

  • Digital catalogues, databases and research material

  • Websites and mobile applications

  • 3D models, virtual tours and interactive heritage experiences

  • Software and code developed as part of the project

For example, a local historical society might receive funding to digitise its photographic collection, record interviews with residents and publish an online exhibition.

Each of those activities creates digital outputs that need to be considered in the application.

The Fund's digital good practice requirements apply to grants of £10,000 and above.

Applicants need to explain how they will meet the relevant requirements, include the necessary activities in their project plan and account for associated costs in their budget.

It's worth identifying every planned digital output before you start writing the application. A project may create more digital material than initially expected, including promotional videos, educational resources, research reports or recordings of community events.

The three digital requirements explained

The Fund's guidance focuses on three principles: availability, accessibility and openness.

The specific requirements depend partly on the size of your grant.

National Lottery Heritage Fund digital requirements by grant size
Requirement Grants of£10,000 to £250,000 Grantsover £250,000
Availability 5 years Digital outputs must remain publicly available for at least 5 years after the project ends 20 years At least 20 years after the project ends
Accessibility WCAG 2.2 Level A Websites and content must meet WCAG 2.2 Level A as a minimum WCAG 2.2 Level AA WCAG 2.2 Level AA as a minimum
Openness Open licence Digital outputs should generally be shared under an accepted open licence, with recognised exceptions Open licence The same licensing principles apply

Source: National Lottery Heritage Fund, Digital good practice guidance (opens in a new tab) (updated 26 October 2026)

The Fund's default open licence is Creative Commons Attribution 4.0 (CC BY 4.0). Other accepted options include the Open Government Licence v3.0 and CC BY-SA 4.0. Separate requirements apply to metadata, data and software.

These requirements affect decisions about where your digital collection will be hosted, how content is presented, what permissions you collect and which technology you use.

Let's look at each in more detail.

Availability: keeping your digital heritage accessible

A digital heritage project shouldn't disappear when its funding ends.

The Fund expects digital outputs to remain publicly accessible, without unnecessary restrictions, for the required five- or twenty-year period.

This doesn't mean you need to maintain your own servers or continually update the content. It does mean you need a credible plan for keeping it available.

What should you consider?

Where will your digital outputs be hosted?

Will your organisation use a specialist digital archive platform, an established repository or a bespoke system?

Consider whether your chosen solution can accommodate the amount and type of material you expect to create.

Who will be responsible after the project finishes?

Many community heritage projects rely heavily on volunteers or short-term project staff.

Your application should identify who will take responsibility for the collection once the funded activities are complete.

How will ongoing costs be covered?

If your digital archive requires hosting, storage, technical support or a subscription, these costs need to be considered from the beginning.

For a project with a twenty-year availability requirement, it's particularly important to understand the long-term financial implications.

What happens if you need to move your collection?

Technology changes, suppliers change and organisations sometimes merge or close. Make sure you understand how your digital files and associated information can be exported and transferred elsewhere.

Ideally, you should retain access to complete copies of your files and metadata in formats that can be used by another system.

What to include in your funding application

Your application should explain:

  • Where the digital outputs will be hosted and made publicly accessible

  • How the required availability period will be met

  • Who will be responsible for managing access after the project ends

  • What ongoing costs are anticipated and how they will be funded

  • How files and metadata could be transferred if hosting arrangements change

You don't necessarily need every technical detail finalised before applying, but your plan should demonstrate that you've considered the long-term responsibilities.

How YourArchive can help

YourArchive provides cloud-hosted digital archives with public, private and hybrid access options.

Projects can create publicly accessible collections and galleries without requiring visitors to log in. The platform also supports bulk export of files and metadata, helping organisations retain control over their collections if they need to move them in future.

Preservation masters are held separately from published content, with integrity checks and tools to support format management.

Hosting arrangements can be planned around a project's required availability period, with costs quoted according to storage needs and timescales.

For a Heritage Fund project, it's important to agree a suitable hosting and continuity plan before making commitments in your application.

Accessibility: making digital heritage usable by everyone

Accessibility is often one of the most challenging aspects of a digital heritage project, particularly when collections contain large numbers of photographs, scanned documents, recordings or interactive experiences.

The Fund expects digital outputs to be accessible to people with disabilities.

This includes people who use screen readers, navigate websites using a keyboard, need captions or transcripts, enlarge text or require information to be presented in alternative formats.

The relevant standard is the Web Content Accessibility Guidelines (WCAG) 2.2, developed by the World Wide Web Consortium (W3C).

Which accessibility level applies?

WCAG 2.2 has three conformance levels: A, AA and AAA.

For Heritage Fund grants:

  • Projects receiving £10,000 to £250,000 must meet at least Level A.

  • Projects receiving more than £250,000 must meet at least Level AA.

  • Public sector organisations may already be subject to additional accessibility obligations, including Level AA requirements.

The Fund recommends aiming for Level AA wherever possible, even when the minimum requirement is Level A.

What does accessibility mean for a heritage collection?

Different types of digital heritage present different challenges.

Historical photographs and images

People using screen readers need text alternatives that communicate the important information contained in an image.

For example, a photograph in a local history collection might have the following alternative text:

Workers standing outside a brick factory in Southampton, approximately 1925.

A longer catalogue description could provide names, historical context, dates and other information useful to researchers.

For large photographic collections, creating meaningful descriptions can take considerable time. This is worth including in your staffing and volunteer plans rather than treating it as an activity to complete after digitisation.

The W3C's alt text decision tree provides useful guidance.

Oral histories, audio and video

Oral history projects are particularly valuable for capturing community memories, but recordings need to be accessible.

Plan to provide:

  • Accurate transcripts for audio recordings

  • Captions for recorded video

  • Descriptions of important visual information where required

  • Accessible controls for playing, pausing and navigating recordings

Automatic transcription can significantly reduce the amount of manual work, but transcripts and captions should still be checked.

Historical names, local place names, regional accents and specialist terminology are particularly prone to transcription errors.

Scanned documents and publications

A scanned newspaper, handwritten letter or historical report may look perfectly readable on screen but still be difficult for someone using assistive technology.

Optical Character Recognition (OCR) can make text within scanned documents searchable, but OCR alone doesn't necessarily make a document accessible.

Depending on the material, additional work may be needed to provide readable text, a logical document structure and appropriate descriptions.

For new reports and learning resources, use proper headings, lists and tables when creating the documents, rather than relying on visual formatting.

Virtual tours and interactive exhibitions

Virtual tours, interactive maps and digital timelines can be excellent ways to explore heritage.

However, they may create barriers for visitors who cannot use a mouse, have visual impairments or rely on assistive technology.

Consider whether visitors can navigate using a keyboard and whether the same heritage information can be accessed in another format.

For example, a virtual tour of a historic building could be accompanied by a written room-by-room guide with descriptions of the exhibits.

Accessibility testing

Accessibility should be considered throughout the project, not simply checked before launch.

A sensible approach includes automated testing, manual checks and, wherever possible, testing with people who use assistive technology.

Useful tools include:

Automated tools cannot identify every accessibility problem. Keyboard navigation, screen-reader compatibility and the quality of alternative text also require human assessment.

For projects with substantial collections, build accessibility checks into the cataloguing and publication process so that newly added material follows the same standards.

What to include in your funding application

Explain:

  • Which WCAG 2.2 level applies to your project

  • How your chosen website or platform will support accessibility

  • Who will create and check alternative text, captions and transcripts

  • How interactive content and downloadable documents will be made accessible

  • What accessibility testing will take place and when

  • How accessibility issues will be identified and addressed

Include time and costs for these activities in your project plan.

How YourArchive can help

YourArchive supports descriptive metadata for individual archive items, automatic transcription of audio and video, and OCR for searchable text within documents and images, including handwriting.

Projects can also configure aspects of their archive's appearance and presentation.

These capabilities can support accessible heritage delivery and reduce manual cataloguing work.

However, accessibility depends on the complete published experience, including platform interfaces, content, configuration and any custom features.

Using an archive platform with accessibility features does not automatically establish WCAG conformance. Applicants should discuss their specific requirements with their supplier, obtain appropriate accessibility evidence and plan for testing.

Openness: copyright, permissions and sharing heritage

The Fund generally expects digital outputs created with its funding to be openly licensed.

The principle is that publicly funded heritage should be available for people to access, learn from and reuse, wherever rights and ethical considerations allow.

The default licence is Creative Commons Attribution 4.0 (CC BY 4.0). This allows others to copy, share and adapt material, including for commercial purposes, provided they give appropriate credit.

The Fund also accepts certain alternative open licences.

Metadata and data are generally expected to be released under CC0 1.0, while software should use an appropriate open software licence.

Why copyright planning matters

Digitising an old photograph doesn't necessarily mean your organisation owns the copyright.

A local museum might hold the physical print, but the photographer or their estate may still hold rights in the image.

Similarly, an oral history recording can involve rights belonging to the interviewer, interviewee and recording organisation.

Before publishing and openly licensing material, you'll need to establish what rights exist and whether you have permission to share it under the proposed terms.

For community heritage projects, this may involve:

  • Identifying copyright holders

  • Obtaining permissions from photographers and contributors

  • Agreeing appropriate rights with contractors and volunteers

  • Recording consent for oral history interviews

  • Keeping a record of the licence attached to each digital item

The Fund's guidance on working with open licences provides further information.

What about public-domain material?

Some historical material is no longer protected by copyright.

The Fund's guidance makes clear that creating a digital reproduction of a public-domain work should not create new rights over that reproduction.

Digital reproductions of public-domain material should be clearly identified and made available under CC0 1.0 or an equivalent public-domain dedication.

This is particularly relevant to organisations digitising older photographs, publications and historical documents.

However, don't assume that an item is in the public domain simply because it's old. Copyright duration can vary according to the type of work, its creator and other circumstances.

What about sensitive material?

Not every heritage item is suitable for unrestricted public access or reuse.

The Fund recognises exceptions to its default open-licensing requirements for certain types of material, including:

  • Material depicting people currently under 18

  • Material containing special category personal data

  • Material produced by, or depicting, adults at risk of harm

Ethical considerations may also arise when working with culturally sensitive collections, funerary material or heritage associated with particular communities.

These exceptions don't automatically mean that all such material must remain private. Appropriate arrangements depend on the content, permissions, risks and circumstances.

The important point is to identify potential issues early, establish suitable arrangements and discuss any proposed exceptions with the Fund.

Avoid assuming that a single access or licensing policy will be appropriate for every item in your collection.

Start at question 1 for each item. Yes leads to the answer; no leads to the next question.

  1. Question 1: Is the material sensitive?

    For example, it depicts people under 18 or adults at risk of harm, contains special category data such as some oral histories, or is culturally sensitive.

    If yes: Agree an alternative arrangement

    The Fund accepts exceptions. Decide on suitable access, record why, and discuss it with the Fund.

  2. If no, question 2: Is it a digital copy of a public domain work?

    Copyright has expired. Don't assume this just because an item is old.

    If yes: Mark it with CC0 1.0

    Digitising a public domain work doesn't create new rights, so don't claim any.

  3. If no, question 3: Is it metadata, data or code?

    Catalogue records, datasets, or software developed by the project.

    If yes: CC0 1.0 or an open software licence

    CC0 1.0 for metadata and data; an open software licence for code.

  4. If no, question 4: Do you hold the rights, or have permission to openly license it?

    From photographers, contributors, interviewees, volunteers and contractors.

    If yes: Use CC BY 4.0

    The Fund's default. OGL v3.0 and CC BY-SA 4.0 are also accepted.

  5. If no, question 5: Can the rights holder be identified and traced?

    If yes: Ask for permission

    Once you have it, go back to question 4.

  6. If no: It's likely an orphan work

    Don't openly license it. Record what you know and take advice before publishing.

Whichever licence applies, display the licence badge and an attribution statement clearly next to each output.

What to include in your funding application

Your project plan should explain:

  • How copyright and permissions will be investigated

  • Which open licences you intend to use

  • How rights and licensing information will be recorded and displayed

  • How contributors will give permission for material to be used

  • Whether any collections require restricted access or alternative arrangements

  • Who will be responsible for rights management

For projects involving community contributions, permissions should be built into the submission process from the outset.

How YourArchive can help

YourArchive allows projects to record rights, permissions and licence information against individual items using configurable metadata fields.

This means openly licensed material and content requiring restrictions can be managed within the same archive.

Public access, download permissions, redaction and user roles can be configured according to the needs of the collection.

Community contributions can also pass through moderation before publication, with consent information recorded as part of the process.

Projects remain responsible for obtaining appropriate permissions and deciding which material can be openly licensed.

What should you budget for?

One of the easiest mistakes when planning a digital heritage project is to concentrate on the cost of creating the digital material without fully accounting for the work involved in publishing, managing and maintaining it.

The Fund expects applicants to plan and budget for activities needed to meet its digital requirements.

Depending on your project, these might include:

What to consider when budgeting for a Heritage Fund digital project
Budget area What to consider
StaffingNew project posts or extra hours for existing staff, and specialist freelancers such as an oral historian. All project staff must be paid at least the Living Wage
DigitisationScanning equipment, photography, specialist services and file preparation
Digital platformSetup, hosting, storage, subscriptions and technical support
Long-term availabilityHosting or repository arrangements for the required period
CataloguingStaff or volunteer time to organise, describe and upload material
AccessibilityAlternative text, transcription checking, captions, document preparation and testing
Copyright and permissionsRights research, contributor agreements and consent management
TrainingHelping staff and volunteers use new equipment and systems, and follow agreed procedures
Community engagementWorkshops, scanning days, oral history sessions and outreach
Monitoring and reportingCollecting evidence of participation, access and project outcomes
ContingencyAllowance for unexpected technical or delivery requirements

Not every project will need every item, and some activities may be delivered by volunteers. However, both staff and volunteer time need to be planned realistically. Digital work often takes longer than expected, and the Fund will want to see that your project has the capacity to deliver what it promises.

For example, digitising 2,000 historical photographs may be relatively straightforward. But identifying the people pictured, writing descriptions, checking permissions and preparing the collection for publication could take substantially longer. Estimate the hours each task will need, decide who will do it, and make sure your staffing and volunteer plans reflect that.

If you’re a voluntary sector organisation, the Fund also encourages you to include full cost recovery in your budget. This covers a fair share of running costs that support the project, such as management time, rent and utilities, and can be important for your organisation’s sustainability. Public sector organisations aren’t eligible. The National Lottery Community Fund has guidance on calculating full cost recovery.

Think beyond the funded delivery period

If your project must keep its digital outputs publicly accessible for twenty years, consider what arrangements will support that commitment.

Ask potential suppliers for clear information about hosting, storage, renewal costs, export options and what happens if the service ends.

The objective is to demonstrate that the project has a realistic plan for its digital legacy.

Bespoke website or existing digital heritage platform: which is right for your project?

When planning a digital heritage project, many organisations assume they'll need to commission a new website to display their collections.

A bespoke website can be an excellent option, particularly for projects with unusual technical requirements or highly customised visitor experiences. But it's worth considering whether an existing digital heritage platform could deliver what you need without the cost and complexity of building a system from scratch.

The important question is whether your project needs custom-developed software, or an established way to manage, preserve and share its digital heritage.

Look beyond the initial development cost

A bespoke website quote may cover the design, development and launch of your online exhibition or archive. But what happens afterwards?

If your project needs visitors to search thousands of historical photographs, explore oral history recordings, contribute memories or access material with different copyright permissions, these capabilities may need to be developed separately.

There are also ongoing considerations: hosting, security updates, accessibility testing, technical support and ensuring the system continues working as technology changes.

For a Heritage Fund project with a five- or twenty-year public availability requirement, those long-term costs matter.

What does a purpose-built heritage platform offer?

Specialist digital archive platforms already include many of the tools heritage projects would otherwise need to commission.

For example, YourArchive brings together digital collection management, searchable photographs and documents, oral history recordings, community contributions, permissions management and a public-facing heritage portal within one platform.

Features such as OCR, automatic transcription, facial recognition to help identify people in historical photographs, and interactive Virtual Spaces are also available without needing to develop them individually.

Because the underlying software is already established, organisations can concentrate more of their project time and budget on digitising collections, recording stories and involving their communities.

A platform approach may also simplify ongoing technical maintenance, although applicants should still check hosting costs, accessibility, data export arrangements and long-term support.

Compare the full cost of both approaches

Before committing to a bespoke website, ask potential suppliers to provide costs covering the full period your digital outputs need to remain available.

Compare initial setup and development alongside ongoing hosting, maintenance, accessibility, collection management, technical support and future changes.

An existing platform may be considerably more cost-effective, especially for smaller heritage organisations that don't have their own technical teams.

However, the lowest initial price isn't necessarily the best value. The right solution is one that meets your project's needs, supports the Fund's requirements and remains manageable after the funding period ends.

Worked example: planning a community heritage project

Let's imagine a local historical society is applying for £75,000 from the National Lottery Heritage Fund.

Its proposed project will:

  • Digitise 1,500 historical photographs

  • Record 30 oral history interviews with local residents

  • Create a publicly accessible online exhibition

  • Invite community members to identify people and places in the photographs

  • Produce learning resources for local schools

How might the society address the Fund's digital requirements?

Availability

Because the proposed grant is £75,000, the society plans to keep its digital outputs publicly accessible for at least five years after the project finishes.

It identifies a suitable archive platform, obtains hosting costs and assigns responsibility for the collection to its committee.

The project plan also includes an arrangement for exporting files and metadata if the collection needs to move.

Accessibility

The society plans to meet WCAG 2.2 Level A as a minimum, while aiming for Level AA where practical.

Volunteers will create descriptions for photographs, and oral history recordings will be accompanied by checked transcripts.

The online exhibition and learning resources will be tested for accessibility before publication.

Openness

The society will investigate copyright ownership and obtain permissions from contributors.

Eligible digital outputs will be published under the required open licences, with rights and attribution information recorded.

Any material requiring restrictions will be identified and managed through an agreed process.

Community engagement

Residents will be invited to contribute photographs, share memories and help identify people in historical images.

The project will establish clear submission terms, consent arrangements and moderation procedures.

Budgeting and delivery

The budget includes digitisation, platform hosting, volunteer training, transcription checking, rights management and accessibility testing.

The society also plans to monitor engagement with the online collection and report on the project's outcomes.

Where YourArchive could support the project

A platform such as YourArchive could bring these activities together in one environment.

The society could publish its photographs and recordings in a searchable public archive, use transcription and OCR to improve discoverability, invite moderated community contributions and record permissions alongside individual items.

Analytics could help the project understand how people are engaging with the collection and provide evidence for reports to funders and trustees.

This is an illustrative example rather than a template for every application. The precise requirements, costs and evidence would depend on the project and the Fund's assessment.

Choosing a digital archive platform for your Heritage Fund project

Your choice of technology can have a significant effect on whether your project can meet its commitments.

It's worth evaluating potential platforms before finalising your application, particularly if the project involves substantial collections, sensitive material or a long-term public access requirement.

Here are some useful questions to ask suppliers:

Can the platform keep our digital outputs publicly accessible?

Check whether visitors can access funded material without creating an account, paying a fee or requesting permission.

If the platform also offers private collections, establish how public and restricted content will be separated.

Can we export our complete collection?

Ask whether you can download original files, descriptive metadata and associated information in formats suitable for transfer to another system. Find out whether exporting requires supplier assistance or additional charges.

How does the platform support accessibility?

Ask what accessibility testing has been completed, whether the relevant interfaces have been assessed against WCAG 2.2 and what documentation the supplier can provide.

Find out how the platform handles alternative text, captions, transcripts and keyboard navigation.

Can we manage copyright and licensing at item level?

Heritage collections frequently contain material with different copyright holders, permissions and access requirements. Check whether the platform can record and display this information clearly.

Can our community contribute?

If your project involves collecting memories, photographs or oral histories from residents, ask how contributions are submitted, moderated and approved. Consider how permissions and consent will be recorded.

What will it cost over the required period?

Understand the complete cost of hosting, storage, technical support and any additional services. For longer projects, discuss how future pricing and continuity arrangements will be managed.

Can we demonstrate the project's impact?

The Fund will want to understand what your project achieves.

Look for ways to measure engagement, participation and use of the digital collection. This might include visitor activity, collection views, community contributions and other relevant outcomes.

Choosing a platform that supports these activities from the beginning can reduce the amount of additional work your project team needs to undertake.

National Lottery Heritage Fund digital requirements checklist

Use this checklist while preparing your application, project plan and budget.

Identify your digital outputs

  • List every digital output your project expects to create.
  • Confirm the relevant availability period and accessibility level for your grant.

Plan for availability

  • Identify where your digital outputs will be hosted.
  • Confirm that funded outputs can be accessed publicly, without a login, payment or other restrictions.
  • Plan for five or twenty years of availability, as applicable.
  • Identify who will manage the collection and access after the project finishes.
  • Check that files and metadata can be exported.
  • Include appropriate hosting and continuity costs.

Plan for accessibility

  • Establish the WCAG 2.2 level your project must meet.
  • Discuss accessibility evidence and requirements with your website or platform supplier.
  • Plan alternative text and descriptions for images.
  • Provide appropriate captions and transcripts for recordings.
  • Check colour contrast, keyboard access and text resizing.
  • Consider accessible alternatives for interactive content.
  • Make downloadable documents accessible.
  • Budget for accessibility testing and improvements.
  • Plan an accessibility statement and contact arrangements where appropriate.

Plan for copyright and openness

  • Identify copyright holders and any existing restrictions.
  • Decide which accepted open licences will apply.
  • Establish how licence and attribution information will be displayed.
  • Prepare permission and consent arrangements for contributors.
  • Record rights information alongside digital items.
  • Identify sensitive material requiring alternative arrangements.
  • Discuss any proposed exceptions with the Fund.

Plan your delivery and budget

  • Allow sufficient time for cataloguing and metadata.
  • Budget for staffing, hosting, accessibility, permissions and training.
  • Identify staff and volunteer responsibilities.
  • Agree how community contributions will be managed.
  • Plan how you will monitor engagement and report outcomes.

Planning your Heritage Fund application?

The National Lottery Heritage Fund's digital requirements are much easier to address when they're considered from the beginning.

Decisions about hosting, accessibility, copyright, community participation and long-term preservation will influence the technology you choose, the people you involve and the costs you include in your application.

Choosing an established digital archive platform can also mean more of the available funding goes towards digitising collections, recording stories and engaging communities, rather than developing and maintaining bespoke software.

Download: How YourArchive Supports the Heritage Fund's Digital Requirements

We've prepared a briefing that maps the Fund's digital good practice requirements against YourArchive's capabilities, covering availability, accessibility, open licensing, permissions, preservation and project planning.

It's designed to help you evaluate your digital archive options and plan the technical aspects of your funding application.

If you're preparing a Heritage Fund application and considering a digital archive or online exhibition, we're also happy to discuss your project and provide a tailored quotation to help with your budget. Talk to us about your project, or book a short demonstration to find out more.

Sources and further reading:

FAQs:

Do the National Lottery Heritage Fund's digital requirements apply to my project?
The requirements apply to grants of £10,000 and above where the project creates digital outputs. These include digitised photographs, oral history recordings, online exhibitions, databases, learning resources, 3D models and websites. Your application should explain how you'll meet the requirements and include the necessary activities and costs in your project plan and budget.

How long do digital outputs need to stay available?
For grants of £10,000 to £250,000, digital outputs must remain publicly available for at least five years after the project ends. For grants over £250,000, the requirement is 20 years. You don't have to host them yourself or continually update them, but you need a credible plan for keeping them accessible throughout the required period.

Which WCAG accessibility level does my project need to meet?
Grants of £10,000 to £250,000 must meet WCAG 2.2 Level A as a minimum, while grants over £250,000 must meet Level AA. Public sector organisations may already have additional legal accessibility obligations. The Fund recommends aiming for Level AA wherever possible.

If I use an accessible archive platform, does my project automatically meet WCAG?
No. Accessibility depends on the complete published experience, including your content, alternative text, captions, colour contrast, navigation and platform configuration. A digital archive platform can provide useful accessibility features, but your organisation remains responsible for meeting the relevant requirements and should plan for appropriate testing.

Which open licence should we use for our Heritage Fund project?
The Fund's default is Creative Commons Attribution 4.0 (CC BY 4.0). It also accepts the Open Government Licence v3.0 and CC BY-SA 4.0. Metadata and data should generally be released under CC0 1.0, while software should use an appropriate open software licence. Check that you have the necessary rights and permissions before applying any licence.

Do oral history recordings have to be openly licensed?
Not necessarily. The Fund recognises exceptions to its open-licensing requirements for certain sensitive material, including recordings containing special category personal data. However, oral histories aren't automatically exempt. Projects should consider the content of each recording, obtain appropriate permissions and discuss any proposed exceptions with the Fund.

We own the original photographs. Can we openly license the digital copies?
Owning a physical photograph doesn't necessarily mean you own its copyright. The photographer or their estate may still hold the rights, so check before applying an open licence. Digital reproductions of public-domain works should generally be released under CC0 1.0. Where the copyright holder cannot be identified or located, the material may be an orphan work and will require separate rights assessment before publication or reuse.

What digital costs should we include in our Heritage Fund application?
Your budget should account for hosting, accessibility testing and rights management, alongside activities such as cataloguing, writing alternative text, checking transcripts and captions, staffing costs and training volunteers. You'll also need to consider how digital outputs will remain publicly available for the required five- or 20-year period.

Do we need to commission a bespoke website for a Heritage Fund project?
Not necessarily. A bespoke website may suit projects with unusual requirements, but it can involve additional development, hosting, security, accessibility and maintenance costs. An established digital heritage platform such as YourArchive already includes a public-facing portal, collection management and community engagement tools, potentially making it more cost-effective over the required availability period.

Next
Next

How to Host a Community Scanning Day