Study guide · Media and Accessibility

Media, accessibility and clean data exchange

As of November 15, 2026 · TYPO3 14.3 LTS · about 25 min read

Images and videos bring a website to life, but they often cause slow pages and barriers. Here you learn how to advise on formats, videos and accessibility. At the end we look at character encoding and CSV files, which come up in every data import.

A client project serves as the running example. The tourism association Seetal Holiday Region is getting a new website with TYPO3 14, and you accompany the project as a consultant. Four wishes are on the table:

  • A photo series “Hiking along the lakeshore” that looks good on phones and big screens.
  • A promotional film on YouTube and several of their own explainer videos.
  • An accessible website, because the association is partly publicly funded and offers online booking.
  • The import of the list of hosts from the old system, which comes as a CSV file.

Media in TYPO3: the Media module

TYPO3 manages all kinds of media: images, videos, audio files, PDFs and other documents. You upload them in the backend module Media. Since TYPO3 14, that is the name of the module formerly called “Filelist”. There you create folders, upload files, also by drag and drop, and move them. You also maintain the metadata of a file, such as title, description, alternative text and copyright.

Under the hood is the File Abstraction Layer, FAL for short. It separates where a file is stored from where it is used. By default, files live in the storage fileadmin on your own server. Extensions can connect further storages, for example WebDAV or a cloud storage such as Amazon S3. Editors then work with them in the Media module just like with local files.

When you use a file in a content element, TYPO3 creates a file reference. So TYPO3 knows every place where a file appears. This has two consequences:

  • A file that is still in use cannot be deleted. TYPO3 refuses, lists the places where it is used, and you remove those usages first.
  • Moving a file, on the other hand, is possible. The frontend output does not break, because the references point to the file and not to its path.

Which file extensions are allowed is set in the configuration of the installation. For images this is the setting imagefile_ext, for media the setting mediafile_ext.

Images: formats, cropping and loading time

In the default configuration of TYPO3 14, these extensions count as image formats: gif, jpg, jpeg, tif, tiff, bmp, pcx, tga, png, pdf, ai, svg, webp and avif. The list can be changed in the configuration.

Every format has strengths and weaknesses. The choice is always a trade-off between quality, file size and purpose:

  • JPEG compresses photos with their colour gradients well, but has no transparency. With strong compression it visibly loses quality.
  • PNG is lossless and supports transparency. For photos the files are usually too large, for graphics and screenshots it fits well.
  • GIF can animate, but knows only 256 colours.
  • SVG is a vector format. It stays sharp at any size and is ideal for logos, icons and simple graphics.
  • WebP and AVIF are modern formats. At comparable quality the files are usually much smaller than JPEG or PNG, and they support transparency.
  • BMP is uncompressed and unsuitable for the web.
Which format for which image? Photo many gradients JPEG · WebP · AVIF compresses well Logo, icon clear shapes SVG vector, always sharp Graphic with transparency PNG · WebP · SVG not JPEG: no transparency BMP: uncompressed not suitable for the web
Which format suits which image?

With modern formats you weigh things up: which browsers does the target audience use, and is image processing on the server set up for it? By the way, no format brings an alternative text along, it always belongs in the metadata.

A wide stage image looks great on a desktop. On a smartphone it rather needs a portrait format, otherwise the subject is tiny. That is why you often need images in different aspect ratios, so they look good on every device.

TYPO3 can crop images itself. In the content element you open the image editor, the cropper, and set a section. Often there are fixed aspect ratios to choose from. If the site package defines several crop variants, for example for desktop, tablet and smartphone, the template uses the right one for each output. With a focus area you mark the important part of the subject. The original file stays unchanged.

TYPO3 does the calculation on the server with GraphicsMagick or ImageMagick. With them TYPO3 scales images, crops them and converts them into other formats. Since TYPO3 14 you can also set the target format for processed images, for example converting everything to WebP.

If a client wants more, such as automatically generated WebP variants, focus points by click or further image optimisation, that usually comes from extensions in the TER. You assess them by maintenance, compatibility with TYPO3 14 and effort. Changing the Core code of image processing is not an option, because it blocks updates.

Videos: own files and YouTube

For your own videos, two formats matter most. MP4 with the H.264 codec plays in practically every browser. WebM is an open, efficient format and saves file size. Both are in the setting mediafile_ext by default in TYPO3 14. It also contains mov, m4v, ogg, mp3 and wav, among others, plus the two pseudo formats youtube and vimeo. AVI and WMV are not in the default list.

In the content element “Text & Media” you have two ways:

  • Add media file uploads a video file of your own. TYPO3 shows the allowed formats below the selection field.
  • Add media by URL embeds a video from YouTube or Vimeo. You simply paste the address of the video.

Data protection: An embedded player loads content from the provider’s server. Data is already transferred at that point, for example the visitor’s IP address. The Core does use privacy-friendlier variants without cookies or with “do not track”. Still, embedding by URL is not automatically compliant. Usually you need prior consent. The editors’ guide advises talking to the data protection officer and using an extension for consent. One example is b13 twoclickmedia. It works with the normal “Text & Media” element and only loads the video after someone has agreed.

For the client’s own explainer videos, you advise on three more points:

  • Captions: For prerecorded videos with sound, the WCAG require captions already at level A. That way deaf people and people without sound can follow the content.
  • File size: Videos are large. The server’s upload limit, storage space and bandwidth belong in the concept. Very large videos may be better embedded from an external platform.
  • No autoplay with sound: It disturbs many people and drowns out screen readers.

Accessibility: who sets the rules?

Accessibility means that a website can be used by everyone, including people with disabilities. That includes people using a screen reader, people who only use the keyboard and people with low vision.

A screen reader is software that reads screen content aloud or outputs it on a braille display. Well-known screen readers are NVDA and JAWS on Windows and VoiceOver on Apple devices. They depend on a clean structure: headings, landmarks, link texts and alternative texts.

The internationally recognised rules come from the W3C and its Web Accessibility Initiative, WAI for short. It publishes the Web Content Accessibility Guidelines, WCAG for short. The current version is WCAG 2.2.

The WCAG assign every criterion to four principles. Content must be perceivable, operable, understandable and robust, POUR for short. Below them are testable success criteria in three conformance levels: A is basic, AA is required by many laws, and AAA is the highest level.

The legal situation in the EU:

  • Websites of public bodies fall under EU Directive 2016 2102, the Web Accessibility Directive. In Germany it is implemented, among others, by the BITV 2.0.
  • Since 28 June 2025, the European Accessibility Act also applies to certain products and services of private providers, for example in online retail or booking services.
  • Both refer technically to the standard EN 301 549 and thus to WCAG criteria at level AA.

So in the EU, accessibility is not a voluntary recommendation, and there is no threshold based on visitor numbers. Whether an exception applies in a specific case, for example for micro-enterprises, needs a legal review. As a consultant you do not give legal advice.

An accessible frontend

Accessibility comes from three parties working together. The template provides landmarks, keyboard operation and a visible focus. The design ensures sufficient contrast. The editors maintain alternative texts, headings, link texts and understandable language. Exactly these points belong in the concept for an accessible relaunch.

Landmarks are page regions such as header, navigation, main content and footer. Screen reader users jump straight to a region with them, for example to the main content. In HTML they come from the elements header, nav, main, aside and footer. These match the ARIA roles banner, navigation, main, complementary and contentinfo. Elements such as span or strong have no landmark meaning. Each page should have exactly one main region.

Contrast: Too little contrast between text and background makes text hard to read for people with low vision or in bright light. That is why the WCAG define minimum ratios:

  • Level AA requires 4.5 to 1 for normal text and 3 to 1 for large text. Large means from 18 point, or from 14 point bold.
  • Level AAA requires 7 to 1 for normal text and 4.5 to 1 for large text.

Link texts should say where they lead even without the surrounding sentence. Many screen reader users have a list of all links read out. Ten times “click here” does not help there. “Download the hiking map as a PDF” is better. The editors’ guide recommends: first write the meaningful text, select it and then add the link.

Easy Read, in German “Leichte Sprache”, is a strongly simplified form of language. It uses short sentences, familiar words and a clear structure. This makes texts understandable for people with learning difficulties or limited language skills. Many websites offer such versions in addition and link them where they are easy to find, for example permanently in the header. Text in capital letters, on the other hand, tends to make reading harder.

Accessible images and alternative texts

The alternative text describes the information of an image for people who cannot see it. It is normally not visible. A screen reader reads it aloud, and the browser shows it if the image does not load. The caption, on the other hand, usually appears visibly below the image and gives all visitors additional information.

What belongs in the alternative text depends on the kind of image:

Which alternative text? informative hiking photo the information, briefly “Jetty on the lakeshore in fog” decorative ornament line empty alternative text screen reader skips it linked logo as a link the link target “Go to home page” complex chart short alternative text plus a table in the text Default in the metadata, override per content element.
The type of image determines the alternative text.
  • Decorative images without information get an empty alt attribute. The screen reader then skips them. If the attribute is missing entirely, some screen readers read out the file name.
  • Linked images that form the link on their own turn their alternative text into the link text. So it says where the link leads, for a logo for example “Go to home page”.
  • Complex images such as a ten-year revenue chart need two parts: a short alternative text for orientation and a detailed version nearby, for example as a data table. That is how the image tutorials of the W3C WAI describe it. Putting the whole data set into the alternative text makes it unreadable.

No text in images: Screen readers cannot read text in images. It becomes blurry when enlarged and does not adapt to contrast settings. Important text belongs on the page as real text.

Where do you maintain the alternative text? You maintain the default in the metadata of the file in the Media module. It then applies wherever the file is used. In the content element you can override it for that one place if the context needs a different statement. If the same hiking photo shows the product on an offer page and the mood in a blog article, it gets two fitting texts. You do not have to upload the file twice for that.

Testing accessibility

Only a mix of methods shows whether a website is really accessible:

  • Automated checking tools find easily detectable errors such as missing alternative texts or too little contrast. But they only cover part of the criteria.
  • Manual tests using only the keyboard reveal problems with focus and order.
  • Tests with a screen reader such as NVDA or VoiceOver show whether headings, landmarks, forms and link texts are read out understandably.

During acceptance you also check specifically whether the editors have set alternative texts.

The TYPO3 backend and accessibility

Editors may depend on accessibility too. So a public client often asks: is the backend fully accessible with a screen reader? The professionally correct answer names both the state and the limits.

The TYPO3 Accessibility Team tested TYPO3 14 during a sprint in autumn 2025. The benchmark was WCAG 2.2 criteria at level AA. The result: most controls are labelled for screen readers, and the backend has improved considerably from version to version. But the team still found barriers, for example in the search, the date picker and the file picker when used with the keyboard. On top of that, focus sometimes leaves a dialog window, and after saving there is no feedback for the screen reader.

You should also know two further limits:

  • The rich text editor is CKEditor 5. It is a third-party library whose limitations TYPO3 cannot fix on its own.
  • Drag and drop remains a hurdle for anyone who does not use a mouse. Make sure there is also a way to do such tasks without dragging.

There is currently no accessibility statement for the backend, let alone a certification at level AAA. But the backend is not unusable with screen readers either.

In the community, the Accessibility Team keeps working on improvements. It holds a monthly open session in the Slack channel accessibility, the Accessibility Hour.

If an editor works with the keyboard only, you can reassure her: the module menu and the help menu can be operated with the keyboard alone. For the page tree, the editors’ guide helps. It follows the patterns of the WAI-ARIA Authoring Practices:

  1. She reaches the page tree with the Tab key.
  2. Arrow up and arrow down move the focus between entries.
  3. Arrow right expands an entry, arrow left collapses it.
  4. Enter selects the page or expands it.
  5. Home and End jump to the first and the last entry.

Character encoding

A character encoding assigns a number or a sequence of bytes to every character. Only then can computers store and transmit text. It has nothing to do with encryption: anyone who knows the encoding can read the text.

Why are there so many encodings? Early encodings only covered certain languages. ASCII knew only 128 characters, without umlauts. Later, regional extensions appeared, such as ISO-8859-1, also called Latin-1, and Windows-1252 for Western European languages. Unicode with the encoding UTF-8 finally unites all writing systems and is the standard on the web today.

All TYPO3 websites use UTF-8. This lets you store characters from all languages consistently. It cannot be switched. Problems therefore arise when exchanging data with external files.

UTF-8 stores an umlaut as two bytes. If a program opens a UTF-8 file as Latin-1, it reads those two bytes as two wrong characters. The German ä then becomes a capital A with a tilde, followed by a currency sign. This is called mojibake, or garbled text. The other way round, Latin-1 umlauts often appear in UTF-8 as a replacement character, a question mark in a diamond.

How do you find out the encoding? You cannot tell from the file name or the size. Many text editors show the encoding in the status bar and can change it when saving. On the command line, the command file with the option minus i gives an estimate. Reliable detection is not always possible, because not every file records its encoding.

CSV files: delimiters and enclosures

CSV stands for comma-separated values, more generally character-separated values. A CSV file is a plain text file. Each line is a record, and a delimiter separates the fields. CSV is used to exchange data between systems. You can open and edit it in any text editor or in a spreadsheet such as LibreOffice Calc or Excel.

Common delimiters are the comma, the semicolon and the tab. The comma gives the format its name. In countries where the comma is the decimal separator, such as Germany, spreadsheets often export with a semicolon. Files with tabs are also called TSV. The CSV download in the TYPO3 Records module offers comma, semicolon and the vertical bar, called pipe.

The enclosure is usually a double quote. It wraps values that themselves contain a delimiter, a line break or a quote. Without it, a name like “Müller, Anna” would be read as two fields. If the value itself contains a quote, that quote is doubled. This is the usual escape rule according to RFC 4180. The standard knows no backslashes as escape characters, and no single quotes as enclosure either. The CSV download in the Records module does offer single quotes as an option, but the double quote is the default.

A value with a comma and quotes Value She said "Hello", I replied 1. Contains a comma: whole value in " " 2. Inner " is doubled to "" In the CSV file "She said ""Hello"", I replied" Backslashes and single quotes are not standard.
Enclosure and doubled quotes according to RFC 4180.

Encoding and spreadsheets: Some spreadsheets open a CSV file on double click with a regional default encoding such as Windows-1252. A UTF-8 file from TYPO3 then shows wrong umlauts, although it looks correct in a text editor. The solution: open the file through the import function and choose UTF-8 as encoding. A byte order mark at the start of the file, BOM for short, often helps too, because the program recognises UTF-8 from it.

Key points

  • TYPO3 manages all media in the Media module, formerly Filelist. Files in use cannot be deleted, but they can be moved.
  • Default image formats in TYPO3 14 include JPEG, PNG, GIF, SVG, WebP and AVIF. Photos as JPEG, WebP or AVIF, logos as SVG, transparency as PNG, WebP or SVG.
  • For videos, MP4 and WebM are the standard formats. YouTube and Vimeo come in by URL, but usually need consent.
  • The WCAG by the W3C have four principles and the levels A, AA and AAA. For normal text, AA requires a contrast of 4.5 to 1.
  • You maintain alternative texts in the metadata and override them in the content element when needed. Decorative images get an empty alternative text.
  • Testing means: tool, keyboard and screen reader.
  • The backend has improved a lot, but has barriers and no accessibility statement.
  • TYPO3 always works with UTF-8. Convert external data before the import, and check delimiter and encoding for CSV.

Terms

FAL
The file management of TYPO3, which separates where a file is stored from where it is used.
File reference
The use of a file in a specific place, with its own details such as alternative text or crop.
WCAG
The guidelines for accessible web content by the Web Accessibility Initiative of the W3C.
POUR
The four principles perceivable, operable, understandable and robust.
Landmark
A page region that screen reader users can jump to directly.
Alternative text
An invisible text version of the information in an image.
UTF-8
The Unicode encoding for all writing systems, the standard in TYPO3.
CSV
A text file with one record per line and fields separated by a delimiter.
Enclosure
A character, usually a double quote, that wraps a value containing special characters.

As of: November 15, 2026 (TYPO3 14.3 LTS)

Sources:

  • Tutorial for Editors 14.3, chapters Media, Images, Videos and Accessibility
  • TYPO3 Explained 14.3, chapter File Abstraction Layer
  • Frontend Localization Guide 14.3, chapter Character sets
  • Source code TYPO3 14.3 (typo3/cms-core, typo3/cms-backend), checked for imagefile_ext, mediafile_ext, deleting files in use, YouTube and Vimeo, and the CSV download
  • W3C WAI, Web Content Accessibility Guidelines 2.2
  • news.typo3.com, TYPO3 and its Accessibility in the Backend, changes from version 6 to 14
  • RFC 4180 (CSV)
  • Learning objectives TYPO3 CMS Certified Consultant 14 LTS, area media and accessibility

This study guide was written with AI and checked against the sources.

Certifications & exams

Which exam comes next?

You can already practise for 51 exams, and 16 are up for a vote. See all certifications with their official information, cast your vote or suggest your exam.

See all certifications