You can declare and update the WCAG conformance level of your content, along with related accessibility features, by uploading a metadata CSV through the Go1 bulk uploader. This guide shows you how to prepare your file and upload it.
Why this matters
Go1 customers can filter the catalogue by WCAG level to find content that meets their accessibility requirements. This is increasingly important for organisations operating under the European Accessibility Act and similar regulations, where teams need to verify content meets a specific WCAG standard before enrolling.
Only content with WCAG metadata appears in these filtered results. If your content meets WCAG 2.0 AA or above and you haven't declared it, customers using the accessibility filter won't see it — even if it would have been a strong match for their needs. Updating your metadata is the fastest way to keep your content discoverable to this audience.
The 8 accessibility metadata fields
The bulk uploader supports the following accessibility fields:
Field | Value | Instructions |
WCAG Level | One of: | Select the minimum WCAG conformance level the content meets. Leave blank if the content is not compliant with any of the above standards. |
Closed Captions |
| Whether the content has closed captions. If the content is video content, a Optional for interactive or link type content. |
Closed Captions File Name | The name of the file. Ensure the file name matches the file uploaded and include file extensions. Example: | Name of the caption file you've uploaded. Required when:
File formats supported: .vtt or .srt Size: max 20MB |
Closed Captions Language | ISO-639-1 code, with an optional ISO-3166 two character country code in uppercase separated by a hyphen. Example: | Language of the caption file. Required only for video content IF a closed captions file is uploaded. |
Transcript |
| Whether the content has a transcript. If the content is audio content, a Optional for video, interactive, and link type content. |
Transcript File Name | The name of the file. Ensure the file name matches the file uploaded and include file extensions. Example: | Name of the transcript file you've uploaded. Required when:
|
Transcript Language | ISO-639-1 code, with an optional ISO-3166 two character country code in uppercase separated by a hyphen. Example: | Language of the transcript file. Required only for audio content IF a transcript file is uploaded. |
Screenreader Compatible |
| Whether the content is compatible with screen readers. If the content is document or text content a |
Update WCAG metadata in bulk
Step 1: Export your current metadata
Sign in to your portal and go to the Content Manager
Select the items that you want to update
Select Export to download a CSV of your existing content metadata
Open the file in a spreadsheet tool
Step 2: Update the accessibility fields
In your CSV, update the relevant columns for each learning item:
Set WCAG Level to the level your content meets (or leave blank if it doesn't meet a WCAG standard)
Fill in the accessibility feature fields (Closed Captions, Transcript, Screenreader Compatible) based on what your content includes
For any caption or transcript files, enter the file name and language code
Save the file as a CSV when you're done.
Step 3: Open the bulk uploader
Go back to the Content Manager
Click on the Bulk manage content button
Select Update content
Select Go1 Premium
Click Next
Step 4: Upload your files
Drag your updated metadata CSV, and any closed captions or transcript files into the file upload area
The uploader will match files to learning items based on the file names in your CSV
Step 5: Review and resolve any errors
The bulk uploader checks your file as it processes:
Inline errors appear next to any rows that need fixing
A downloadable error report lists every issue with the matching error message
Successfully processed items move to the Processed tab, where you can review everything that was updated. Anything still showing on the Errors tab needs to be fixed and re-uploaded before its metadata will be saved.
Common errors and how to fix them:
Error | What to do |
| Check that WCAG Level exactly matches one of the 8 supported values |
| Add the mandatory accessibility field for that content type |
| Add the file name to the Transcript File Name or Closed Captions File Name column. Ensure the file name matches the file uploaded and include file extensions. |
| Add the language code to the Transcript Language or Closed Captions Language columns |
| Use ISO-639-1 (e.g. |
| Re-upload the file or correct the file name in your CSV. Ensure the file name matches the file uploaded and include file extensions. |
| Convert the file to a supported format |
| Compress or split the file before uploading |
Once all errors are resolved, confirm the upload to apply the changes.
FAQs
How do I clear the WCAG level for content that no longer meets a standard?
Leave the WCAG Level field blank in your CSV. When you upload the file, the bulk uploader will clear the existing value.
Which fields are required for which content types?
Certain accessibility fields are mandatory depending on the type of learning item:
Video content:
Closed Captions:
true/falseis required
Audio content:
Transcript:
true/falseis required
Document or Text content:
Screenreader Compatible:
true/falseis required
How can I check the content type of my learning items?
You can find the content type for each item in the Content Manager table. The content type is listed under the title. This determines which accessibility fields are required for that item.
Will edits made using the MyGo1 Editors overwrite my accessibility metadata?
No. Accessibility metadata you've set through the bulk uploader is preserved if you make further edits using the MyGo1 Editors.
Can I upload captions or transcripts in multiple languages for the same learning item?
Not yet. Each caption or transcript file currently supports a single language.
Related articles