Ap Image to PDF Convert 3.4 serial key or number

1. Introduction

This document enumerates the requirements that must be met in order for devices to be compatible with Android 11.

The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard defined in RFC2119.

As used in this document, a “device implementer” or “implementer” is a person or organization developing a hardware/software solution running Android 11. A “device implementation” or “implementation" is the hardware/software solution so developed.

To be considered compatible with Android 11, device implementations MUST meet the requirements presented in this Compatibility Definition, including any documents incorporated via reference.

Where this definition or the software tests described in section 10 is silent, ambiguous, or incomplete, it is the responsibility of the device implementer to ensure compatibility with existing implementations.

For this reason, the Android Open Source Project is both the reference and preferred implementation of Android. Device implementers are STRONGLY RECOMMENDED to base their implementations to the greatest extent possible on the “upstream” source code available from the Android Open Source Project. While some components can hypothetically be replaced with alternate implementations, it is STRONGLY RECOMMENDED to not follow this practice, as passing the software tests will become substantially more difficult. It is the implementer’s responsibility to ensure full behavioral compatibility with the standard Android implementation, including and beyond the Compatibility Test Suite. Finally, note that certain component substitutions and modifications are explicitly forbidden by this document.

Many of the resources linked to in this document are derived directly or indirectly from the Android SDK and will be functionally identical to the information in that SDK’s documentation. In any cases where this Compatibility Definition or the Compatibility Test Suite disagrees with the SDK documentation, the SDK documentation is considered authoritative. Any technical details provided in the linked resources throughout this document are considered by inclusion to be part of this Compatibility Definition.

1.1 Document Structure

1.1.1. Requirements by Device Type

Section 2 contains all of the requirements that apply to a specific device type. Each subsection of Section 2 is dedicated to a specific device type.

All the other requirements, that universally apply to any Android device implementations, are listed in the sections after Section 2. These requirements are referenced as "Core Requirements" in this document.

1.1.2. Requirement ID

Requirement ID is assigned for MUST requirements.

• The ID is assigned for MUST requirements only.
• STRONGLY RECOMMENDED requirements are marked as [SR] but ID is not assigned.
• The ID consists of : Device Type ID - Condition ID - Requirement ID (e.g. C-0-1).

Each ID is defined as below:

• Device Type ID (see more in 2. Device Types)
  • C: Core (Requirements that are applied to any Android device implementations)
  • H: Android Handheld device
  • T: Android Television device
  • A: Android Automotive implementation
  • W: Android Watch implementation
  • Tab: Android Tablet implementation
• Condition ID
  • When the requirement is unconditional, this ID is set as 0.
  • When the requirement is conditional, 1 is assigned for the 1st condition and the number increments by 1 within the same section and the same device type.
• Requirement ID
  • This ID starts from 1 and increments by 1 within the same section and the same condition.

1.1.3. Requirement ID in Section 2

The Requirement ID in Section 2 starts with the corresponding section ID that is followed by the Requirement ID described above.

• The ID in Section 2 consists of : Section ID / Device Type ID - Condition ID - Requirement ID (e.g. 7.4.3/A-0-1).

2. Device Types

While the Android Open Source Project provides a software stack that can be used for a variety of device types and form factors, there are a few device types that have a relatively better established application distribution ecosystem.

This section describes those device types, and additional requirements and recommendations applicable for each device type.

All Android device implementations that do not fit into any of the described device types MUST still meet all requirements in the other sections of this Compatibility Definition.

2.1 Device Configurations

For the major differences in hardware configuration by device type, see the device-specific requirements that follow in this section.

2.2. Handheld Requirements

An Android Handheld device refers to an Android device implementation that is typically used by holding it in the hand, such as an mp3 player, phone, or tablet.

Android device implementations are classified as a Handheld if they meet all the following criteria:

• Have a power source that provides mobility, such as a battery.
• Have a physical diagonal screen size in the range of 3.3 inches (or 2.5 inches for devices which launched on an API level earlier than Android 11) to 8 inches.

The additional requirements in the rest of this section are specific to Android Handheld device implementations.

2.2.1. Hardware

Handheld device implementations:

• [7.1.1.1/H-0-1] MUST have at least one Android-compatible display that meets all requirements described on this document.
• [7.1.1.3/H-SR] Are STRONGLY RECOMMENDED to provide users an affordance to change the display size (screen density).

If Handheld device implementations support software screen rotation, they:

• [7.1.1.1/H-1-1]* MUST make the logical screen that is made available for third party applications be at least 2 inches on the short edge(s) and 2.7 inches on the long edge(s). Devices which launched on an API level earlier than that of this document are exempted from this requirement.

If Handheld device implementations do not support software screen rotation, they:

• [7.1.1.1/H-2-1]* MUST make the logical screen that is made available for third party applications be at least 2.7 inches on the short edge(s). Devices which launched on an API level earlier than that of this document are exempted from this requirement.

If Handheld device implementations claim support for high dynamic range displays through , they:

• [7.1.4.5/H-1-1] MUST advertise support for the , , , , and extensions.

Handheld device implementations:

• [7.1.4.6/H-0-1] MUST report whether the device supports the GPU profiling capability via a system property .

If Handheld device implementations declare support via a system property , they:

Handheld device implementations:

• [7.1.5/H-0-1] MUST include support for legacy application compatibility mode as implemented by the upstream Android open source code. That is, device implementations MUST NOT alter the triggers or thresholds at which compatibility mode is activated, and MUST NOT alter the behavior of the compatibility mode itself.
• [7.2.1/H-0-1] MUST include support for third-party Input Method Editor (IME) applications.
• [7.2.3/H-0-3] MUST provide the Home function on all the Android-compatible displays that provide the home screen.
• [7.2.3/H-0-4] MUST provide the Back function on all the Android-compatible displays and the Recents function on at least one of the Android-compatible displays.
• [7.2.3/H-0-2] MUST send both the normal and long press event of the Back function () to the foreground application. These events MUST NOT be consumed by the system and CAN be triggered by outside of the Android device (e.g. external hardware keyboard connected to the Android device).
• [7.2.4/H-0-1] MUST support touchscreen input.
• [7.2.4/H-SR] Are STRONGLY RECOMMENDED to launch the user-selected assist app, in other words the app that implements VoiceInteractionService, or an activity handling the on long-press of or if the foreground activity does not handle those long-press events.
• [7.3.1/H-SR] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer.

If Handheld device implementations include a 3-axis accelerometer, they:

• [7.3.1/H-1-1] MUST be able to report events up to a frequency of at least 100 Hz.

If Handheld device implementations include a GPS/GNSS receiver and report the capability to applications through the feature flag, they:

• [7.3.3/H-2-1] MUST report GNSS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported.
• [7.3.3/H-2-2] MUST report GNSS pseudoranges and pseudorange rates, that, in open-sky conditions after determining the location, while stationary or moving with less than 0.2 meter per second squared of acceleration, are sufficient to calculate position within 20 meters, and speed within 0.2 meters per second, at least 95% of the time.

If Handheld device implementations include a 3-axis gyroscope, they:

• [7.3.4/H-3-1] MUST be able to report events up to a frequency of at least 100 Hz.
• [7.3.4/H-3-2] MUST be capable of measuring orientation changes up to 1000 degrees per second.

Handheld device implementations that can make a voice call and indicate any value other than in :

• [7.3.8/H] SHOULD include a proximity sensor.

Handheld device implementations:

• [7.3.11/H-SR] Are RECOMMENDED to support pose sensor with 6 degrees of freedom.
• [7.4.3/H] SHOULD include support for Bluetooth and Bluetooth LE.

If Handheld device implementations include a metered connection, they:

• [7.4.7/H-1-1] MUST provide the data saver mode.

If Handheld device implementations include a logical camera device that lists capabilities using , they:

• [7.5.4/H-1-1] MUST have normal field of view (FOV) by default and it MUST be between 50 and 90 degrees.

Handheld device implementations:

• [7.6.1/H-0-1] MUST have at least 4 GB of non-volatile storage available for application private data (a.k.a. "/data" partition).
• [7.6.1/H-0-2] MUST return “true” for when there is less than 1GB of memory available to the kernel and userspace.

If Handheld device implementations declare support of only a 32-bit ABI:

• [7.6.1/H-1-1] The memory available to the kernel and userspace MUST be at least 416MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA).

• [7.6.1/H-2-1] The memory available to the kernel and userspace MUST be at least 592MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA).

• [7.6.1/H-3-1] The memory available to the kernel and userspace MUST be at least 896MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+).

• [7.6.1/H-4-1] The memory available to the kernel and userspace MUST be at least 1344MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA).

If Handheld device implementations declare support of 32-bit and 64-bit ABIs:

• [7.6.1/H-5-1] The memory available to the kernel and userspace MUST be at least 816MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA).

• [7.6.1/H-6-1] The memory available to the kernel and userspace MUST be at least 944MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA).

• [7.6.1/H-7-1] The memory available to the kernel and userspace MUST be at least 1280MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+).

• [7.6.1/H-8-1] The memory available to the kernel and userspace MUST be at least 1824MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA).

Note that the "memory available to the kernel and userspace" above refers to the memory space provided in addition to any memory already dedicated to hardware components such as radio, video, and so on that are not under the kernel’s control on device implementations.

If Handheld device implementations include less than or equal to 1GB of memory available to the kernel and userspace, they:

• [7.6.1/H-9-1] MUST declare the feature flag .
• [7.6.1/H-9-2] MUST have at least 1.1 GB of non-volatile storage for application private data (a.k.a. "/data" partition).

If Handheld device implementations include more than 1GB of memory available to the kernel and userspace, they:

• [7.6.1/H-10-1] MUST have at least 4GB of non-volatile storage available for application private data (a.k.a. "/data" partition).
• SHOULD declare the feature flag .

Handheld device implementations:

• [7.6.2/H-0-1] MUST NOT provide an application shared storage smaller than 1 GiB.
• [7.7.1/H] SHOULD include a USB port supporting peripheral mode.

If handheld device implementations include a USB port supporting peripheral mode, they:

• [7.7.1/H-1-1] MUST implement the Android Open Accessory (AOA) API.

If Handheld device implementations include a USB port supporting host mode, they:

• [7.7.2/H-1-1] MUST implement the USB audio class as documented in the Android SDK documentation.

Handheld device implementations:

• [7.8.1/H-0-1] MUST include a microphone.
• [7.8.2/H-0-1] MUST have an audio output and declare .

If Handheld device implementations are capable of meeting all the performance requirements for supporting VR mode and include support for it, they:

• [7.9.1/H-1-1] MUST declare the feature flag.
• [7.9.1/H-1-2] MUST include an application implementing that can be enabled by VR applications via .

If Handheld device implementations include one or more USB-C port(s) in host mode and implement (USB audio class), in addition to requirements in section 7.7.2, they:

• [7.8.2.2/H-1-1] MUST provide the following software mapping of HID codes:

• [7.8.2.2/H-1-2] MUST trigger ACTION_HEADSET_PLUG upon a plug insert, but only after the USB audio interfaces and endpoints have been properly enumerated in order to identify the type of terminal connected.

When the USB audio terminal types 0x0302 is detected, they:

• [7.8.2.2/H-2-1] MUST broadcast Intent ACTION_HEADSET_PLUG with "microphone" extra set to 0.

When the USB audio terminal types 0x0402 is detected, they:

• [7.8.2.2/H-3-1] MUST broadcast Intent ACTION_HEADSET_PLUG with "microphone" extra set to 1.

When API AudioManager.getDevices() is called while the USB peripheral is connected they:

• [7.8.2.2/H-4-1] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0302.

• [7.8.2.2/H-4-2] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0402.

• [7.8.2.2/H-4-3] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSource() if the USB audio terminal type field is 0x0402.

• [7.8.2.2/H-4-4] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSink() if the USB audio terminal type field is 0x603.

• [7.8.2.2/H-4-5] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSource() if the USB audio terminal type field is 0x604.

• [7.8.2.2/H-4-6] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSink() if the USB audio terminal type field is 0x400.

• [7.8.2.2/H-4-7] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSource() if the USB audio terminal type field is 0x400.

• [7.8.2.2/H-SR] Are STRONGLY RECOMMENDED upon connection of a USB-C audio peripheral, to perform enumeration of USB descriptors, identify terminal types and broadcast Intent ACTION_HEADSET_PLUG in less than 1000 milliseconds.

If Handheld device implementations include at least one haptic actuator, they:

• [7.10/H-SR]* Are STRONGLY RECOMMENDED NOT to use an eccentric rotating mass (ERM) haptic actuator(vibrator).
• [7.10/H]* SHOULD position the placement of the actuator near the location where the device is typically held or touched by hands.
• [7.10/H-SR]* Are STRONGLY RECOMMENDED to implement all public constants for clear haptics in android.view.HapticFeedbackConstants namely (CLOCK_TICK, CONTEXT_CLICK, KEYBOARD_PRESS, KEYBOARD_RELEASE, KEYBOARD_TAP, LONG_PRESS, TEXT_HANDLE_MOVE, VIRTUAL_KEY, VIRTUAL_KEY_RELEASE, CONFIRM, REJECT, GESTURE_START and GESTURE_END).
• [7.10/H-SR]* Are STRONGLY RECOMMENDED to implement all public constants for clear haptics in android.os.VibrationEffect namely (EFFECT_TICK, EFFECT_CLICK, EFFECT_HEAVY_CLICK and EFFECT_DOUBLE_CLICK) and all public constants for rich haptics in android.os.VibrationEffect.Composition namely (PRIMITIVE_CLICK and PRIMITIVE_TICK).
• [7.10/H-SR]* Are STRONGLY RECOMMENDED to use these linked haptic constants mappings.
• [7.10/H-SR]* Are STRONGLY RECOMMENDED to follow quality assessment for createOneShot() and createWaveform() API's.
• [7.10/H-SR]* Are STRONGLY RECOMMENDED to verify the capabilities for amplitude scalability by running android.os.Vibrator.hasAmplitudeControl().

Linear resonant actuator (LRA) is a single mass spring system which has a dominant resonant frequency where the mass translates in the direction of desired motion.

If Handheld device implementations include at least one linear resonant actuator, they:

• [7.10/H]* SHOULD move the haptic actuator in the X-axis of portrait orientation.

If Handheld device implementations have a haptic actuator which is X-axis Linear resonant actuator (LRA), they:

• [7.10/H-SR]* Are STRONGLY RECOMMENDED to have the resonant frequency of the X-axis LRA be under 200 Hz.

If handheld device implementations follow haptic constants mapping, they:

2.2.2. Multimedia

Handheld device implementations MUST support the following audio encoding and decoding formats and make them available to third-party applications:

• [5.1/H-0-1] AMR-NB
• [5.1/H-0-2] AMR-WB
• [5.1/H-0-3] MPEG-4 AAC Profile (AAC LC)
• [5.1/H-0-4] MPEG-4 HE AAC Profile (AAC+)
• [5.1/H-0-5] AAC ELD (enhanced low delay AAC)

Handheld device implementations MUST support the following video encoding formats and make them available to third-party applications:

• [5.2/H-0-1] H.264 AVC
• [5.2/H-0-2] VP8

Handheld device implementations MUST support the following video decoding formats and make them available to third-party applications:

• [5.3/H-0-1] H.264 AVC
• [5.3/H-0-2] H.265 HEVC
• [5.3/H-0-3] MPEG-4 SP
• [5.3/H-0-4] VP8
• [5.3/H-0-5] VP9

2.2.3. Software

Handheld device implementations:

• [3.2.3.1/H-0-1] MUST have an application that handles the , , , and intents as described in the SDK documents, and provide the user affordance to access the document provider data by using API.
• [3.2.3.1/H-0-2]* MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here.
• [3.2.3.1/H-SR] Are STRONGLY RECOMMENDED to preload an email application which can handle ACTION_SENDTO or ACTION_SEND or ACTION_SEND_MULTIPLE intents to send an email.
• [3.4.1/H-0-1] MUST provide a complete implementation of the API.
• [3.4.2/H-0-1] MUST include a standalone Browser application for general user web browsing.
• [3.8.1/H-SR] Are STRONGLY RECOMMENDED to implement a default launcher that supports in-app pinning of shortcuts, widgets and widgetFeatures.
• [3.8.1/H-SR] Are STRONGLY RECOMMENDED to implement a default launcher that provides quick access to the additional shortcuts provided by third-party apps through the ShortcutManager API.
• [3.8.1/H-SR] Are STRONGLY RECOMMENDED to include a default launcher app that shows badges for the app icons.
• [3.8.2/H-SR] Are STRONGLY RECOMMENDED to support third-party app widgets.
• [3.8.3/H-0-1] MUST allow third-party apps to notify users of notable events through the and API classes.
• [3.8.3/H-0-2] MUST support rich notifications.
• [3.8.3/H-0-3] MUST support heads-up notifications.
• [3.8.3/H-0-4] MUST include a notification shade, providing the user the ability to directly control (e.g. reply, snooze, dismiss, block) the notifications through user affordance such as action buttons or the control panel as implemented in the AOSP.
• [3.8.3/H-0-5] MUST display the choices provided through in the notification shade.
• [3.8.3/H-SR] Are STRONGLY RECOMMENDED to display the first choice provided through in the notification shade without additional user interaction.
• [3.8.3/H-SR] Are STRONGLY RECOMMENDED to display all the choices provided through in the notification shade when the user expands all notifications in the notification shade.
• [3.8.3.1/H-SR] Are STRONGLY RECOMMENDED to display actions for which is set as in-line with the replies displayed by .
• [3.8.4/H-SR] Are STRONGLY RECOMMENDED to implement an assistant on the device to handle the Assist action.

If Handheld device implementations support Assist action, they:

• [3.8.4/H-SR] Are STRONGLY RECOMMENDED to use long press on key as the designated interaction to launch the assist app as described in section 7.2.3. MUST launch the user-selected assist app, in other words the app that implements , or an activity handling the intent.

If Handheld device implementations support and group them into a separate section from alerting and silent non-conversation notifications, they:

• [3.8.4/H-1-1]* MUST display conversation notifications ahead of non conversation notifications with the exception of ongoing foreground service notifications and importance:high notifications.

If Android Handheld device implementations support a lock screen, they:

• [3.8.10/H-1-1] MUST display the Lock screen Notifications including the Media Notification Template.

If Handheld device implementations support a secure lock screen, they:

• [3.9/H-1-1] MUST implement the full range of device administration policies defined in the Android SDK documentation.
• [3.9/H-1-2] MUST declare the support of managed profiles via the feature flag, except when the device is configured so that it would report itself as a low RAM device or so that it allocates internal (non-removable) storage as shared storage.

If Handheld device implementations include support for and APIs and allow third-party applications to publish , then they:

• [3.8.16/H-1-1] MUST declare the feature flag and set it to .
• [3.8.16/H-1-2] MUST provide a user affordance with the ability to add, edit, select, and operate the user’s favorite device controls from the controls registered by the third-party applications through the and the APIs.
• [3.8.16/H-1-3] MUST provide access to this user affordance within three interactions from a default Launcher.
• [3.8.16/H-1-4] MUST accurately render in this user affordance the name and icon of each third-party app that provides controls via the API as well as any specified fields provided by the APIs.

Conversely, If Handheld device implementations do not implement such controls, they:

Handheld device implementations:

• [3.10/H-0-1] MUST support third-party accessibility services.
• [3.10/H-SR] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preinstalled Text-to-speech engine) accessibility services as provided in the talkback open source project.
• [3.11/H-0-1] MUST support installation of third-party TTS engines.
• [3.11/H-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
• [3.13/H-SR] Are STRONGLY RECOMMENDED to include a Quick Settings UI component.

If Android handheld device implementations declare or support, they:

• [3.16/H-1-1] MUST support the companion device pairing feature.

If the navigation function is provided as an on-screen, gesture-based action:

• [7.2.3/H] The gesture recognition zone for the Home function SHOULD be no higher than 32 dp in height from the bottom of the screen.

If Handheld device implementations provide a navigation function as a gesture from anywhere on the left and right edges of the screen:

• [7.2.3/H-0-1] The navigation function's gesture area MUST be less than 40 dp in width on each side. The gesture area SHOULD be 24 dp in width by default.

2.2.4. Performance and Power

• [8.1/H-0-1] Consistent frame latency. Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second.
• [8.1/H-0-2] User interface latency. Device implementations MUST ensure low latency user experience by scrolling a list of 10K list entries as defined by the Android Compatibility Test Suite (CTS) in less than 36 secs.
• [8.1/H-0-3] Task switching. When multiple applications have been launched, re-launching an already-running application after it has been launched MUST take less than 1 second.

Handheld device implementations:

• [8.2/H-0-1] MUST ensure a sequential write performance of at least 5 MB/s.
• [8.2/H-0-2] MUST ensure a random write performance of at least 0.5 MB/s.
• [8.2/H-0-3] MUST ensure a sequential read performance of at least 15 MB/s.
• [8.2/H-0-4] MUST ensure a random read performance of at least 3.5 MB/s.

If Handheld device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

• [8.3/H-1-1] MUST provide user affordance to enable and disable the battery saver feature.
• [8.3/H-1-2] MUST provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.

Handheld device implementations:

• [8.4/H-0-1] MUST provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
• [8.4/H-0-2] MUST report all power consumption values in milliampere hours (mAh).
• [8.4/H-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the kernel module implementation.
• [8.4/H-0-4] MUST make this power usage available via the shell command to the app developer.
• [8.4/H] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.

If Handheld device implementations include a screen or video output, they:

2.2.5. Security Model

Handheld device implementations:

• [9.1/H-0-1] MUST allow third-party apps to access the usage statistics via the permission and provide a user-accessible mechanism to grant or revoke access to such apps in response to the intent.

Handheld device implementations (* Not applicable for Tablet):

• [9.11/H-0-2]* MUST back up the keystore implementation with an isolated execution environment.
• [9.11/H-0-3]* MUST have implementations of RSA, AES, ECDSA, and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
• [9.11/H-0-4]* MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
• [9.11/H-0-5]* MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.

Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a keystore backed by an isolated execution environment and support the key attestation, unless it declares the feature which requires a keystore backed by an isolated execution environment.

When Handheld device implementations support a secure lock screen, they:

• [9.11/H-1-1] MUST allow the user to choose the shortest sleep timeout, that is a transition time from the unlocked to the locked state, as 15 seconds or less.
• [9.11/H-1-2] MUST provide user affordance to hide notifications and disable all forms of authentication except for the primary authentication described in 9.11.1 Secure Lock Screen. The AOSP meets the requirement as lockdown mode.

2.2.6. Developer Tools and Options Compatibility

Handheld device implementations (* Not applicable for Tablet):

• [6.1/H-0-1]* MUST support the shell command .

Handheld device implementations (* Not applicable for Tablet):

• Perfetto
  • [6.1/H-0-2]* MUST expose a binary to the shell user which cmdline complies with the perfetto documentation.
  • [6.1/H-0-3]* The perfetto binary MUST accept as input a protobuf config that complies with the schema defined in the perfetto documentation.
  • [6.1/H-0-4]* The perfetto binary MUST write as output a protobuf trace that complies with the schema defined in the perfetto documentation.
  • [6.1/H-0-5]* MUST provide, through the perfetto binary, at least the data sources described in the perfetto documentation.
  • [6.1/H-0-6]* The perfetto traced daemon MUST be enabled by default (system property ).

2.3. Television Requirements

An Android Television device refers to an Android device implementation that is an entertainment interface for consuming digital media, movies, games, apps, and/or live TV for users sitting about ten feet away (a “lean back” or “10-foot user interface”).

Android device implementations are classified as a Television if they meet all the following criteria:

• Have provided a mechanism to remotely control the rendered user interface on the display that might sit ten feet away from the user.
• Have an embedded screen display with the diagonal length larger than 24 inches OR include a video output port, such as VGA, HDMI, DisplayPort, or a wireless port for display.

The additional requirements in the rest of this section are specific to Android Television device implementations.

2.3.1. Hardware

Television device implementations:

• [7.2.2/T-0-1] MUST support D-pad.
• [7.2.3/T-0-1] MUST provide the Home and Back functions.
• [7.2.3/T-0-2] MUST send both the normal and long press event of the Back function () to the foreground application.
• [7.2.6.1/T-0-1] MUST include support for game controllers and declare the feature flag.
• [7.2.7/T] SHOULD provide a remote control from which users can access non-touch navigation and core navigation keys inputs.

If Television device implementations include a 3-axis gyroscope, they:

• [7.3.4/T-1-1] MUST be able to report events up to a frequency of at least 100 Hz.
• [7.3.4/T-1-2] MUST be capable of measuring orientation changes up to 1000 degrees per second.

Television device implementations:

• [7.4.3/T-0-1] MUST support Bluetooth and Bluetooth LE.
• [7.6.1/T-0-1] MUST have at least 4 GB of non-volatile storage available for application private data (a.k.a. "/data" partition).

If Television device implementations include a USB port that supports host mode, they:

• [7.5.3/T-1-1] MUST include support for an external camera that connects through this USB port but is not necessarily always connected.

If TV device implementations are 32-bit:

• [7.6.1/T-1-1] The memory available to the kernel and userspace MUST be at least 896MB if any of the following densities are used:

  • 400dpi or higher on small/normal screens
  • xhdpi or higher on large screens
  • tvdpi or higher on extra large screens

If TV device implementations are 64-bit:

• [7.6.1/T-2-1] The memory available to the kernel and userspace MUST be at least 1280MB if any of the following densities are used:

  • 400dpi or higher on small/normal screens
  • xhdpi or higher on large screens
  • tvdpi or higher on extra large screens

Note that the "memory available to the kernel and userspace" above refers to the memory space provided in addition to any memory already dedicated to hardware components such as radio, video, and so on that are not under the kernel’s control on device implementations.

Television device implementations:

• [7.8.1/T] SHOULD include a microphone.
• [7.8.2/T-0-1] MUST have an audio output and declare .

2.3.2. Multimedia

Television device implementations MUST support the following audio encoding and decoding formats and make them available to third-party applications:

• [5.1/T-0-1] MPEG-4 AAC Profile (AAC LC)
• [5.1/T-0-2] MPEG-4 HE AAC Profile (AAC+)
• [5.1/T-0-3] AAC ELD (enhanced low delay AAC)

Television device implementations MUST support the following video encoding formats and make them available to third-party applications:

• [5.2/T-0-1] H.264
• [5.2/T-0-2] VP8

Television device implementations:

• [5.2.2/T-SR] Are STRONGLY RECOMMENDED to support H.264 encoding of 720p and 1080p resolution videos at 30 frames per second.

Television device implementations MUST support the following video decoding formats and make them available to third-party applications:

Television device implementations MUST support MPEG-2 decoding, as detailed in Section 5.3.1, at standard video frame rates and resolutions up to and including:

• [5.3.1/T-1-1] HD 1080p at 59.94 frames per second with Main Profile High Level.
• [5.3.1/T-1-2] HD 1080i at 59.94 frames per second with Main Profile High Level. They MUST deinterlace interlaced MPEG-2 video to its progressive equivalent (e.g. from 1080i at 59.94 frames per second to 1080p at 29.97 frames per second) and make it available to third-party applications.

Television device implementations MUST support H.264 decoding, as detailed in Section 5.3.4, at standard video frame rates and resolutions up to and including:

• [5.3.4/T-1-1] HD 1080p at 60 frames per second with Baseline Profile
• [5.3.4/T-1-2] HD 1080p at 60 frames per second with Main Profile
• [5.3.4/T-1-3] HD 1080p at 60 frames per second with High Profile Level 4.2

Television device implementations with H.265 hardware decoders MUST support H.265 decoding, as detailed in Section 5.3.5, at standard video frame rates and resolutions up to and including:

• [5.3.5/T-1-1] HD 1080p at 60 frames per second with Main Profile Level 4.1

If Television device implementations with H.265 hardware decoders support H.265 decoding and the UHD decoding profile, they:

• [5.3.5/T-2-1] MUST support UHD 3480p at 60 frames per second with Main10 Level 5 Main Tier profile

Television device implementations MUST support VP8 decoding, as detailed in Section 5.3.6, at standard video frame rates and resolutions up to and including:

• [5.3.6/T-1-1] HD 1080p at 60 frames per second decoding profile

Television device implementations with VP9 hardware decoders MUST support VP9 decoding, as detailed in Section 5.3.7, at standard video frame rates and resolutions up to and including:

• [5.3.7/T-1-1] HD 1080p at 60 frames per second with profile 0 (8 bit color depth)

If Television device implementations with VP9 hardware decoders support VP9 decoding and the UHD decoding profile, they:

• [5.3.7/T-2-1] MUST support UHD 3480p at 60 frames per second with profile 0 (8 bit color depth).
• [5.3.7/T-2-1] Are STRONGLY RECOMMENDED to support UHD 3480p at 60 frames per second with profile 2 (10 bit color depth).

Television device implementations:

• [5.5/T-0-1] MUST include support for system Master Volume and digital audio output volume attenuation on supported outputs, except for compressed audio passthrough output (where no audio decoding is done on the device).

If Television device implementations do not have a built in display, but instead support an external display connected via HDMI, they:

• [5.8/T-0-1] MUST set the HDMI output mode to select the maximum resolution that can be supported with either a 50Hz or 60Hz refresh rate.
• [5.8/T-SR] Are STRONGLY RECOMMENDED to provide a user configurable HDMI refresh rate selector.
• [5.8] SHOULD set the HDMI output mode refresh rate to either 50Hz or 60Hz, depending on the video refresh rate for the region the device is sold in.

If Television device implementations do not have a built in display, but instead support an external display connected via HDMI, they:

• [5.8/T-1-1] MUST support HDCP 2.2.

If Television device implementations do not support UHD decoding, but instead support an external display connected via HDMI, they:

• [5.8/T-2-1] MUST support HDCP 1.4

2.3.3. Software

Television device implementations:

• [3/T-0-1] MUST declare the features and .
• [3.2.3.1/T-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here.
• [3.4.1/T-0-1] MUST provide a complete implementation of the API.

If Android Television device implementations support a lock screen,they:

• [3.8.10/T-1-1] MUST display the Lock screen Notifications including the Media Notification Template.

Television device implementations:

• [3.8.14/T-SR] Are STRONGLY RECOMMENDED to support picture-in-picture (PIP) mode multi-window.
• [3.10/T-0-1] MUST support third-party accessibility services.
• [3.10/T-SR] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preinstalled Text-to-speech engine) accessibility services as provided in the talkback open source project.

If Television device implementations report the feature , they:

• [3.11/T-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
• [3.11/T-1-1] MUST support installation of third-party TTS engines.

Television device implementations:

• [3.12/T-0-1] MUST support TV Input Framework.

2.3.4. Performance and Power

• [8.1/T-0-1] Consistent frame latency. Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second.
• [8.2/T-0-1] MUST ensure a sequential write performance of at least 5MB/s.
• [8.2/T-0-2] MUST ensure a random write performance of at least 0.5MB/s.
• [8.2/T-0-3] MUST ensure a sequential read performance of at least 15MB/s.
• [8.2/T-0-4] MUST ensure a random read performance of at least 3.5MB/s.

If Television device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

• [8.3/T-1-1] MUST provide user affordance to enable and disable the battery saver feature.

If Television device implementations do not have a battery they:

If Television device implementations have a battery they:

• [8.3/T-1-3] MUST provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.

Television device implementations:

• [8.4/T-0-1] MUST provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
• [8.4/T-0-2] MUST report all power consumption values in milliampere hours (mAh).
• [8.4/T-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the kernel module implementation.
• [8.4/T] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
• [8.4/T-0-4] MUST make this power usage available via the shell command to the app developer.

2.3.5. Security Model

Television device implementations:

• [9.11/T-0-1] MUST back up the keystore implementation with an isolated execution environment.
• [9.11/T-0-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
• [9.11/T-0-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
• [9.11/T-0-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.

Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a keystore backed by an isolated execution environment and support the key attestation, unless it declares the feature which requires a keystore backed by an isolated execution environment.

If Television device implementations support a secure lock screen, they:

• [9.11/T-1-1] MUST allow the user to choose the Sleep timeout for transition from the unlocked to the locked state, with a minimum allowable timeout up to 15 seconds or less.

2.3.6. Developer Tools and Options Compatibility

Television device implementations:

Rule 6.1.2-1

Requirement

The % character of the file header shall occur at byte offset 0 of the file. The first line of a PDF file is a header identifying the version of the PDF specification to which the file conforms.

Error details

File header does not start at byte offset 0 or does not correctly identify the version of the PDF document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.1.2-2

Requirement

The file header line shall be immediately followed by a comment consisting of a % character followed by at least four characters, each of whose encoded byte values shall have a decimal value greater than 127.

Error details

Binary comment in the file header is missing or does not conform to Rule 6.1.2-2.

The presence of encoded character byte values greater than decimal 127 near the beginning of a file is used by various software tools and protocols to classify the file as containing 8-bit binary data that should be preserved during processing.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.1.3-1

Requirement

The file trailer dictionary shall contain the ID keyword. The file trailer referred to is either the last trailer dictionary in a PDF file, as described in PDF Reference 3.4.4 and 3.4.5, or the first page trailer in a linearized PDF file, as described in PDF Reference F.2.

Error details

Missing ID keyword in the document trailer.

Processing systems and documents may contain references to PDF files. Simply storing a file name, however, even in a platform-independent format, does not guarantee that the file can be found. Even if the file still exists and its name has not been changed, different server software applications may identify it in different ways. For example, servers running on DOS platforms must convert all file names to 8 characters and a 3-character extension; different servers may use different strategies for converting longer file names to this format.

External file references can be made more reliable by including a file identifier in the file itself and using it in addition to the normal platform-based file designation. File identifiers are defined by the optional ID entry in a PDF file’s trailer dictionary. The value of this entry is an array of two strings. The first string is a permanent identifier based on the contents of the file at the time it was originally created, and does not change when the file is incrementally updated. The second string is a changing identifier based on the file’s contents at the time it was last updated. When a file is first written, both identifiers are set to the same value. If both identifiers match when a file reference is resolved, it is very likely that the correct file has been found; if only the first identifier matches, then a different version of the correct file has been found.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 3.3.4, 3.3.5, 9.3, F.2

Rule 6.1.3-2

Requirement

The keyword Encrypt shall not be used in the trailer dictionary.

Error details

Encrypt keyword is present in the trailer dictionary.

The explicit prohibition of the Encrypt keyword has the implicit effect of disallowing encryption and password-protected access permissions.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.1.3-3

Requirement

No data shall follow the last end-of-file marker except a single optional end-of-line marker.

Error details

Data is present after the last end-of-file marker.

The trailer of a PDF file enables an application reading the file to quickly find the cross-reference table and certain special objects. Applications should read a PDF file from its end. The last line of the file contains only the end-of-file marker, %%EOF. Some PDF viewers require only that the %%EOF marker appear somewhere within the last 1024 bytes of the file. But having any data after %%EOF marker introduces risks that the PDF document might not be processed correctly.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.1.3-4

Requirement

In a linearized PDF, if the ID keyword is present in both the first page trailer dictionary and the last trailer dictionary, the value to both instances of the ID keyword shall be identical.

Error details

The Linearized PDF contains both the ID keyword in the last trailer and in the the first page trailer, and these IDs do not match.

A linearized PDF file is one that has been organized in a special way to enable efficient incremental access in a network environment. The file is valid PDF in all respects, and is compatible with all existing viewers and other PDF applications. Enhanced viewer applications can recognize that a PDF file has been linearized and can take advantage of that organization (as well as added “hint” information) to enhance viewing performance.

As a result of this optimization, the ID of the linearized PDF can be fount in two different places: in the last document trailer and in the trailer for the first page, normally located at the beginning of the document. These two IDs shall be identical to avoid any ambiguities in identifying the PDF document by its ID entry.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • ISO 19005-1:2005/Cor.2:2011, 6.1.3
  • Rule 6.1.3-1

Rule 6.1.4-1

Requirement

In a cross reference subsection header the starting object number and the range shall be separated by a single SPACE character (20h).

Error details

Spacings of a subsection header in the cross reference table do not conform to Rule 6.1.4-1.

The cross-reference table contains information that permits random access to indirect objects within the file, so that the entire file need not be read to locate any particular object. The table contains a one-line entry for each indirect object, specifying the location of that object within the body of the file.

The cross-reference table is the only part of a PDF file with a fixed format; this permits entries in the table to be accessed randomly. Any variations in this format, including unnecessary SPACE charaters may result in incorrect parsing of the cross-reference table and, thus, errors in reading the PDF document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.1.4-2

Requirement

The xref keyword and the cross reference subsection header shall be separated by a single EOL marker.

Error details

Spacings after the “xref” keyword in the cross reference table do not conform to Rule 6.1.4-2.

As mentioned in Rule 6.1.4-1, any variations in cross reference table format may result in incorrect parsing of the cross-reference table and, thus, errors in reading the PDF document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.1.6-1

Requirement

Hexadecimal strings shall contain an even number of non-white-space characters.

Error details

A hexadecimal string contains odd number of non-white-space characters.

Strings in PDF documents may be written as a literal byte sequence or as a hexadecimal string; the latter is useful for including arbitrary binary data in a PDF file. A hexadecimal string is written as a sequence of hexadecimal digits (0–9 and either A–F or a–f) enclosed within angle brackets (< and >):

Each pair of hexadecimal digits defines one byte of the string. White-space characters (such as space, tab, carriage return, line feed, and form feed) are ignored.

PDF Validation Technical Working Group notes

White-space characters are defined as NULL (00h), TAB (09h), LINE FEED (0Ah), FORM FEED (0Ch), CARRIGE RETURN (0Dh), SPACE (20h). They may appear within hexadecimal strings for formatting purposes:

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.1.6-2

Requirement

All non-white-space characters in hexadecimal strings shall be in the range 0 to 9, A to F or a to f.

Error details

Hexadecimal string contains non-white-space characters outside the range 0 to 9, A to F or a to f.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Other references:

Rule 6.1.7-1

Requirement

The value of the Length key specified in the stream dictionary shall match the number of bytes in the file following the LINE FEED character after the stream keyword and preceding the EOL marker before the endstream keyword.

Error details

Actual length of the stream does not match the value of the Length key in the Stream dictionary.

Every stream dictionary has a Length entry that indicates how many bytes of the PDF file are used for the stream’s data. (If the stream has a filter, Length is the number of bytes of encoded data.) In addition, most filters are defined so that the data is self-limiting; that is, they use an encoding scheme in which an explicit end-of-data (EOD) marker delimits the extent of the data. Finally, streams are used to represent many objects from whose attributes a length can be inferred. All of these constraints must be consistent.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.1.7-2

Requirement

The stream keyword shall be followed either by a CARRIAGE RETURN (0Dh) and LINE FEED (0Ah) character sequence or by a single LINE FEED character. The endstream keyword shall be preceded by an EOL marker.

Error details

Spacings of keywords “stream” and “endstream” do not conform to Rule 6.1.7-2.

These requirements remove potential ambiguity regarding the ending of stream content.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.1.7-3

Requirement

A stream object dictionary shall not contain the F, FFilter, or FDecodeParms keys.

Error details

A stream object dictionary contains one of the F, FFilter, or FDecodeParms keys.

These keys are used to point to document content external to the file. The explicit prohibition of these keys has the implicit effect of disallowing external content that can create external dependencies and complicate preservation efforts.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • 19005-1:2005/Cor.2:2011, 6.1.7

Rule 6.1.8-1

Requirement

The object number and generation number shall be separated by a single white-space character. The generation number and obj keyword shall be separated by a single white-space character. The object number and endobj keyword shall each be preceded by an EOL marker. The obj and endobj keywords shall each be followed by an EOL marker.

Error details

Spacings of object number and generation number or keywords “obj” and “endobj” do not conform to Rule 6.1.8-1.

The definition of an indirect object in a PDF file consists of its object number and generation number, followed by the value of the object itself bracketed between the keywords “obj” and “endobj”. The requirements of this rule guarantee that the definition of an indirect object can be parsed unambiguously.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.1.10-1

Requirement

The LZWDecode filter shall not be permitted.

Error details

LZW compression is used.

The use of the LZW compression algorithm has been subject to intellectual property constraints.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.1.10-2

Requirement

The LZWDecode filter shall not be permitted.

Error details

LZW compression is used in the inline image.

Inline images are defined directly within the content stream in which it will be painted, rather than as separate objects. The use of LZW compression is also not permitted for such images.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Other references:

Rule 6.1.11-1

Requirement

A file specification dictionary, as defined in PDF 3.10.2, shall not contain the EF key.

Error details

A file specification dictionary contains the EF key.

This key is used to encapsulate files containing arbitrary content within a PDF file. The explicit prohibition of EF key has the implicit effect of disallowing embedded files that can create external dependencies and complicate preservation efforts.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 3.10.2

Rule 6.1.11-2

Requirement

A file’s name dictionary, as defined in PDF Reference 3.6.3, shall not contain the EmbeddedFiles key.

Error details

The document contains embedded files (EmbeddedFiles key is present in the file’s name dictionary).

PDF/A-1 standard does not permit embedded files. This requirement was relaxed in PDF/A-2 to embed other PDF documents conforming to either PDF/A-1 or PDF/A-2, and in PDF/A-3 to allow any embedded files.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.1.12-1

Requirement

Largest Integer value is 2,147,483,647. Smallest integer value is -2,147,483,648.

Error details

Integer value is out of range.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.12-2

Requirement

Absolute real value must be less than or equal to 32767.0.

Error details

Real value is out of range.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.12-3

Requirement

Maximum length of a string (in bytes) is 65535.

Error details

Maximum length of a String (65535) is exceeded.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.12-4

Requirement

Maximum length of a name (in bytes) is 127.

Error details

Maximum length of a Name (127 bytes) is exceeded.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.12-5

Requirement

Maximum capacity of an array (in elements) is 8191.

Error details

Maximum capacity of an array (8191) is exceeded.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.12-6

Requirement

Maximum capacity of a dictionary (in entries) is 4095.

Error details

Maximum capacity of a dictionary (4095) is exceeded.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.12-7

Requirement

Maximum number of indirect objects in a PDF file is 8,388,607.

Error details

Maximum number of indirect objects (8,388,607) in a PDF file is exceeded.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.12-8

Requirement

Maximum depth of graphics state nesting by q and Q operators is 28.

Error details

Maximum depth of graphics state nesting (q and Q operators) is exceeded.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.12-9

Requirement

Maximum number of DeviceN components is 8.

Error details

Maximum number of DeviceN components (8) is exceeded.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.12-10

Requirement

Maximum value of a CID (character identifier) is 65,535.

Error details

Maximum value of a CID (65,535) is exceeded.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF Reference 1.4, Table C.1

Rule 6.1.13-1

Requirement

The document catalog dictionary shall not contain a key with the name OCProperties.

Error details

The document catalog dictionary contains the OCProperties entry.

The explicit prohibition of the OCProperties key has the implicit effect of disallowing optional content that generates alternative renderings of a document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.2.2-1

Requirement

A PDF/A-1 OutputIntent is an OutputIntent dictionary, as defined by PDF Reference 9.10.4, that is included in the file’s OutputIntents array and has GTS_PDFA1 as the value of its S key and a valid ICC profile stream as the value its DestOutputProfile key.

Error details

The embedded PDF/A Output Intent colour profile is either invalid or does not provide BToA information.

PDF/A standard requires that all colours shall be specified in a device-independent manner, either directly by the use of a device-independent colour space, or indirectly by the use of an OutputIntent.

The BToA information in ICC profiles connects the PDF colour space with the colour space of the output device.

The ICC specification is an evolving standard. The ICCBased color spaces supported in PDF 1.3 are based on ICC specification version 3.3; those in PDF 1.4 are based on the ICC specification ICC.1:1998-09 and its addendum ICC.1A:1999-04.

PDF Validation Technical Working Group notes

It is generally accepted in practice that PDF/A-1 documents may use any ICC colour profiles with their internal version number “major.minor”, where “major” number is 2 or less. Such output profiles are fully backward compatible with the ICC specification ICC.1A:1999-04, which has internal version number “2.3”.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.2.2-2

Requirement

If a file’s OutputIntents array contains more than one entry, then all entries that contain a DestOutputProfile key shall have as the value of that key the same indirect object, which shall be a valid ICC profile stream.

Error details

File’s OutputIntents array contains several output intent dictionaries with non-matching destination output profiles.

A PDF document may conform to several PDF standarda at the same time, such as PDF/X, PDF/E or PDF/UA. Each of these standards relies on the presense of the OutputIntent color profile and has to identify such profile via a standard-specific subtype entry (S key in the OutputIntent dictionary). For example, the value of this key is “GTS_PDFA1” for the PDF/A standards, and is “GTS_PDFX” for PDF/X standards.

The requirement for all output intent dictionaries to share the same output ICC profile mimimizes risks that a wrong ICC output profile is used for rendering the PDF document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.2.3-1

Requirement

All ICCBased colour spaces shall be embedded as ICC profile streams as described in PDF Reference 4.5

Error details

The embedded ICC profile is either invalid or does not satisfy PDF 1.4 requirements.

ICC profiles can be used in PDF documents to identify the source color spaces. Similar to the requirements for the ICC output profile (see Rule 6.2.2-1), the embedded ICC input profile shall satisfy a number of additional requements of PDF 1.4 Specification. These requirements cover the device calss of the ICC profile, its connection color space and the version of the ICC standard the input profile is based on.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 4.5.4, ICCBased Color Spaces
  • International Color Consortium, ICC Specifications
  • Rule 6.2.2-1

Rule 6.2.3-2

Requirement

DeviceRGB may be used only if the file has a PDF/A-1 OutputIntent that uses an RGB colour space.

Error details

DeviceRGB colour space is used without RGB-based output intent ICC profile.

A conforming PDF/A document may use either DeviceRGB or DeviceCMYK colour spaces, but shall not use both. In an uncalibrated colour space is used in a file then that file shall contain an PDF/A-1 OutputIntent specifying the output ICC profile with matching colour space.

When rendering colours specified in a device-dependent colour space a conforming reader shall use file’s PDF/A-1 OutputIntent dictionary as the source colour space. This guarantees unambiguous and device-independent representation of all colours used in the conforming PDF/A document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.2.3-3

Requirement

DeviceCMYK may be used only if the file has a PDF/A-1 OutputIntent that uses an CMYK colour space.

Error details

DeviceCMYK colour space is used without RGB-based output intent ICC profile.

A conforming PDF/A document may use either DeviceRGB or DeviceCMYK colour spaces, but shall not use both. In an uncalibrated colour space is used in a file then that file shall contain an PDF/A-1 OutputIntent specifying the output ICC profile with matching colour space.

When rendering colours specified in a device-dependent colour space a conforming reader shall use file’s PDF/A-1 OutputIntent dictionary as the source colour space. This guarantees unambiguous and device-independent representation of all colours used in the conforming PDF/A document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.2.3-4

Requirement

If an uncalibrated colour space is used in a file then that file shall contain a PDF/A-1 OutputIntent, as defined in 6.2.2.

Error details

DeviceGray colour space is used without output intent ICC profile.

When rendering a DeviceGray colour specification in a file whose OutputIntent is an RGB profile, a conforming reader shall convert the DeviceGray colour specification to RGB by the method described in PDF 1.4 Reference 6.2.1:

When rendering a DeviceGray colour specification in a file whose OutputIntent is a CMYK profile, a conforming reader shall convert the DeviceGray colour specification to DeviceCMYK by the method described in PDF 1.4 Reference 6.2.2:

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 6.2.1, 6.2.2

Rule 6.2.3-5

Requirement

All ICCBased colour spaces shall be embedded as ICC profile streams as described in PDF Reference 4.5.

Error details

The N entry in the ICC profile dictionary is missing or does not match the number of components in the embedded ICC profile.

PDF 1.4 References requires that the number of color components in the color space described by the ICC profile data must match the number of components actually in the ICC profile. As of PDF 1.4, N must be 1, 3, or 4.

A conforming reader shall render ICCBased colour spaces as specified by the ICC specification, and shall not use the Alternate colour space specified in an ICC profile stream dictionary.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 4.5.4, Table 4.16

Rule 6.2.4-1

Requirement

An Image dictionary shall not contain the Alternates key.

Error details

Alternates key is present in the Image dictionary.

Alternate images provide a straightforward and backward-compatible way to include multiple versions of an image in a PDF file for different purposes. These variant representations of the image may differ, for example, in resolution or in color space. The primary goal is to reduce the need to maintain separate versions of a PDF document for low-resolution on-screen viewing and highresolution printing. However, this mechanism is prohibited in PDF/A-compliant documents, as it introduces risks of choosing different images for rendering.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 4.8.4, Alternate Images

Rule 6.2.4-2

Requirement

An XObject dictionary (Image or Form) shall not contain the OPI key.

Error details

OPI key is present in an XObject dictionary.

The Open Prepress Interface (OPI) is a mechanism, originally developed by Aldus Corporation, for creating low-resolution placeholders, or proxies, for such high-resolution images. The proxy typically consists of a downsampled version of the full-resolution image, to be used for screen display and proofing. Before the document is printed, it passes through a filter known as an OPI server, which replaces the proxies with the original full-resolution images. Similar to Rule 6.2.4-1, this mechanism is prohibited in PDF/A-compliant documents, as it introduces risks of unpredictable PDF rendering.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 9.10.6, Open Prepress Interface (OPI)
  • Rule 6.2.4-1

Rule 6.2.4-3

Requirement

If an Image dictionary contains the Interpolate key, its value shall be false.

Error details

The value of the Interpolate key in the Image dictionary is true.

When the resolution of a source image is significantly lower than that of the output device, each source sample covers many device pixels. This can cause images to appear “jaggy” or “blocky.” These visual artifacts can be reduced by applying an image interpolation algorithm during rendering. Instead of painting all pixels covered by a source sample with the same color, image interpolation attempts to produce a smooth transition between adjacent sample values.

However, the interpolation algorithm is implementation-dependent and is not specified by PDF. Image interpolation may not always be performed for some classes of images or on some output devices. Therefore, this mechanism is not permitted in PDF/A-compliant documents.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 4.8.4, Image interpolation

Rule 6.2.5-1

Requirement

A form XObject dictionary shall not contain the Subtype2 key with a value of PS or the PS key.

Error details

The form XObject dictionary contains a PS key or Subtype2 key with value PS.

In earlier versions of PDF, a content stream can include PostScript language fragments. These fragments are used only when printing to a PostScript output device; they have no effect either when viewing the document on-screen or when printing to a non-PostScript device. In addition, applications that understand PDF are unlikely to be able to interpret the PostScript fragments. Hence, this capability should be used with extreme caution and only if there is no other way to achieve the same result. Inappropriate use of PostScript XObjects can cause PDF files to print incorrectly.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 4.10, PostScript XObjects

Rule 6.2.6-1

Requirement

A conforming file shall not contain any reference XObjects.

Error details

The document contains a reference XObject (Ref key in the form XObject dictionary).

Reference XObjects enable one PDF document to import content from another. The document in which the reference occurs is called the containing document; the one whose content is being imported is the target document. The target document may reside in a file external to the containing document or may be included within it as an embedded file stream.

As this makes the inital PDF document depentent on the presence of external resources, this mechanism is not permitted in PDF/A-compliant documents.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 4.9.3, Reference XObjects

Rule 6.2.7-1

Requirement

A conforming file shall not contain any PostScript XObjects.

Error details

The document contains a PostScript XObject.

PostScript XObjects contain arbitrary executable PostScript code streams that have the potential to interfere with reliable and predictable rendering. See Rule 6.2.5-1 for more detail.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 4.10, PostScript XObjects
  • Rule 6.2.5-1

Rule 6.2.8-1

Requirement

An ExtGState dictionary shall not contain the TR key.

Error details

An ExtGState dictionary contains the TR key.

In PDF, a transfer function adjusts the values of color components to compensate for nonlinear response in an output device and in the human eye. Each component of a device color space (for example, the red component of the DeviceRGB space) is intended to represent the perceived lightness or intensity of that color component in proportion to the component’s numeric value. Many devices do not actually behave this way, however; the purpose of a transfer function is to compensate for the device’s actual behavior.

As this may lead in significantly different visual appearance of PDF documents on different devices, the use of transfer functions is not permitted by PDF/A.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 6.3, Transfer Functions

Rule 6.2.8-2

Requirement

An ExtGState dictionary shall not contain the TR2 key with a value other than Default.

Error details

An ExtGState dictionary contains the TR2 key with a value other than Default.

The TR2 key has the same meaning as TR key (see Rule 6.2.8-1) except that the value may also be the name or name Default, denoting the transfer function used by deafult by the output device. And this is the only case, permitted in PDF/A-compliant documents.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.2.9-1

Requirement

Where a rendering intent is specified, its value shall be one of the four values defined in PDF Reference RelativeColorimetric, AbsoluteColorimetric, Perceptual or Saturation.

Error details

A rendering intent with non-standard value is used.

Although CIE-based color specifications are theoretically device-independent, they are subject to practical limitations in the color reproduction capabilities of the output device. Such limitations may sometimes require compromises to be made among various properties of a color specification when rendering colors for a given device. Specifying a rendering intent allows a PDF file to set priorities regarding which of these properties to preserve and which to sacrifice.

PDF 1.4 defines four standard rendering intents, which can be specificed directly in the page content stream via the “ri” operator or attached to any image as an extra property. These standard intents have been deliberately chosen to correspond closely to those defined by the International Color Consortium (ICC), an industry organization that has developed standards for device-independent color.

However, that the exact set of rendering intents supported may vary from one output device to another; a particular device may not support all possible intents, or may support additional ones beyond those listed in the table. To guarantee the predictability of PDF rendering results, non-standard rendering intents are not permitted in PDF/A-compliant documents.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 4.5.4, Rendering Intents

Rule 6.2.10-1

Requirement

A content stream shall not contain any operators not defined in PDF Reference even if such operators are bracketed by the BX/EX compatibility operators.

Error details

A content stream contains an operator not defined in PDF Reference.

Ordinarily, when a viewer application encounters an operator in a content stream that it does not recognize, an error will occur. A pair of compatibility operators, BX and EX, modify this behavior. These operators must occur in pairs and may be nested. They bracket a compatibility section, a portion of a content stream within which unrecognized operators are to be ignored without error. This mechanism enables a PDF document to use operators defined in newer versions of PDF without sacrificing compatibility with older viewers.

However, as the use of undefined operators may still result in error for some PDF processors, their use is not permitted in PDF/A-compliant documents, even if they are bracketed by BX/EX compatibility operators.

In earlier versions of the PDF format a PostScript operator “PS” was defined. As this operator is not defined in PDF Reference its use is implicitly prohibited by PDF/A-1 specification.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Specification, 3.7.1, Content Streams

Rule 6.3.2-1

Requirement

All fonts used in a conforming file shall conform to the font specifications defined in PDF Reference 5.5.

Type - name - (Required) The type of PDF object that this dictionary describes; must be Font for a font dictionary.

Error details

A Font dictionary has missing or invalid Type entry

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.5.1 - Table 5.8
  • PDF 1.4 Reference, 5.5.4 - Table 5.9
  • PDF 1.4 Reference, 5.6.3 - Table 5.13
  • PDF 1.4 Reference, 5.6.5 - Table 5.17

Rule 6.3.2-2

Requirement

All fonts used in a conforming file shall conform to the font specifications defined in PDF Reference 5.5.

Subtype - name - (Required) The type of font; must be “Type1” for Type 1 fonts, “MMType1” for multiple master fonts, “TrueType” for TrueType fonts “Type3” for Type 3 fonts, “Type0” for Type 0 fonts and “CIDFontType0” or “CIDFontType2” for CID fonts.

Error details

A Font dictionary has missing or invalid Subtype entry.

The correct value of the Subtype entry in the font dictionary is critical for the text rendering in PDF documents.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.5.1 - Table 5.8
  • PDF 1.4 Reference, 5.5.4 - Table 5.9
  • PDF 1.4 Reference, 5.6.3 - Table 5.13
  • PDF 1.4 Reference, 5.6.5 - Table 5.17

Rule 6.3.2-3

Requirement

All fonts used in a conforming file shall conform to the font specifications defined in PDF Reference 5.5.

BaseFont - name - (Required) The PostScript name of the font.

Error details

A BaseFont entry is missing or has invalid type.

For Type 1 fonts, this is usually the value of the FontName entry in the font program. The PostScript name of the font can be used to find the font’s definition in the viewer application or its environment. It is also the name that will be used when printing to a PostScript output device.

For TrueType fonts the value of BaseFont is determined in one of two ways. It is defined as the PostScript name that is an optional entry in the “name” table of the TrueType font itself. In the absence of such an entry in the “name” table, a PostScript name is derived from the name by which the font is known in the host operating system.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.5.1 - Table 5.8
  • PDF 1.4 Reference, 5.5.4 - Table 5.9
  • PDF 1.4 Reference, 5.6.3 - Table 5.13
  • PDF 1.4 Reference, 5.6.5 - Table 5.17

Rule 6.3.2-4

Requirement

All fonts used in a conforming file shall conform to the font specifications defined in PDF Reference 5.5.

FirstChar - integer - (Required except for the standard 14 fonts) The first character code defined in the font’s Widths array.

Error details

A non-standard simple font dictionary has missing or invalid FirstChar entry.

The PostScript names of 14 Type 1 fonts, known as the standard fonts, are as follows:

These fonts, or their font metrics and suitable substitution fonts, are guaranteed to be available to any viewer application.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.5.1 - Table 5.8
  • PDF 1.4 Reference, 5.5.4 - Table 5.9

Rule 6.3.2-5

Requirement

All fonts used in a conforming file shall conform to the font specifications defined in PDF Reference 5.5.

FirstChar - integer - (Required except for the standard 14 fonts) The first character code defined in the font’s Widths array.

Error details

A non-standard simple font dictionary has missing or invalid LastChar entry.

See also Rule 6.3.2-4.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.5.1 - Table 5.8
  • PDF 1.4 Reference, 5.5.4 - Table 5.9
  • Rule 6.3.2-4

Rule 6.3.2-6

Requirement

All fonts used in a conforming file shall conform to the font specifications defined in PDF Reference 5.5.

Widths - array - (Required except for the standard 14 fonts; indirect reference preferred) An array of (LastChar − FirstChar + 1) widths.

Error details

Widths array is missing or has invalid size.

See also Rule 6.3.2-4.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.5.1 - Table 5.8
  • PDF 1.4 Reference, 5.5.4 - Table 5.9
  • Rule 6.3.2-4

Rule 6.3.2-7

Requirement

All fonts used in a conforming file shall conform to the font specifications defined in PDF Reference 5.5.

The use of OpenType fonts is not allowed in PDF/A Part 1.

Error details

The subtype of the embedded font program is determined as follows.

• PostScript Type1, if referenced by /FontFile key in the font descriptor dictionary
• TrueType, if referenced by /FontFile2 key in the font descriptor dictionary
• Type1 (or CID Type1), if referenced by /FontFile3 key.

In the latter case the Subtype key in the referenced stream object is used to determine the exact font type. The only valid values of this key in PDF 1.4 are:

• Type1C - Type 1–equivalent font program represented in the Compact Font Format (CFF) and

• CIDFontType0C - Type 0 CIDFont program represented in the Compact Font Format (CFF).

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.8 - Table 5.22
  • PAdobe Technical Note #5176, The Compact Font Format Specification

Rule 6.3.3-1

Requirement

For any given composite (Type 0) font referenced within a conforming file, the CIDSystemInfo entries of its CIDFont and CMap dictionaries shall be compatible.

Error details

Registry and Ordering entries in the CIDFont and CMap dictionaries of a Type 0 font are not compatible.

CIDFont and CMap dictionaries contain a CIDSystemInfo entry specifying the character collection assumed by the CIDFont or by each CIDFont associated with the CMap – that is, the interpretation of the CID numbers used by the CIDFont. A character collection is uniquely identified by the Registry, Ordering, and Supplement entries in the CIDSystemInfo dictionary. Character collections whose Registry and Ordering values are the same are compatible.

PDF/A-1 standard requires that the Registry and Ordering strings of the CIDSystemInfo dictionaries for that font shall be identical, unless the value of the CMap dictionary UserCMap key is “Identity-H” or “Identity-V”.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.6.2
  • ISO 19005-1:2005/Cor.2:2011, 6.3.3

Rule 6.3.3-2

Requirement

For all Type 2 CIDFonts, the CIDFont dictionary shall contain a CIDToGIDMap entry that shall be a stream mapping from CIDs to glyph indices or the name Identity, as described in PDF Reference Table 5.13.

Error details

A Type 2 CIDFont dictionary has missing or invalid CIDToGIDMap entry.

For Type 2, the CIDFont program is actually a TrueType font program, which has no native notion of CIDs. In a TrueType font program, glyph descriptions are identified by glyph index values. Glyph indices are internal to the font and are not defined consistently from one font to another. Instead, a TrueType font program contains a “cmap” table that provides mappings directly from character codes to glyph indices for one or more predefined encodings.

If the TrueType font program is embedded, the Type 2 CIDFont dictionary must contain a CIDToGIDMap entry that maps CIDs to the glyph indices for the appropriate glyph descriptions in that font program.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.6.3 - Table 5.13

Rule 6.3.3-3

Requirement

All CMaps used within a conforming file, except Identity-H and Identity-V, shall be embedded in that file as described in PDF Reference 5.6.4.

Error details

A CMap is different from “Identity-H” or “Identity-V” and is not embedded.

A CMap specifies the mapping from character codes to character selectors (CIDs, or character codes) in the associated CIDFont. It serves a function analogous to the Encoding dictionary for a simple font.

A CMap may be specified in two ways: as a name object identifying a predefined CMap, whose definition is known to the viewer application, or as a stream object whose contents are an embedded CMap file.

The “Identity−H” and “Identity−V” CMaps are two predefined CMap names that can be used to refer to characters directly by their CIDs when showing a text string.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.3.3-4

Requirement

For those CMaps that are embedded, the integer value of the WMode entry in the CMap dictionary shall be identical to the WMode value in the embedded CMap stream.

Error details

WMode entry in the embedded CMap and in the CMap dictionary are not identical.

A CMap also specifies the writing mode (horizontal or vertical) for any CIDFont with which the CMap is combined. This determines which metrics are to be used when glyphs are painted from that font.

In case of embedded CMap file, the writing mode is specified in two different places: in the PDF dictionary associated with the embedded CMap, and inside the embedded CMap file itself. To aviod any ambiguities, PDF/A standard requires that values of these two writing modes coincide.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.3.4-1

Requirement

The font programs for all fonts used within a conforming file shall be embedded within that file, as defined in PDF Reference 5.8, except when the fonts are used exclusively with text rendering mode 3.

Error details

The font program is not embedded.

Text rendering mode 3 specifies that glyphs are not stroked, filled or used as a clipping boundary. A font referenced for use solely in this mode is therefore not rendered and is thus exempt from the embedding requirement.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.3.5-1

Requirement

Embedded font programs shall define all font glyphs referenced for rendering with conforming file.

Error details

Not all glyphs referenced for rendering are present in the embedded font program, which is used with text rendering modes other than 3.

All conforming PDF/A readers shall use the embedded fonts, rather than other locally resident, substituted or simulated fonts, for rendering.

The fonts used exclusively with text rendering mode 3 (invisible) are exempt from this requirement. OCR solutions often use such invisible fonts on top of the original scanned image to enable selection and copying of recognized text.

There is no exemption from the requirements of this rule for the 14 standard Type 1 fonts. See Rule 6.3.2-4 for the list of all standard fonts.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.3.5-2

Requirement

For all Type 1 font subsets referenced within a conforming file, the font descriptor dictionary shall include a CharSet string listing the character names defined in the font subset, as described in PDF Reference Table 5.18.

Error details

A Type1 font subset does not define CharSet entry in its Descriptor dictionary.

Font subsets are acceptable by PDF/A as long as the embedded font programs provide glyph definitions for all characters referenced within the file. Embedding the font programs allows any conforming reader to reproduce correctly all glyphs in the manner in which they were originally published without reference to possibly ephemeral external resources.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.3.5-3

Requirement

For all CIDFont subsets referenced within a conforming file, the font descriptor dictionary shall include a CIDSet stream identifying which CIDs are present in the embedded CIDFont file, as described in PDF Reference Table 5.20.

Error details

A CID Font subset does not define CIDSet entry in its Descriptor dictionary.

The CIDSet stream data is organized as a table of bits indexed by CID. The bits should be stored in bytes with the high-order bit first. Each bit corresponds to a CID. The first bit of the first byte corresponds to CID 0, the next bit to CID 1, and so on.

See also Rule 6.3.5-2.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 5.5.3
  • Rule 6.3.5-2.

Rule 6.3.6-1

Requirement

For every font embedded in a conforming file, the glyph width information stored in the Widths entry of the font dictionary and in the embedded font program shall be consistent.

Error details

Glyph width information in the embedded font program is not consistent with the Widths entry of the font dictionary.

This requirement is necessary to ensure predictable font rendering, regardless of whether a given reader uses the metrics in the Widths entry or those in the font program.

Fonts used exclusively in text rendering mode 3 (invisible) are exempt from this requirement.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.3.7-1

Requirement

All non-symbolic TrueType fonts shall specify MacRomanEncoding or WinAnsiEncoding, either as the value of the Encoding entry in the font dictionary or as the value of the BaseEncoding entry in the dictionary that is the value of the Encoding entry in the font dictionary. If the value of the Encoding entry is a dictionary, it shall not contain a Differences entry.

Error details

A non-symbolic TrueType font has an encoding different from MacRomanEncoding or WinAnsiEncoding.

Because some aspects of TrueType glyph selection are dependent on the viewer implementation or the operating system, PDF files that use TrueType fonts should follow certain guidelines to ensure predictable behavior across all viewer applications.

This requirement makes normative the suggested guidelines described in PDF 1.4 Reference 5.5.5.

A Font is called non-symbolc, if its character set is the Adobe standard Latin character set (or a subset of it) and it uses the standard names for those characters. The characters in this character set are given in PDF 1.4 Reference, Section D.1, “Latin Character Set and Encodings.”

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • ISO19005-1:2005/Cor.2:2011, 6.3.7
  • PDF 1.4 Reference, 5.5.5.
  • PDF 1.4 Reference, Section D.1, “Latin Character Set and Encodings.”

Rule 6.3.7-2

Requirement

All symbolic TrueType fonts shall not specify an Encoding entry in the font dictionary.

Error details

A symbolic TrueType font specifies an Encoding entry in its dictionary.

A Font is called symbolic if it contains characters outside the Adobe standard Latin character set. It is marked by special flag in its font descriptor dictionary.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • ISO19005-1:2005/Cor.2:2011, 6.3.7
  • PDF 1.4 Reference, 5.5.5
  • PDF 1.4 Reference, Section D.1, “Latin Character Set and Encodings.”
  • Rule 6.3.7-1

Rule 6.3.7-3

Requirement

Font programs’ “cmap” tables for all symbolic TrueType fonts shall contain exactly one encoding.

Error details

The embedded font program for a symbolic TrueType font contains more than one cmap subtable.

A TrueType font program’s built-in encoding maps directly from character codes to glyph descriptions, using an internal data structure called a “cmap” (not to be confused with the CMap from Rules 6.3.3-3 and 6.3.3-4). A TrueType font program can contain multiple encodings that are intended for use on different platforms (such as Mac OS and Windows).

A Font is called symbolic if it contains characters outside the Adobe standard Latin character set. It is marked by special flag in its font descriptor dictionary. Such fonts may use implementation-specific glyph names and are required by PDF/A-1 standard to have to Encoding entry in its font dictionary (see Rule 6.3.7-2). In addition to this, the corresponding embedded TrueType program shall have only one cmap subtable to aviod ambiguities in the mapping from character codes to glyph indices in the embedded font.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • ISO19005-1:2005/Cor.2:2011, 6.3.7
  • PDF 1.4 Reference, 5.5.5
  • PDF 1.4 Reference, Section D.1, “Latin Character Set and Encodings.”
  • Rule 6.3.7-2

Rule 6.3.8-1

Requirement

Each character used in the page shall be mapped to Unicode.

Error details

According to PDF Reference, characters can be mapped to Unicode in several ways:

• The font dictionary shall include a ToUnicode entry whose value is a CMap stream object that maps character codes to Unicode values, as described in PDF Reference 5.9, unless the font meets any of the following three conditions:
• fonts that use the predefined encodings MacRomanEncoding, MacExpertEncoding or WinAnsiEncoding, or that use the predefined Identity-H or Identity-V CMaps;
• Type 1 fonts whose character names are taken from the Adobe standard Latin character set or the set of named characters in the Symbol font, as defined in PDF Reference Appendix D;

• Type 0 fonts whose descendant CIDFont uses the Adobe-GB1, Adobe-CNS1, Adobe-Japan1 or Adobe-Korea1 character collections.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A

Rule 6.4-1

Requirement

If an SMask key appears in an ExtGState dictionary, its value shall be None.

Error details

An ExtGState contains SMask key with a value other than None.

The SMask key in an ExtGState dictionary defines the soft mask, which specifies the mask shape or mask opacity values to be used in the PDF transparent imaging model.

This provision, along with Rules 6.4-2 to 6.4-6, prohibits the use of transparency within a conforming PDF/A-1 document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 7.2.6, 7.5.4

Rule 6.4-2

Requirement

An XObject dictionary shall not contain the SMask key.

Error details

An XObject contains an SMask key.

The SMask key in XObject dictionaries specifies a subsidiary image XObject defining a soft-mask image to be used as a source of mask shape or mask opacity values in the PDF transparent imaging model.

This provision, along with Rules 6.4-1 and 6.4-3 to 6.4-6, prohibits the use of transparency within a conforming PDF/A-1 document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • ISO19005-1:2005/Cor.2:2011, 6.4

Rule 6.4-3

Requirement

A Group object with an S key with a value of Transparency shall not be included in a form XObject.

A Group object with an S key with a value of Transparency shall not be included in a page dictionary.

Error details

A transparency group is present in a form XObject or page dictionary.

A group XObject is a special type of form XObject that can be used to group graphical elements together as a unit for various purposes. It is distinguished by the presence of the optional Group entry in the form dictionary. The value of this entry is a subsidiary group attributes dictionary describing the properties of the group.

A transparency group XObject is defined as a group whose S (subtype) key has value Transparency. It represents a transparency group for use in the PDF transparent imaging model.

This provision, along with Rules 6.4-1, 6.4-2, and 6.4-4 to 6.4-6, prohibits the use of transparency within a conforming PDF/A-1 document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • ISO19005-1:2005/Cor.2:2011, 6.4

Rule 6.4-4

Requirement

The following keys, if present in an ExtGState object, shall have the values shown: BM - Normal or Compatible.

Error details

An ExtGState dictionary contains the BM key (blend mode) with a value other than Normal or Compatible.

The BM key in the ExtGState dictionary specifies the current blend mode to be used in the PDF transparent imaging model.

The “Normal” blend mode selects the source color, ignoring the backdrop and, thus, corresponding to the traditional non-transparent imaging model. An additional standard blend mode, “Compatible”, is a vestige of an earlier design and is no longer needed, but is still recognized for the sake of compatibility; its effect is equivalent to that of the “Normal” blend mode.

This provision, along with Rules 6.4-1 to 6.4-3, 6.4-5, and 6.4-6, prohibits the use of transparency within a conforming PDF/A-1 document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 7.2.4, 7.5.2

Rule 6.4-5

Requirement

The following keys, if present in an ExtGState object, shall have the values shown: CA - 1.0.

Error details

An ExtGState dictionary contains the CA key (stroke alpha) with a value other than 1.0.

The CA key defines the current stroking alpha constant, specifying the constant shape or constant opacity value to be used for stroking operations in the PDF transparent imaging model.

This provision, along with Rules 6.4-1 to 6.4-4 and 6.4-6, prohibits the use of transparency within a conforming PDF/A-1 document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.4-6

Requirement

The following keys, if present in an ExtGState object, shall have the values shown: ca - 1.0.

Error details

An ExtGState dictionary contains the ca key (fill alpha) with a value other than 1.0.

The ca key defines the current non-stroking alpha constant, specifying the constant shape or constant opacity value to be used for all non-stroking operations (such as path fill or image drawing) in the PDF transparent imaging model.

This provision, along with Rules 6.4-1 to 6.4-5, prohibits the use of transparency within a conforming PDF/A-1 document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.5.2-1

Requirement

Annotation types not defined in PDF Reference shall not be permitted. Additionally, the FileAttachment, Sound and Movie types shall not be permitted.

Error details

Unknown or not permitted annotation type.

An annotation associates an object such as a note, sound, or movie with a location on a page of a PDF document, or provides a means of interacting with the user via the mouse and keyboard. PDF includes a wide variety of standard annotation types, described in detail in PDF 1.4 Reference, 8.4.5, “Annotation Types.”

Support for multimedia content is outside the scope of PDF/A-1, and, thus, annotations of type “Sound” and “Movie” are not permitted. Annotations of type “FileAttachment” are also not permitted, as PDF/A-1 does not allow any file attachments.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:

Rule 6.5.3-1

Requirement

An annotation dictionary shall not contain the CA key with a value other than 1.0.

Error details

An annotation dictionary contains the CA key with value other than 1.0.

The CA key specifies the constant opacity value to be used in painting the annotation. It shall have the value 1.0 similar to stroking and non-stroking constant alpha in the ExtGState dictionary (see Rules 6.4-5 and 6.4-6).

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 7.2.6
  • Rules 6.4-5, 6.4-6

Rule 6.5.3-2

Requirement

An annotation dictionary shall contain the F key. The F key’s Print flag bit shall be set to 1 and its Hidden, Invisible and NoView flag bits shall be set to 0.

Error details

Annotation flags are either missing or have forbidden values.

The value of the annotation dictionary’s F entry is an unsigned 32-bit integer containing flags specifying various characteristics of the annotation. Bit positions within the flag word are numbered from 1 (low-order) to 32 (high-order).

Flag “Invisible” (bit position 1), if clear, allows to display an unknown annotation using an appearance stream specified by its appearance dictionary, if any.

Flag “Hidden” (bit position 2), if set, specifies to not display or print the annotation or allow it to interact with the user, regardless of its annotation type.

Flag “Print” (bit position 3), if set, specifies to print the annotation when the page is printed.

Flag “NoView” (bit position 6), if set, specifies to not display the annotation on the screen or allow it to interact with the user.

The restrictions on annotation flags prevent the use of annotations that are hidden or that are viewable but not printable.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.5.3-3

Requirement

An annotation dictionary shall not contain the C array or the IC array unless the colour space of the DestOutputProfile in the PDF/A-1 OutputIntent dictionary, defined in 6.2.2, is RGB.

Error details

Annotation’s color or interior color is used without specifying RGB-based destination output profile.

These provisions ensure that the device colour spaces used in annotations by mechanisms other than an appearance stream are indirectly defined by means of the PDF/A-1 OutputIntent. See also Rule 6.2.3-2.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.5.3-4

Requirement

For all annotation dictionaries containing an AP key, the appearance dictionary that it defines as its value shall contain only the N key. If an annotation dictionary’s Subtype key has a value of Widget and its FT key has a value of Btn, the value of the N key shall be an appearance subdictionary; otherwise the value of the N key shall be an appearance stream.

Error details

Annotation’s appearance dictionary contains entries other than N or the N entry has an invalid type.

An annotation can define as many as three separate appearances. The normal appearance (N key in the appearance dictionary) is used when the annotation is not interacting with the user. This is also the appearance that is used for printing the annotation. The rollover appearance (R key) is used when the user moves the cursor into the annotation’s active area without pressing the mouse button. The down appearance (R key) is used when the mouse button is pressed or held down within the annotation’s active area.

In accordance with the PDF 1.4 Specification, 8.4.4, a Button form field needs to have multiple appearance states, each one associated with the specific values that the button can take.

PDF Validation Technical Working Group notes

Even if a Button form field has only one state, it is still required to have an appearance subdictionary with a single key as its default (and only) state.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005/Corr.2:2011
• Levels: A, B
• Additional references:
  • ISO19005-1/Cor.2:2011, 6.5.3
  • PDF 1.4 Reference, 8.4.4

Rule 6.6.1-1

Requirement

The Launch, Sound, Movie, ResetForm, ImportData and JavaScript actions shall not be permitted. Additionally, the deprecated set-state and no-op actions shall not be permitted. The Hide action shall not be permitted.

Error details

Unknown or not permitted action type.

Support for multimedia content is outside the scope of PDF/A-1. The ResetForm action changes the rendered appearance of a form. The ImportData action imports form data from an external file. JavaScript actions permit an arbitrary executable code that has the potential to interfere with reliable and predictable rendering.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005/Corr.2:2011
• Levels: A, B
• Additional references:
  • ISO 19005-1:2005/Cor.2:2011, 6.6.1

Rule 6.6.1-2

Requirement

Named actions other than NextPage, PrevPage, FirstPage, and LastPage shall not be permitted.

Error details

Unknown named action.

In response to each of the four allowed named actions, conforming interactive readers shall perform the appropriate action described in PDF 1.4 Reference Table 8.45. Viewer applications may support additional, nonstandard named actions, but any document using them will not be portable.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B
• Additional references:
  • PDF 1.4 Reference, 8.5.3 - Named Actions - Table 8.45

Rule 6.6.1-3

Requirement

Interactive form fields shall not perform actions of any type.

Error details

Interactive form field contains an action object (‘A’ key).

Such actions may modify the values of the forms and alter the visual representation of the document.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.6.2-1

Requirement

A Widget annotation dictionary shall not include an AA entry for an additional-actions dictionary.

Error details

A Widget annotation contains an additional-actions dictionary (AA entry).

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.6.2-2

Requirement

A Field dictionary shall not include an AA entry for an additional-actions dictionary.

Error details

A Field dictionary contains an additional-actions dictionary (AA entry).

These additional-actions dictionaries define arbitrary JavaScript actions. The explicit prohibition of the AA entry has the implicit effect of disallowing JavaScript actions that can create external dependencies and complicate preservation efforts.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.6.2-3

Requirement

The document catalog dictionary shall not include an AA entry for an additional-actions dictionary.

Error details

The document catalog dictionary contains an additional-actions dictionary (AA entry).

These additional-actions dictionaries define arbitrary JavaScript actions. The explicit prohibition of the AA entry has the implicit effect of disallowing JavaScript actions that can create external dependencies and complicate preservation efforts.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.7.2-1

Requirement

The document catalog dictionary of a conforming file shall contain the Metadata key.

Error details

The document catalog dictionary doesn’t contain Metadata key.

Metadata is essential for effective management of a file throughout its life cycle. A file depends on metadata for identification and description, as well as for describing appropriate technical and administrative matters.

Metadata, both for an entire document and for components within a document, can be stored in PDF streams called metadata streams. The contents of a metadata stream is the metadata represented in Extensible Markup Language (XML). The format of the XML representing the metadata is defined as part of a framework called the Extensible Metadata Platform (XMP).

A metadata stream can be attached to a document through the Metadata entry in the document catalog.

• Object type:
• Test condition:
• Specification: ISO 19005-1:2005
• Levels: A, B

Rule 6.7.2-2

Requirement

Metadata object stream dictionaries shall not contain the Filter key.

Error details