Corporate interview film in Dubai the delivery specification set at brief stage
A delivery list for a corporate interview film in Dubai can name a graded master, social cutdowns and a thumbnail, and no caption file anywhere on it. Whether it names one, alongside a transcript and an audio description, belongs in the brief. This article sets out the three files that decide whether the film can sit on a page claiming WCAG Level AA, what the UAE's National Policy for Digital Accessibility asks a private company in each of its two languages, why one of the three depends on how many speakers there are, and why the destination decides the file as much as the film.
The one line to hold onto
The caption file, the transcript and the audio description are a delivery specification, and all three are post-production line items. Captions sit at Level A, so they are inside any Level AA claim already. Audio description is where the levels separate, and W3C publishes a Sufficient Technique that lets a video of only a speaker against an unchanging background be discharged with a static text alternative at both levels. It stops applying the moment several speakers are identified only by an on-screen graphic.
A corporate interview film in Dubai ships against a file specification
Three files are in question, and they are three different work products.
A caption file is a timed text track that plays with the film. WCAG defines captions as a synchronized visual or text alternative for speech and non-speech audio needed to understand the content, which is where captions part company with subtitles. A subtitle file carries dialogue. A caption file carries sound effects, music, speaker identification and location too.
An audio description is narration added to the soundtrack to describe important visual details that cannot be understood from the soundtrack alone. In standard audio description it goes into pauses that already exist in the dialogue.
The third file is a transcript, which the UAE Design System's content guideline asks for alongside closed captions.
All of it engages through one classification. WCAG defines synchronized media as audio or video synchronized with another format for presenting information, and a person speaking to camera is exactly that.
One technical fact puts the audio description in the brief. W3C's technique for delivering an audio description as a timed text track records that the cues have to fit the gaps available in the audio, and that where there is not enough time to synthesize the description inside a cue's interval the user agent may truncate the speech. W3C lists it as Advisory rather than Sufficient. Those gaps are a property of the cut.
Where the line between a brand film and a corporate video matters, brand film production in Dubai draws it.
What the UAE policy actually asks a private company to do
The instrument in question is the National Policy for Digital Accessibility, issue date March 2024, published by the UAE Government as twenty pages in English. The Arabic is a separate nineteen-page file, and the two read differently in the one place that matters.
Article 2, the Policy Objective, reaches the private sector by name, the health sector and e-commerce included. Naming a sector in an objective is not binding it in a scope clause, and the scope clause is next.
Article 3, the Policy Scope, carries two things. The first is a binding list of who the policy applies to, and that list is federal: federal ministries, authorities and institutions; semi-government entities and private companies engaged in digital transactions with a government entity through the Competent Authority; partners, contractors and outsourced staff in those transactions; and service providers building websites and digital services for federal entities. Two of those four limbs reach a private company directly.
The second is the sentence this turns on, and it addresses the company no limb catches. In English: all local Government Entities, Semi-Government Entities, and Private Sector entities should take this document into account, and exert the best efforts in compliance. Three softeners in one sentence, with local government entities sitting beside private companies.
The Arabic changes the reading, and in the direction an English-only reader would not expect. The verb is an obligation construction rather than a should, and the same document renders that construction as must twice elsewhere. A genuine Arabic should was available, is used eight times, and is not used here.
The limit belongs in the same breath. That verb governs two objects: taking the document into account, and exerting the best means of complying with it. So the Arabic obliges a private company to try where the English suggests it try, and trying is the whole of the obligation. Neither language binds anyone to a conformance level.
The government portal's own summary of the scope gives four bullets, and it omits both the sentence about a federal sector regulator liaising with the private companies it licenses and the should-and-best-efforts sentence, so a reader who stops at the landing page never meets the sentence this turns on.
We have established no figure for how many company websites in the UAE currently meet Level AA.
The word the policy never uses, and where the duty comes from instead
Term-search the twenty English pages. Caption, zero. Subtitle, zero. Audio description, zero. Transcript, zero. Multimedia, zero.
That is about this document only. Its annex does reach hearing and vision, through a sign language feature and alternative text for graphics, and two guidelines name video without saying what makes one accessible.
So the duty arrives through the WCAG reference, and that reference is not one rule. WCAG is named in seven provisions, from an example in Article 2 to Article 10's must, which names no version and no level. Annex 1 item 1 is the only place a conformance level attaches to a requirement: all public service sites must comply with Level AA of the WCAG 2.1.
Three things about that sentence. The annex's own introduction calls its contents key guidelines, based on best practices and recommended procedures for government entities. Article 9 pulls it back in by requiring compliance. And public service site, the phrase it attaches to, is defined nowhere in an instrument that defines fourteen other terms.
Criterion 1.2.2, Captions, is Level A. Criterion 1.2.3, Audio Description or Media Alternative, is Level A and can be satisfied by a full text alternative instead of a description. Criterion 1.2.5, Audio Description, is Level AA.
The part that decides it for an interview film is narrower than it looks. W3C publishes a Sufficient Technique, G203, for both 1.2.3 and 1.2.5. It applies to videos of only a speaker in front of an unchanging background, where no important visual details warrant description, and it is discharged by a static text alternative carrying the environment, the credits and the name in the lower third. Its carve-out is explicit. It does not apply where multiple speakers are identified on screen as they speak while their identity is not evident in the audio, and W3C says audio description should be used there.
So the question is about the film rather than the standard. Does it carry visual information its audio does not, and are the speakers introduced in the audio or only in the graphics. We have established no answer to that for any given interview film.
Two consequences hold either way. Level AA conformance requires the Level A criteria too, so a caption file is inside any AA claim. And conformance is claimed for full pages only, so one uncaptioned film stops its page claiming AA.
The policy's body and annex say WCAG 2.1, its footnote cites 2.0, and the Competent Authority's own statement names 2.2 AA. It changes nothing, because the three criteria are identical across all three. Name the version and the level on your delivery list, since the instruments will not.
The two UAE government pages that do name captions
The second government document is more useful to a delivery list. The UAE Design System sits on a gov.ae host, TDRA pointed at it in a press release of 6 May 2024, and TDRA's own service page requires every federal entity to comply with it, naming web development firms among its readers.
Its accessibility guideline carries the instruction the policy never gives. To ensure accessibility to people of determination with hearing impairment, you must always consider the use of subtitles or captions to your video. Then the file specification. The most common format for captions on the web is WebVTT. And: do not embed the subtitle or caption within the production of your video, because a user must always have the choice to turn them off and choose the language.
A second Design System page adds the third item. Its content guideline asks for closed captions and transcripts for audio and visual content, and describes a transcript carrying spoken information, sounds such as a door closing, people's names and their actions. Written that way, a transcript carries the visual information too, and the word closed corroborates the do-not-embed instruction on the first page.
WebVTT prescribes the file's encoding, MIME type, signature and timestamp precision, so a delivered file is checkable on receipt, and it carries speaker identification natively, with an interview as its worked example. It is a W3C Candidate Recommendation Draft that calls itself a work in progress, so name it as the format rather than as a standard in the way WCAG is one.
Neither of those two pages mentions audio description, out of twelve published guideline pages. A company following them to the letter has met 1.2.2 and has not been told 1.2.5 exists. W3C, meanwhile, lists open captions burned into the video track as a Sufficient Technique for 1.2.2, the opposite of the Design System's rule. WCAG describes what satisfies a criterion. The Design System sets a house rule for government sites.
Whether the film exists in two languages belongs to Arabic video production. That article found no UAE-published subtitle standard while looking for a style standard, characters per line and reading speed. What is published here is a format instruction, so both stand.
Where the film is going decides which file you deliver
Two limbs of the do-not-embed instruction, turning the file off and choosing a language, are properties of the page and the player rather than of the film. EN 301 549 makes that split explicit, separating the player's ability to display captions from the content's provision of them. It appears in none of the National Policy, TDRA's Digital Government Enablers Annex or the Design System's accessibility guideline, and is explanatory only.
On a self-hosted page the ask is the web platform's own default. The HTML Living Standard enumerates the kinds of timed text track, three of which matter here: subtitles, captions, and descriptions, the last defined as textual descriptions of the video intended for audio synthesis rather than a recorded stem. So the Level AA item has two possible shapes, a mixed audio track and a text file the player reads aloud.
Each page below is authority about its own product on the date it was read. YouTube lists WebVTT among its advanced caption formats rather than its basic ones, and its audio description product is a recorded audio-only file gated to creators with multi-language audio. Vimeo is the closest match to the UAE instruction of anything tested: it specifies caption formats down to the timecode separator and names the viewer control. LinkedIn's captions page requires an SRT file to be attached before the video is posted, does not name WebVTT, and documents no second language track and no viewer toggle. Recruitment films are the subject of employer branding video.
So the buyer's question is which destination the compliance claim attaches to, and that is answerable in one email at brief stage.
Who the policy reaches, and what Dubai prohibits separately
Watch out
The federal policy's silence on penalties and the Dubai fines schedule belong to different instruments and different conduct. Neither reads across.
The federal policy does contain a must about private companies, and it falls on the regulator rather than the company. Articles 3 and 5 both require a sector's regulatory or supervisory federal government entity to liaise with the private companies it licenses. Its applies-to list is federal throughout, from ministries to the suppliers that build digital services for them.
The word federal is where this stalls for the reader this is written for. We have established no answer to whether a Dubai clinic sits inside that clause. The definitions do not settle it: Private Sector is defined broadly enough to include free zone authorities, and appears nowhere on the applies-to list. We have established no answer to whether a free zone licensee is reached, and none to whether a private company's website can be a public service site within the meaning of the only conformance-level requirement. Put the question to your regulator in writing rather than accepting anybody's reading of it, this one included.
Article 14, Enforcement and Compliance, publishes no penalty, no fine and no sanction. Its mechanism is periodic reporting and a compliance percentage, the Arabic carries no penalty language either, and the document sets no deadline. We have established no penalty for non-compliance, and whether one sits in an instrument not retrieved here is not something this research settled.
Dubai runs a separate track. Dubai Law No. (3) of 2022 concerning the rights of persons with disabilities supersedes Law No. (2) of 2014, and its Article 7 prohibits any person, natural or juridical, from discriminating on the basis of disability, expressly including denying reasonable accommodation. Its executive regulation prices that conduct at AED 10,000, doubling on a repeat inside a year to a ceiling of AED 100,000. The same regulation puts Dubai Digital Authority in charge of setting technical standards for digital channels such as websites and smart applications, and of supervising how far the public and private sectors comply.
That Law never names a website, a caption, a subtitle, a video or a conformance level, and its accessible-formats duty falls on government entities. The supervision duty falls on the Authority, not on a company. We have established no content for the standards it must set, and no answer to whether an uncaptioned corporate film could amount to denial of reasonable accommodation under Article 7. That one is for a Dubai lawyer.

Where the film is going decides which file you deliver, and that is a question for the brief.
What goes in the brief, and where it lands in the budget
Every item below is answerable before a shoot date is held.
Ask whoever owns the website whether the page claims Level AA and which WCAG version it names. Ask separately whether an audio description is in scope, and ask what decides it: does the film carry visual information the audio does not, and are the speakers introduced in the audio or only by an on-screen graphic. Put the three files on the delivery list with a format against each, and name the destination, since it decides the format and whether a second language track and a description slot exist. Tell the editor before picture lock if a description is in scope, because standard audio description sits in the existing gaps in the dialogue, and where those are too short WCAG's route is extended audio description, at Level AAA.
Post-production, meaning edit and grade, is about a third of a job, and all three files are post items, so they belong on the quote as scoped items rather than assumptions. The bands sit in video production cost in Dubai. Our own position is that subtitles, Arabic or accessibility work are included or charged depending on the job, which is why the scope is a brief-stage conversation. We have established no figure for what any of the three adds to a post budget. Name all three on the schedule: the client owns the finished film, raw files come on request, and these are deliverables too.
One procurement line, labelled as the reasoning it is. TDRA publishes an RFP annex whose tables are headed as requirements a bidder's solution shall address, and one Service Design item reads in full that the service shall take into consideration the accessibility standards. It names no conformance level and nothing about a film, so the step to a caption file in a video brief is an inference. We have established no UAE tender or contract requiring one.
The rest sits elsewhere in the Journal: filming inside an office in filming permits in Dubai, and consent and usage in filming people in Dubai and video usage rights and ownership.
Common questions
Does UAE law require our corporate videos to have captions?
Not in those terms, and where you sit in Article 3 changes the answer. Its applies-to list is federal, and two limbs reach a private company: one transacting digitally with a government entity, one building a federal entity's digital services. For a company outside that list, the English says take the document into account and exert the best efforts in compliance, and the Arabic of that sentence obliges exactly that effort. The only place a conformance level attaches to a requirement sits in an annex calling its contents recommended procedures.
Our film is one person talking to camera. Do we need an audio description as well?
It depends on the film, and W3C has published the test. Criterion 1.2.3 is Level A and can be satisfied by a full text alternative instead of a description. Criterion 1.2.5 is Level AA and asks for the description itself. But Sufficient Technique G203 covers a video of only a speaker against an unchanging background, and discharges both with a static text alternative. It stops applying where several speakers are identified only by on-screen text as they speak. So what settles it is where your speakers are introduced.
What is the difference between subtitles and captions here?
WCAG's definition draws it. Captions are a synchronized alternative for speech and non-speech audio, carrying sound effects, music, speaker identification and location. A subtitle file carries dialogue. A two-speaker interview needs speaker identification for that reason, and WebVTT carries it natively.
Can we burn the subtitles into the picture the way we do for social?
The UAE Design System instructs the opposite for a video on a government site. Do not embed the caption in the production, because the user must be able to turn it off and choose a language, and the format it names is WebVTT. The complication is that W3C lists open captions as a Sufficient Technique for the captions criterion, while the Journal's Arabic article records burned-in subtitles as safe from renderer failure.
Does any of this reach a clinic licensed in Dubai?
One of the policy's musts falls on the sector's federal regulator, and we have established no answer to whether a Dubai clinic sits inside that clause. Put it to your regulator in writing. Dubai Law No. (3) of 2022 separately prohibits any person from denying reasonable accommodation, and its executive regulation puts Dubai Digital Authority in charge of digital-channel standards and private-sector supervision. Neither names a caption or a conformance level.
What do a caption file, a transcript and an audio description cost?
We have established no figure for what any of the three adds to a post-production budget. Two things are established. Post-production, meaning edit and grade, is about a third of a job, so all three are post items rather than production ones. And our own line is that subtitles, Arabic or accessibility work are included or charged depending on the job, which makes it a brief-stage conversation rather than a price.
What to hold onto, in one pass
Three files decide whether an interview film can sit on a page claiming Level AA: a caption track, a transcript and an audio description. The UAE's National Policy for Digital Accessibility uses none of those words across twenty English pages, and the duty arrives only through its WCAG reference. Captions are Level A and are inside any AA claim already. Audio description is where the levels separate, and W3C's own technique lets a single speaker against an unchanging background be discharged with a paragraph of text, while taking that route away the moment speakers are named only on screen. For a private company outside Article 3's federal applies-to list the English says should and best efforts, the Arabic obliges the same effort, and neither is a conformance requirement. Dubai separately prohibits denial of reasonable accommodation and names no caption. And the destination decides the file as much as the film does, which is why all of it belongs in the brief.
Grolez Films: the specification goes in the brief
Three questions belong in the brief. Which version and level the page claims, whether an audio description is in scope, and where the film is going. Subtitles, Arabic or accessibility work are included or charged depending on the job, which is why they are worth settling at brief stage.
Luis Grolez, the founder, pitches this personally.
See the work. Then get in touch about a specific film and the page it has to live on.
Sources and methodology
Everything regulatory here was read from primary text rather than from commentary, across two research passes on 22 and 28 August 2026. The policy was retrieved as a twenty-page English PDF and a separate nineteen-page Arabic one from the UAE Government's own asset host, both read end to end and then term-searched over extracted text, with coordinate-aware extraction used to settle which article each sentence sits in. The Arabic path published in the research brief did not exist and the real one is a segment shorter, which is the kind of failure that gets written up as an unpublished document. Rung four is unavailable on the government portal, where robots.txt, sitemap.xml and the capital-S variant all return 404, so the policy pages were reached by link, and the Design System's own outbound link to the policy is itself broken. Every Arabic term count was taken over normalised text, and every Arabic zero was recorded only alongside a control count for a word that must be present, because a naive search returned zero for a word used 112 times in one document. Character totals for the PDFs and for the Design System pages do not reproduce across extractors, so no character total is claimed anywhere; term counts do reproduce and are printed. WCAG 2.0, 2.1 and 2.2 were all read at w3.org, the second and third of them only to establish that the criteria in play are identical across them. Five W3C techniques and understanding documents were read, and Technique G203 narrowed a sentence an earlier pass of this research had called its most useful. The UAE Design System was read on two pages rather than one, and any negative about it is scoped to a named page or to its twelve-page guidelines index. The Dubai Legal Portal was searched on both its English and Arabic sides, which are not the same corpus, and Dubai Law No. (3) of 2022 and its executive regulation were retrieved in full from the Government of Dubai's own portal, with a copy on another host recorded as corroboration rather than as provenance. An earlier statement that no emirate-level requirement had been established has been withdrawn in every form, and that is the second Dubai negative this research has had to withdraw. A federal legislation host is unreachable from this environment at every rung including a full browser render, so no federal statute was read there. No accessibility-vendor page, law-firm commentary or consultancy page is cited anywhere, and several were set aside, including one that states the private-sector duty more strongly than either language of the policy supports. The questions left open in both directions are the classification of an emirate-licensed company, whether a free zone licensee is reached, whether a private site can be a public service site, whether an uncaptioned film could amount to denial of reasonable accommodation, and what the Dubai Digital Authority standards require. No figure exists here for what a caption file, a transcript or an audio description adds to a post budget, and none is given. The European standard cited for the player-versus-content split appears in none of the National Policy, TDRA's Digital Government Enablers Annex or the Design System's accessibility guideline, and is explanatory only. The platform behaviour described is what each platform's own help page documented on the retrieval date. No claim is made that Grolez Films has delivered a WCAG-conformant film, worked to a conformance level, or has accessibility experience of any kind. The two lines describing our own work are confirmed internally, on 16 and 22 August 2026. This article is informational and is not legal advice. Confirm your position with the relevant authority or with counsel before relying on it. Prepared 28 August 2026.
- UAE Government portal, National Policy for Digital Accessibility, issue date March 2024, English and Arabic, for the policy's scope, its WCAG references, its annex and its enforcement mechanism: u.ae
- W3C, Web Content Accessibility Guidelines 2.1, for success criteria 1.2.2, 1.2.3, 1.2.5 and 1.2.7, the conformance requirements and the glossary definitions: w3.org
- W3C, Web Content Accessibility Guidelines 2.2, for the identical numbering, wording and levels of the time-based media criteria: w3.org
- W3C, Technique G203, for the static text alternative for a talking head video and its carve-out: w3.org
- W3C, Technique G93, for open captions burned into the video track as a Sufficient Technique for the captions criterion: w3.org
- W3C, Technique H96, for the description track's advisory status and its gap constraint: w3.org
- W3C, WebVTT, for the format, its prescribed structure and its status as a Candidate Recommendation Draft: w3.org
- WHATWG, HTML Living Standard, for the track element and the three kinds of timed text track: html.spec.whatwg.org
- UAE Design System, accessibility guideline, for the caption instruction, WebVTT and the do-not-embed rule: designsystem.gov.ae
- UAE Design System, content guideline, for the transcript instruction with names and actions: designsystem.gov.ae
- TDRA, Digital Government service page for the UAE Design System, for the compliance duty on federal entities and for web development firms named among its readers: dgov.tdra.gov.ae
- TDRA, press release of 6 May 2024, for the Competent Authority describing the AA duty as guidance and pointing at the Design System: tdra.gov.ae
- TDRA, Digital Government Enablers Annex, version 3, January 2025, for the bidder-facing accessibility requirement: dgov.tdra.gov.ae
- Dubai Legal Portal, Law No. (3) of 2022 concerning the rights of persons with disabilities, and Executive Council Resolution No. (1) of 2022 issuing its executive regulation, for the prohibition, the fines schedule and the digital-channel supervision limb. The portal serves instruments through a viewer with no addressable URL of its own, so the entry point is its legislation search: dlp.dubai.gov.ae
- ETSI, EN 301 549 V3.2.1, cited as an explanatory source for the player-versus-content split, never as a UAE obligation: etsi.org
- YouTube help, for its caption format tiers: support.google.com
- YouTube help, for its audio description product: support.google.com
- Vimeo help, for its caption file specifications, its viewer control and its audio description track type: help.vimeo.com
- LinkedIn help, for the SRT requirement on its captions page: linkedin.com