car connectivity consortium

Car Connectivity Consortium MirrorLink®

Application Requirements

Version 2.0.8 (CCC-RQ-005)

1

Copyright © 2011-2019 Car Connectivity Consortium LLC

All rights reserved

Confidential

Mirror Link Specification /39

Application Requirements 2.0.8

CCC-RQ-005

Copyright © 2017-2019 Car Connectivity Consortium LLC. All rights reserved.

Confidential

LEGAL NOTICE 1

The copyright in this Specification is owned by the Car Connectivity Consortium LLC (“CCC LLC”). Use of this 2 Specification and any related intellectual property (collectively, the “Specification”), is governed by these license 3 terms, the Developer Agreement found on the Developer Portal (“Developer Agreement”) and the CCC LLC Limited 4 Liability Company Agreement (the “LLC Agreement”). 5

Use of the Specification by anyone who is not a registered developer ("Developer") or a member of the CCC LLC 6 (each such person or party, a “Member”) is prohibited. The legal rights and obligations of Developers are governed 7 by the Developer Agreement found on the Developer Portal. The legal rights and obligations of each Member are 8 governed by the Car Connectivity Consortium LLC Agreement and their applicable Membership Agreement, 9 including without limitation those contained in Article 10 of the LLC Agreement. 10

FOR MEMBERS AND DEVELOPERS 11

CCC LLC hereby grants each Member and Developer a right to use and to make verbatim copies of the Specification 12 for the purposes of implementing the technologies specified in the Specification in their products (“Implementing 13 Products”) under the terms of the LLC Agreement or Developer Agreement, as appropriate (the “Purpose”). No other 14 license, express or implied, by estoppel or otherwise, to any intellectual property rights are granted herein. 15

THE SPECIFICATION IS PROVIDED “AS IS” WITH NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 16 WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, 17 NONINFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHTS, AND COMPLIANCE WITH 18 APPLICABLE LAWS. 19

NOTHING IN THE SPECIFICATION CREATES ANY WARRANTIES, EITHER EXPRESS OR IMPLIED, 20 REGARDING SUCH LAWS OR REGULATIONS. ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT 21 OF ANY INTELLECTUAL PROPERTY RIGHTS OR FOR NONCOMPLIANCE WITH LAWS, RELATING TO USE 22 OF THE SPECIFICATION IS EXPRESSLY DISCLAIMED. BY USE OF THE SPECIFICATION, EACH MEMBER 23 EXPRESSLY WAIVES ANY CLAIM AGAINST CCC LLC AND ITS MEMBERS RELATED TO USE OF THE 24 SPECIFICATION. 25

CCC LLC reserves the right to adopt any changes or alterations to the Specification as it deems necessary or 26 appropriate. 27

Each Member or Developer, as appropriate, (I) hereby acknowledges that its Implementing Products may be subject 28 to various regulatory controls under the laws and regulations of various jurisdictions worldwide. Such laws and 29 regulatory controls may govern, among other things, the combination, operation, use, implementation and distribution 30 of Implementing Products. Examples of such laws and regulatory controls include, but are not limited to, road safety 31 regulations, telecommunications regulations, technology transfer controls and health and safety regulations, (ii) is 32 solely responsible for the compliance by their Implementing Products with any such laws and regulations and for 33 obtaining any and all required authorizations, permits, or licenses for their Implementing Products related to such 34 regulations within the applicable jurisdictions, and (iii) acknowledges that nothing in the Specification provides any 35 information or assistance in connection with securing such compliance, authorizations or licenses. 36

FOR DEVELOPERS ONLY 37

Any use of the Specification not in compliance with the terms of this Legal Notice and the Developer Agreement is 38 prohibited and any such prohibited use may result in termination of the Developer Agreement and in other liability as 39 permitted by the Developer Agreement or by applicable law to the CCC LLC or any of its Members for patent, 40 copyright and/or trademark infringement. Developers are not permitted to make available or distribute this 41 Specification or any copies thereof to any third party. 42

FOR MEMBERS ONLY 43

Any use of the Specification not in compliance with the terms of this Legal Notice, the LLC Agreement, and the 44 Membership Agreement is prohibited and any such prohibited use may result in termination of the applicable 45 Membership Agreement and in other liability as permitted by the such Membership Agreement or by applicable law 46 to the CCC LLC or any of its Members for patent, copyright and/or trademark infringement. 47

This Specification may not be provided to any third party other than to Affiliates of Members (as defined in the LLC 48 Agreement) and subcontractors but only to the extent that such Affiliates and subcontractors have a need to know 49 for carrying out the Purpose and provided that such Affiliates and subcontractors accept confidentiality obligations 50 similar to those contained in the LLC Agreement. Each Member shall be responsible for the observance and proper 51 performance by such of its Affiliates and subcontractors of the terms and conditions of this Legal Notice and the LLC 52 Agreement. 53

Copyright © 2011-2019. CCC LLC. 54



CCC-RQ-005


Confidential

CONTENTS 1

LEGAL NOTICE .......................................................................................................................................... 2 2

CONTENTS ................................................................................................................................................... 3 3

TRADEMARKS ............................................................................................................................................ 5 4

MODAL VERBS TERMINOLOGY ........................................................................................................... 5 5

1 SCOPE ................................................................................................................................................... 6 6

2 REFERENCES ...................................................................................................................................... 7 7

2.1 NORMATIVE REFERENCES ............................................................................................................... 7 8

2.2 INFORMATIVE REFERENCES ............................................................................................................. 7 9

3 DEFINITIONS AND ABBREVIATIONS .......................................................................................... 8 10

3.1 DEFINITIONS ................................................................................................................................... 8 11

3.2 ABBREVIATIONS ............................................................................................................................. 8 12

4 BASE CERTIFICATION .................................................................................................................... 9 13

4.1 GENERAL REQUIREMENTS .............................................................................................................. 9 14

5 DRIVE CERTIFICATION ................................................................................................................ 12 15

5.1 REGIONAL APPLICABILITY ............................................................................................................ 12 16

5.2 ADAPTATION (DRIVE) ................................................................................................................... 12 17

5.3 REQUIREMENTS FOR ALL REGIONS ............................................................................................... 12 18

5.4 REGION SPECIFIC REQUIREMENTS ................................................................................................ 17 19

6 DRIVER WORKLOAD [NA, JP, GLOBAL] .................................................................................. 19 20

6.1 OCCLUSION METHOD [NA, JP, GLOBAL] ...................................................................................... 19 21

6.2 TASK IDENTIFICATION .................................................................................................................. 19 22

6.3 TASK DEFINITION ......................................................................................................................... 19 23

6.4 LISTS & TASKS ............................................................................................................................. 20 24

7 IMMERSIVE AND CLASSIC APPS [ALL REGIONS] ................................................................. 21 25

7.1 GENERAL PHONE CALL (CATEGORY 0X0002 0000) ...................................................................... 21 26

7.2 FIRST PARTY HOME SCREEN/LAUNCHER APPLICATIONS (CATEGORY 0X0001 0X0001)............... 21 27

8 TEST CONSIDERATIONS ............................................................................................................... 22 28

8.1 UI FLOW DIAGRAM....................................................................................................................... 22 29

8.2 TASK LIST ..................................................................................................................................... 22 30

8.3 EXAMPLE UI FLOW DIAGRAM: FIND NEAREST GAS STATION ...................................................... 23 31

8.4 RECORDING COLOR COMBINATIONS AND FONT DIMENSIONS ......................................................... 27 32

(NORMATIVE): COLOR CONTRAST ASSESSMENT ................................................... 28 33

A.1 UI ELEMENT COMPLIANCE ........................................................................................................... 28 34

A.2 COMPLEX ELEMENTS .................................................................................................................... 30 35

A.3 TYPOGRAPHIC REQUIREMENTS ..................................................................................................... 31 36

(INFORMATIVE): DESIGN RECOMMENDATIONS ...................................................... 34 37

B.1 DISCOURAGED VISUAL CONTENT [GLOBAL, NA, EU, JP] ............................................................ 34 38

B.2 LIST MANAGEMENT [GLOBAL, NA, EU, JP] ................................................................................. 34 39

B.3 MENU MANAGEMENT [GLOBAL, NA, EU, JP] .............................................................................. 34 40

B.4 DISCOURAGED MANUAL INTERACTIONS [GLOBAL, NA, EU, JP].................................................. 34 41

B.5 NOTIFICATIONS [GLOBAL, NA, EU, JP] ........................................................................................ 35 42

B.6 RESPONSIVENESS [GLOBAL, NA, EU, JP] ..................................................................................... 35 43

B.7 DYNAMIC INFORMATION DISPLAY MANAGEMENT [GLOBAL, JP] ................................................. 35 44

B.8 NAVIGATION RELATED RESTRICTIONS [GLOBAL, JP] ................................................................... 36 45

(INFORMATIVE): DEFINITIONS IN JAMA GUIDELINES [4] .................................... 37 46

(INFORMATIVE): AUTHORS AND CONTRIBUTORS .................................................. 38 47



CCC-RQ-005


Confidential

HISTORY 39 1

2



CCC-RQ-005


Confidential

TRADEMARKS 1

MirrorLink is a registered trademark of Car Connectivity Consortium LLC 2

Other names or abbreviations used in this document may be trademarks of their respective owners. 3

4

5

MODAL VERBS TERMINOLOGY 6

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", 7

"can" and "cannot" are to be interpreted as described similarly in clause 3.2 of the ETSI Drafting Rules 8

(Verbal forms for the expression of provisions) and in IETF RFC 2119 [1]. 9

NOTE: The present document uses lower case verbs in accordance with the ETSI Drafting Rules. 10

"must" and "must not" are not used. 11

https://portal.etsi.org/Services/editHelp!/Howtostart/ETSIDraftingRules.aspx



CCC-RQ-005


Confidential

1 SCOPE 1

This document is part of the MirrorLink specification, which specifies an interface for enabling remote user 2

interaction of a mobile device via another device. This specification is written having a car head-unit to 3

interact with the mobile device in mind, but it will similarly apply for other devices, which do provide a 4

colored display, audio input/output and user input mechanisms. 5

This document provides requirements for Applications to be used in a MirrorLink session while operating 6

while driving. Applications seeking Drive Certification shall comply with the requirements for the region that 7

the application is seeking Drive Certification for, as well as the Base Certification requirements. Drive 8

Certified applications can be displayed on a vehicle’s infotainment screen while the vehicle is driving. This 9

combines the requirements for North America, the European Union and Japan, which were originally in 10

separate documents, into a single document for ease of reference. Applications with Global certification are 11

certified for use in every region. For regional certification only the regional requirements are applicable. 12



CCC-RQ-005


Confidential

2 REFERENCES 1

2.1 Normative references 2

References are either specific (identified by date of publication and/or edition number or version number) or 3

non-specific. For specific references, only the cited version applies. For non-specific references, the latest 4

version of the referenced document (including any amendments) applies. 5

NOTE: While any hyperlinks included in this clause were valid at the time of publication, CCC 6

cannot guarantee their long-term validity. 7

The following referenced documents are necessary for the application of the present document. 8

[1] IETF RFC 2119: "Keys words for use in RFCs to Indicate Requirement Levels", March 1997. 9

http://www.ietf.org/rfc/rfc2119.txt. 10

[2] Alliance of Automobile Manufacturers: "Statement of Principles, Criteria, and Verification 11

Procedures on Driver Interactions with Advanced In-Vehicle Information and Communication 12

Systems" Version 2, June 26, 2006 (AG), http://bit.ly/15FkRdC. 13

[3] "European Statement of Principles on Human Machine Interface for In-Vehicle Information and 14

Communication Systems", December 5, 1998 (ESoP). 15

[4] Japan Automotive Manufacturers Association: "Guidelines for In-vehicle Display Systems – 16

Version 3.0", August 8, 2004 (JAMA). 17

[5] Car Connectivity Consortium CCC-TS-036: "MirrorLink – Handling of Application Certificates", 18

Version 1.1. 19

[6] Car Connectivity Consortium CCC-TS-038: "MirrorLink – Common API", Version 1.1.; 20

[7] Car Connectivity Consortium, "MirrorLink – Task Definition Examples", Version 0.1; CCC-TS-21

0XX 22

[8] International Standards Organization: "Occlusion Method to Assess Visual Demand Due to the 23

Use of In-Vehicle Systems", ISO 16673:2007. 24

[9] Web Contents Accessibility Guidelines (WCAG), 2.0, http://www.w3.org/TR/WCAG20/, W3C 25

Recommendation 11 December 2008. 26

[10] Department of Transportation: "Visual-Manual NHTSA Driver Distraction Guidelines for In-27

Vehicle Electronic Devices", Vol. 78, No. 81, April 2013 28

[11] Car Connectivity Consortium, Javadoc of the MirrorLink Common API, 29

https://causeway.carconnectivity.org/wg/DevWG/document/2119. 30

[12] Car Connectivity Consortium CCC-TS-87: "Consumer Experience Principles and Basic Features" 31

2.2 Informative references 32

References are either specific (identified by date of publication and/or edition number or version number) or 33

non-specific. For specific references, only the cited version applies. For non-specific references, the latest 34

version of the referenced document (including any amendments) applies. 35

NOTE: While any hyperlinks included in this clause were valid at the time of publication, CCC 36

cannot guarantee their long-term validity. 37

The following referenced documents are not necessary for the application of the present document but they 38

assist the user with regard to a particular subject area. 39

Not applicable. 40

http://www.ietf.org/rfc/rfc2119.txt

http://bit.ly/15FkRdC

http://www.w3.org/TR/WCAG20/

https://causeway.carconnectivity.org/wg/DevWG/document/2119



CCC-RQ-005


Confidential

3 DEFINITIONS AND ABBREVIATIONS 1

3.1 Definitions 2

For the purposes of the present document, the following terms and definitions apply: 3

Drive-Mode: Mode of a MirrorLink session when vehicle is driving. 4

Goal: A goal is defined as a system state sought by a driver. Examples include: Obtaining guidance to a 5

particular destination; greater magnification of a map display; determining the location of a point of 6

interest; and canceling route guidance. [2] 7

Landscape: A graphic or image representation where the lateral length is greater than (>) the vertical 8

length. 9

ML Base-Certification: Certification level where successful compliance to MirrorLink requirements 10

for applications promoting interoperability between devices has been proven. 11

ML Client: MirrorLink client software or device where user input and display is managed. 12

ML Drive-Certification: Certification level where successful compliance to MirrorLink requirements 13

for minimized driver distraction has been proven. 14

ML Server: MirrorLink server software or device where the application is executed. 15

Notifications: Pop-up messages, dialogue boxes and similar UI systems. 16

Park-Mode: Mode of a MirrorLink session when vehicle is not driving. 17

Portrait: A graphic or image representation where the vertical length is greater (>) than the lateral length. 18

Task: A task is defined as a sequence of control operations (i.e., a specific method) leading to a goal at 19

which the driver will normally persist until the goal is reached. An example is obtaining guidance by 20

entering a street address using the scrolling list method until route guidance is initiated. [2] 21

3.2 Abbreviations 22

For the purposes of the present document, the following abbreviations apply: 23

AG Alliance Guidelines [2] 24

AUT Application Under Test 25

ESoP European Statement of Principles [3] 26

EU European Union 27

HMI Human-Machine Interface 28

GUI Graphical User Interface 29

JAMA Japan Automotive Manufacturers Association [4] 30

ML MirrorLink 31

NA North America (Canada and USA) 32

RCD Reference Client Display 33

UI User Interface 34

UPnP Universal Plug and Play 35



CCC-RQ-005


Confidential

4 BASE CERTIFICATION 1

4.1 General Requirements 2

The MirrorLink App shall be displayed in landscape mode on the ML Server. Android MirrorLink apps 3

should only support landscape mode in the activity that responds to the MirrorLink launch intent. If the 4

activity supports portrait and landscape modes in that activity, the app shall shift to landscape mode while in 5

a MirrorLink session on launch and when brought to the foreground. 6

The MirrorLink App shall be usable with single-touch interactions (i.e. It shall not require the use of multi-7

touch events/gestures). The MirrorLink App should support the use of the rotary knob that is provided by 8

some MirrorLink clients. 9

NOTE: Support for rotary knob control might be required in future revisions of this document if 10

vehicles with exclusive rotary knob control become available in certain markets. 11

MirrorLink Apps shall not require the use of any other input events, including the mandatory hardware keys 12

of the underlying mobile OS/platform. For example, if a back button is needed to navigate by the app, it shall 13

be provided by the app. 14

The MirrorLink App can rely on the platform specific mechanisms to be terminated. It is not required to 15

implement an app-internal mechanism to terminate (e.g. an exit button). 16

The MirrorLink App shall update the Framebuffer Context Information using the MirrorLink API 17

Framebuffer Context Information function (Android 18

IContextManager.setFramebufferContextInformation) every time when 19

o the app category changes (e.g. switching from telephony to media) 20

o a MirrorLink session is established 21

The Established MirrorLink Connection Callback (Android 22

IConnectionListener.onMirrorLinkSessionChanged(boolean)) informs the app about 23

the MirrorLink connection status. Refer to [11] for documentation about the Android MirrorLink API. 24

4.1.1 Adaptation (Base) 25

The MirrorLink App may adapt its user interface based on the reported capabilities of the MirrorLink Client 26

and Server. Variations can be due to the presence of rotary-knob/steering-wheel controls, screen size of the 27

client, support for Voice Commands, connection status, localization options or other reasons. If the 28

MirrorLink App does adapt its user interface, all UI variations shall offer the same basic functionality. If the 29

MirrorLink App customizes its user interface based on the screen size of the MirrorLink Client, it shall 30

register for, and respond to, the MirrorLink API Display Configuration Callback (Android 31

IDisplayListener.onDisplayConfigurationChanged), as the available screen size may 32

change during runtime due to windowing and other actions by the MirrorLink Client. 33

If the MirrorLink App displays a custom UI when in a MirrorLink session, the MirrorLink App shall 34

register and respond to the Established MirrorLink Connection Callback (Android - 35

IConnectionListener.onMirrorLinkSessionChanged(boolean)). 36

4.1.2 Audio 37

The MirrorLink App shall update the Audio Context Information using the MirrorLink API Audio Context 38

Information function (Android IContextManager.setAudioContextInformation) with 39

audioContent set to TRUE every time one of the following events occurs: 40

- before starting to play back audio 41

- when a MirrorLink connection is established and audio is playing back 42

- when the audio category changes (e.g. from entertainment to navigation prompts) 43

The audio category shall be one of the following: 44



CCC-RQ-005


Confidential

- 0x00030000 – Entertainment audio; undefined length 1

- 0x00050000 – Short navigation related announcements; pre-defined length 2

- 0x00080000 – Short non-navigation related announcements; predefined length 3

- 0x00020000 – Telephony audio; un-defined length 4

- 0xF0000010 – Voice command interactions; predefined maximum 5

If the MirrorLink App provides multiple streams with different audio contexts (e.g. navigation and 6

entertainment) it shall provide and update the Audio Context information for both streams. 7

After stopping the audio stream, the MirrorLink App shall update the Audio Context Information with the 8

flag audioContent set to FALSE 100 to 200 ms after stopping the audio. 9

The MirrorLink App shall not provide key press audio feedback and swipe sounds to avoid interrupting the 10

audio management system of the MirrorLink Client. 11

The audio management of the ML Client may block the audio stream of the MirrorLink App. For example, 12

an incoming call on the MirrorLink Client will cause it to block audio sent by the app. It is the responsibility 13

of the app to handle the blocking event. The MirrorLink App shall wait 100 to 200 ms after stopping playback 14

before removing the audio category. 15

The MirrorLink App shall handle audio blocking notification by either stopping, pausing or muting playback 16

(see below). To receive the blocking events, set the paramenter handleBlocking to true when invoking 17

setAudioContextInformation. Without the registration, the MirrorLink Server does not know, 18

whether the application can handle the blocking and no notification will be sent. 19

On reception of the blocking notification, the MirrorLink App shall either: 20

- Pause audio source (shall not be used for announcements) OR 21

o Optional: Resume at paused position. 22

- Stop audio source (shall be used for Speech, restarting is optional) OR 23

o Optional: Restart at previous position (e.g. from the beginning of a track) 24

- Mute audio source & optionally unmute at current position (shall be used for Telephony) 25

o Optional: Unmute at current position 26

If the audio playback can be resumed or restarted, the MirrorLink App’s UI shall be updated to indicate that 27

playback can be resumed or restarted when block notification is received. 28

If audio playback is resumed by the user, the MirrorLink App shall check to see if the audio is still being 29

blocked and shall respond as above to a blocking notification. 30

On reception of the audio un-blocking callback the MirrorLink App should resume at paused position, restart 31

at previous position (e.g. from the beginning of a track) or unmute at current position 32

The MirrorLink App should not repeat audio announcements like navigation prompts, which are not relevant 33

anymore, unless requested by the user. 34

When an audio unblock event is received with no prior audio blocking event, the MirrorLink App may ignore 35

the event. 36

If a media application has the audio focus it shall consume all multimedia events. 37

The MirrorLink App may receive multimedia events from the MirrorLink API. When receiving multimedia 38

events, the behavior of the MirrorLink App should be consistent with the intention of the events as specified 39

below. 40

Event Expected Application Behavior

Multimedia_Play Start media playing

Multimedia_Pause Pause media playing

Multimedia_Stop Stop media playing



CCC-RQ-005


Confidential

Event Expected Application Behavior

Multimedia_Forward Forward

Multimedia_Rewind Rewind

Multimedia_Next Go to next track in playlist

Multimedia_Previous Go to previous track in playlist

Multimedia_Mute Mute the audio stream at source

Multimedia_Unmute Unmute the audio stream at source

Multimedia_Photo Take a photo

1



CCC-RQ-005


Confidential

5 DRIVE CERTIFICATION 1

Applications that seek MirrorLink drive certification shall comply with the requirements in this document as 2

well as the requirements for Base Certification. 3

The requirements of drive certification apply only when the system is reporting the vehicle to be in drive 4

mode. When the system is reporting park mode, then the requirements in this section do not apply. 5

The requirements in this section are derived from the Alliance of Automobile Manufacturers Guidelines (AG) 6

[2], the Visual-Manual NHTSA Driver Distraction Guidelines for In-Vehicle Electronic Devices, the 7

European Statement of Principles (ESoP) [3] and the Japan Automotive Manufacturers Association (JAMA) 8

guidelines [4]. The requirements are defined so that applications that meet the requirements in this document 9

are also compliant with the requirements of those foundational documents. 10

5.1 Regional Applicability 11

Application shall comply with the requirements for “All Regions” plus regional requirements outlined in 12

section 5.4 if applicable (see section 5.4 Region Specific Requirements). Certification is granted on a per-13

region basis, based on compliance with the requirements for each region. 14

EU drive certification shall be used for Default region drive certification. 15

5.2 Adaptation (Drive) 16

If the MirrorLink App adapts its user interface based on the reported capabilities of the MirrorLink Client 17

and Server (see 4.1.1 – Adaptation (Base)), all UI variations shall comply with the Drive requirements. 18

The MirrorLink App may adapt its user interface based on the drive mode status, as reported by the 19

MirrorLink Client via the MirrorLink API. The MirrorLink App may reduce functionality while in drive 20

mode. 21

If the MirrorLink App customizes its user interface based on the drive mode status of the MirrorLink Client, 22

it shall register for, and respond to, the MirrorLink API Drive Mode Callback (Android 23

IDeviceStatusListener.onDriveModeChange), as the drive status may change during runtime. 24

It shall also check the drive status when a MirrorLink connection is established (Android 25

IDeviceStatusManager.isInDriveMode). 26

5.2.1 Reference Client Display 27

To test compliance with the control, icon and text size requirements (below), the CCC uses the concept of 28

the Reference Client Display (RCD). The RCD is defined as: 29

• Resolution: 800 x 480 30

• Physical sizes: 13.33 cm x 8.00 cm (width x height) 31

• Distance to the eye of the driver: 90cm 32

Applications that do not tailor their UI based on the screen size of the MirrorLink client will be tested on the 33

RCD – if all requirements are met on the RCD, the MirrorLink App is deemed compliant. 34

Applications that DO tailor their UI based on the screen size of the MirrorLink client will be tested for 35

compliance on the RCD, and on larger screens. They will not be tested on smaller screens. 36

5.3 Requirements for All Regions 37

5.3.1 Restricted Content 38

The MirrorLink App shall not display any of the following content when in drive mode: 39

• Video or video based communication 40



CCC-RQ-005


Confidential

• Animated graphics 1

• Flashing content 2

• Automatic scrolling text 3

• Inertial scrolling of texts, lists or other items, after manual interaction 4

• UI elements that have visually entertaining character, e.g. flashing, automatically changing colors 5

or moving elements 6

Animations are allowed in the following cases: 7

• Splash screen animations 8

• Interstitial and screen transitions animations, <0.2 seconds long 9

• Progress/loading animations that cover less than 10% of the screen 10

• Control interaction animations (e.g. button presses) (but not scrolling) 11

• Active voice input animations that cover less than 10% of the screen (e.g. animations like the 12

Android active voice input animation, or the similar Siri active “wave” animation, etc.) 13

NOTE: Even in the above cases, flashing content and automatically scrolling text is not allowed. 14

5.3.2 Number of Hands 15

All tasks shall be capable of being completed with at least one hand on the steering wheel. MirrorLink Apps 16

shall not require the use of the mobile device for any functionality. Example: An application is not allowed 17

to require the user to hold the phone to their mouth to use as a microphone. 18

No manual interaction shall be needed to sustain a voice command interaction with the application. 19

5.3.3 General Requirements 20

• MirrorLink Applications running in the background shall not request foreground status or display pop-21

ups. Exceptions are 22

• Drive-related information is available (e.g. navigation prompts) 23

• Incoming phone calls 24

• Low battery notifications 25

• Warnings (e.g. Extreme weather, emergency warnings, etc.) 26

• MirrorLink Apps should not allow text entry via keyboard, using the touch screen or rotary knob control. 27

• If a MirrorLink App requires a user login, the app shall either provide a drive certified login mechanism 28

or display a message directing the user to login while not driving. The login may be outside of a 29

MirrorLink session. 30

• It is STRONGLY RECOMMENDED that applications deactivate the Android status bar (displaying time, 31

signal strength etc), and soft keys, and request to be displayed in immersive mode. 32

• Splash screens shall only occur during an application launch. Splash screens should not contain important 33

information for the driver except brand images/general marketing images. Splash screens may disappear 34

automatically. 35

• If an application supports text entry while driving, the application should either provide a custom 36

keyboard that supports rotary knob control, or the application should disable that text entry field. 37

• The MirrorLink App shall respond (button highlight, activity indicator, etc.) to all user input within at 38

most 2 seconds of the end of the user input. 39

• The MirrorLink App shall not request any permissions during drive mode. The MirrorLink App should 40

batch-request all needed permissions on first launch (in park mode or outside of a MirrorLink session). 41

5.3.4 Interactive Elements 42

Rectangular interactive elements (e.g. buttons) shall have a minimum edge length of 10 mm and a minimum 43

area of 200 mm2. 44

Non-rectangular elements shall cover at least 50% of an imaginary enclosing rectangle that has a minimum 45

edge length of 10mm and minimum area of 200 mm2. 46

The functional touch region shall be equal to, or larger than, the visual representation. 47



CCC-RQ-005


Confidential

5.3.5 Icons 1

Icons (any non-interactive informational symbol or graphic representation on the screen) used to 2

communicate status or indicate the function of a control shall be greater than or equal to 4.2 mm (or 5.25% 3

of the screen height or 26px on the Reference Client Display) tall and wide. 4

5

Figure 1: Sample Icon 6

5.3.6 Contrast 7

Text and UI elements need to be clearly visible also in situations when direct sunlight is hitting the display. 8

All text, UI elements and icons shall have a minimum contrast ratio of 7:1 (on a scale between 1:1 and 21:1) 9

between foreground and background, which is calculated using the contrast W3C contrast formula defined in 10

the W3C WCAG 2.0 [9]. A number of online tools are available to calculate the contrast ratio for RGB values 11

(no endorsement implied) 12

• http://www.msfw.com/Services/ContrastRatioCalculator 13

• http://juicystudio.com/services/luminositycontrastratio.php 14

• http://snook.ca/technical/colour_contrast/colour.html#fg=33FF33,bg=333333 15

Exceptions: Contrast requirements do not apply for 16

• Maps 17

• Inactive buttons (e.g. buttons that are greyed out). 18

• Brand logos and trademarks without any interactive functionality 19

• Text that is part of an image (e.g. a picture of a train station showing the name of the station). Text 20

that is overlaid over a picture shall comply with the requirements. 21

• Icons with text labels that comply with the supplemental text requirements, below 22

It is however STRONLGY RECOMMENDED that appropriate values are chosen to ensure that the map 23

contents and inactive buttons are clearly visible. 24

5.3.6.1 Icons for Accepting and Ending Calls 25

Buttons used for starting, accepting, declining or ending calls using widely recognized symbols as displayed 26

below only need a contrast ratio of 3:1. 27

28

Figure 2: Examples for Phone Symbols 29

5.3.6.2 Examples for Measuring Contrast 30

The following images give examples on how contrast is measured for different UI elements: 31

http://www.msfw.com/Services/ContrastRatioCalculator

http://juicystudio.com/services/luminositycontrastratio.php

http://snook.ca/technical/colour_contrast/colour.html#fg=33FF33,bg=333333



CCC-RQ-005


Confidential

1

Figure 3: Button Foreground, Button Area and Background 2

3

Figure 4: Slider Example 1 4

5

Figure 5: Slider Example 2 6

Figure 6: Switch Example 1 7

5.3.7 Keeping Partial User Input 8

Data input that requires more than a single or repeated user input shall not be removed, erased, or reset 9

automatically, including when the app is moved to the background. 10



CCC-RQ-005


Confidential

Example 1: If the user starts to enter a telephone number but discontinues, the phone number screen may 1

not be removed, and the incomplete number should not be erased unless it is removed or erased 2

by the user. 3

Example 2: If the user navigates down a menu structure from a home menu (e.g., selecting “Artist Menu” 4

→ (Artist Name) → “Albums” → …) and then decides to suspend the task, the screen should 5

not timeout and send the user to a different screen. The user’s progress shall be preserved. 6

5.3.8 Notification Dismissal 7

Notifications (dialogue boxes, pop-up messages and similar prompts) shall not be removed until dismissed 8

by the user. 9

Exception: Time-sensitive information (such as turning instructions) may be removed automatically if the 10

information is no longer relevant to the current activity but shall stay at least 10 seconds. 11

Example: A navigation instruction, such as “Turn right at the intersection” can be dismissed automatically 12

once the turn has been made or the intersection passed, as it is no longer relevant to the current activity. 13

5.3.9 Text Requirements 14

All text shall have a minimum height of at least 4.2 mm (for uppercase characters). 15

NOTE: The minimum height is measured on the MirrorLink Client not on the phone. 16

MirrorLink apps shall make sure that all text has the minimum height on the connected MirrorLink Client. 17

The following exceptions are defined for the minimum character height: 18

• Quasi static text: The definition of quasi-static text is information that has a limited number of states 19

where one or other states is always displayed and does not change frequently (ISO 15008). Notable 20

examples include AM/PM, mph, eta, and mpg. 21

• Text in symbols: Notable examples being brand logos and trademarks without interactive 22

functionality and album art. 23

• Text in maps: It is however recommended that appropriate text properties are chosen to ensure that 24

text on maps is clearly legible Text that is part of an image (e.g. a picture of a train station showing 25

the name of the station). Text that is overlaid over a picture shall comply with the requirements. 26

5.3.9.1 Supplemental Text and Redundant Information 27

If an application displays text that is purely supplemental to a main or primary text, the minimum character 28

height for this supplemental text shall be 3.1 mm. 29

Examples for supplemental text include 30

• Contact name (primary information) 31

o Contact phone number (supplemental information) 32

• Radio station name (primary information) 33

o Radio station frequency (supplemental information) 34

• Title of a song (primary information) 35

o Label “Title” to categorize this information (supplemental information) 36

• Title of an album (primary information) 37

o Label “Album” to categorize this information (supplemental information) 38

• Artist name (primary information) 39

o Label “Artist” to categorize this information (supplemental information) 40

• A button with an icon, e.g. an icon symbolizing a contact list (primary information) 41

The button label can be considered supplemental 42

Further, static labels on tabs or tabbed interfaces may use supplemental text. 43



CCC-RQ-005


Confidential

5.3.10 Fonts 1

The MirrorLink App shall use a pre-approved font to comply with typographic requirements OR the font 2

shall comply with the requirements listed in A.3. The list of pre-approved fonts can be found on the Developer 3

Portal Wiki, and includes the stock Android fonts. 4

Exception: Fonts in maps and images. It is however recommended to choose appropriate font properties to 5

ensure that the text is clearly legible. 6

5.4 Region Specific Requirements 7

5.4.1 Certification Type NORTH AMERICA Only 8

Driver workload verification applies, outlined in section 6. 9

The MirrorLink App shall not use any of the following content: 10

• Text longer than 30 words in single text block 11

• Visual advertisement 12

• Graphics and images 13

o Exception: Images attached to contacts e.g. in a phone book 14

o Cover Art 15

Images attached to contacts e.g. in a phone book and cover art images may be displayed during selection 16

tasks but shall be removed after the selection has been performed. 17

Maps shall be displayed in a two-dimensional format, with or without perspective, for the purpose of 18

providing navigational information or driving directions. 19

Maps shall not display informational detail not critical to navigation, such as photorealistic images, satellite 20

image and three-dimensional images. 21

The MirrorLink App shall not use text entry during the drive for the purpose of text-based messaging, other 22

communication, or internet browsing. 23

The MirrorLink App shall not display tutorials, disclaimer and legal information. These information items 24

should be displayed in park mode. 25

MirrorLink Applications may utilize acoustic based advertisement. MirrorLink Apps shall not use visual 26

advertisement. 27

5.4.2 Certification Type JAPAN Only 28

Driver workload verification applies, outlined in section 6. 29

Traffic information and other similar videos specially simplified for driving use may be displayed. 30

The following information, which is useful for driving and is quickly comprehensible, may be used even if it 31

is flashing but is not dazzling a driver: 32

• My vehicle position on the map. 33

• Traffic alert indication such as spot of traffic accident or traffic congestion road on the map. 34

Scrolling of any kind whether automatically or user controlled shall not be used. A notable use case is 35

incremental scrolling of email messages or lists. Discrete user interactions like paged swipes are allowed for 36

navigating through lists. 37

If the application displays a navigation map, the application shall meet the rules presented in Table 1 (find 38

“Minor road” and “Important road in the road network” definitions in Annex C Definitions in JAMA 39

Guidelines for more details) 40

O = permitted; X = not permitted 41

https://causeway.carconnectivity.org/wg/DevWG/wiki/pre-approved-font-list

https://causeway.carconnectivity.org/wg/DevWG/wiki/pre-approved-font-list



CCC-RQ-005


Confidential

Scale of map

Driving Condition

1:20,000 or less

detailed

More detailed than

1:20,000

1:5,000 or more

detailed

Important Roads in Road Network O O O

Driving on Minor Road X O (X when scrolling) O (X when scrolling)

Driving on Other Roads X X O (X when scrolling)

Table 1: Map Scaling Display Requirements 1

• The application shall not display addresses and telephone numbers as guidance information nor 2

information describing restaurants, hotels and other similar facilities. 3

• If the application displays a picture of facility, the application shall not display its indoor images 4

(inside a shop) or product images. 5

FM Literal Information is not supported by MirrorLink. Applications that use FM Literal Information shall 6

comply with the JAMA requirements. 7

The application shall not display more than 30 characters (e.g., kanji, kana, or alphanumeric characters) for 8

dynamic information. Notable examples of dynamic information are song titles, traffic congestion 9

information and weather information whose contents constantly change. See Annex Cfor the definitions from 10

the JAMA guidelines of “dynamic information”. 11

The following examples are provided for clarity: 12

• Numbers are considered 1 character (e.g., “120”) 13

• Units are considered 1 character (e.g., “km/h”) 14

5.4.3 Certification Type China Only 15

For MirrorLink Apps intended for use in the China region, only the following requirements are mandatory: 16

• 4 Base Certification 17

• 5.3.1 Restricted Content 18

• 5.3.2 Number of Hands 19

• 5.2 Adaptation (Drive) 20

All other drive requirements are STRONGLY RECOMMENDED. 21

5.4.4 Certification Type Global Only 22

Note that the certification type Global combines the requirements of all regions and thus is a very strict set 23

of requirements. For most applications following the regional requirements will be sufficient. 24

MirrorLink apps that seek Global certification shall comply with: ALL requirements for 25

• 5.3 – Requirements for All Regions 26

• 5.4.1 – Certification Type NORTH AMERICA Only 27

• 5.4.2 –Certification Type JAPAN Only 28

• Driver Workload – 6.1.2 – Occlusion Requirement [JP, Global] 29

Please note again that for most apps, one of the other certification types is sufficient. 30



CCC-RQ-005


Confidential

6 DRIVER WORKLOAD [NA, JP, GLOBAL] 1

At a high-level, interactions with an application shall be no more distracting than tuning the radio. To evaluate 2

an app, tasks are identified for testing, and the worst-case tasks are tested using volunteer test subjects. Testing 3

is via a blanking-display or occlusion goggles, and the time taken to perform the tasks is measured. 4

NOTE: All user interface variants of the app shall comply with this requirement. 5

NOTE: Driver workload verification is required for certification types Global, North America and 6

Japan. For EU and Default region drive certification, driver workload verification is not 7

required. 8

6.1 Occlusion Method [NA, JP, Global] 9

The occlusion method has participants complete application tasks while wearing occlusion goggles or using 10

a blanking display as described in [8]. Occlusion goggles are wearable glasses that cycle between transparent 11

(open) and opaque (closed) states automatically. The transparent duration is 1.5 seconds and the opaque 12

duration is 1 second. A blanking display operates by periodically clearing the display of the Client device (or 13

simulator) for equivalent time periods. 14

NOTE: The user is allowed to interact with the client’s controls (including touch screen controls) 15

even when the goggles are opaque or the screen is blank. 16

6.1.1 Occlusion Requirement [NA] 17

A subject matter expert evaluates the application and identifies tasks to be tested, 18

Success criterion: Each tested task has a mean occlusion goggle total open time (TOT) less than or equal to 19

(≤) 12 seconds for 21 of 24 participants. 20

21

A participant pool of 24 test participants with the following characteristics is required: 22

• Six test participants 18 -24 years 23

• Six test participants 25 -39 years 24

• Six test participants 40 -54 25

• Six test participants 55 years old or older 26

• Twelve men and twelve women and an equal balance of men and women in each of the age ranges 27

6.1.2 Occlusion Requirement [JP, Global] 28

A subject matter expert evaluates the application and identifies tasks to be tested, 29

Success criterion: For each application task, 100% of 10 participants whose ages are between 20 and 49 years 30

shall have a mean TOT that is less than or equal to 7.5 seconds. 31

6.2 Task Identification 32

Application developers will provide a list of the tasks that a user can perform while in drive mode. The test 33

lab, and their subject matter experts, will review the provided list, determine the specific tasks that will be 34

tested when assessing the application, and the task steps that will be performed during testing. 35

6.3 Task Definition 36

For the purposes of testing applications, a task is defined as the series of user actions needed to exercise an 37

application function. In general, a task’s starting point is from the highest-level interactive screen of the 38

application. The ending point is defined as the last user interaction required to exercise the application 39

function. 40



CCC-RQ-005


Confidential

Example 1: A music player application. One of the tasks for that application is finding and starting a specific 1

song. The task start would be at the home screen of the application (the “now playing screen,” 2

presumably). The endpoint will be marked when the user has started the song. 3

Example 2: Find Nearest Gas Station (see 8.3). One of the tasks is to find and select a gas station. The task 4

start would be from the Search Screen. The ending point is when the user selects a gas station 5

and confirms the selection. See [7] for additional information about tasks and examples. 6

6.4 Lists & Tasks 7

If a given list has a maximum list length limit, the list will be populated to the maximum length for the 8

purposes of that test. For example, if an application allows at most 5 entries in a list, then the list will be 9

populated to 5 entries. If the list is unlimited in length, the list will be populated with a pre-defined list of 10

1,000 items. 11



CCC-RQ-005


Confidential

7 IMMERSIVE AND CLASSIC APPS [ALL REGIONS] 1

Please note: This section applies only for telephony or home screen/launcher apps usually implemented 2

by phone vendors. Other apps can typically ignore this section. These requirements duplicate the 3

requirements given in CCC-TS-087 Consumer Experience Principles and Basic Features and are 4

provided here for reference. 5

7.1 General Phone Call (Category 0x0002 0000) 6

Many MirrorLink Clients rely on Bluetooth to offer telephony functionality. The MirrorLink Client will 7

typically show a native call user interface during phone calls over Bluetooth. The MirrorLink Server may 8

include an application that offers telephony functionality over MirrorLink. In this case the MirrorLink App 9

replaces the Bluetooth telephony mechanism and UI on the Client. In this case the following requirements 10

apply: 11

• The MirrorLink Phone Call application shall be CCC drive-certified for the current region. 12

• The MirrorLink Phone Call application shall respond accordingly to the Device_phone_call 13

and Device_phone_end key events. 14

• The MirrorLink Phone Call application shall support all Bluetooth HFP features (all versions) that 15

are provided by the MirrorLink Server; this may include features like merge call or conference calls. 16

• Only MirrorLink Phone Call applications fulfilling above requirements shall be CCC certified under 17

the application category 0x0002 0000 (General Phone Call) 18

7.2 First Party Home Screen/Launcher Applications (Category 19

0x0001 0x0001) 20

Launcher Applications are first-party applications provided by device makers that list other MirrorLink aware 21

applications and allow the user to launch them, similar to the native application list of the MirrorLink Client 22

The Launcher App may offer additional functionality. 23

• In Drive mode, the Launcher Application shall not make any non-drive certified applications 24

accessible (non-certified content will be blocked) 25

• Member-drive certified applications shall be only included, if the MirrorLink Client manufacturer 26

name matches the certifying entity. 27

• In Drive mode, the Launcher Application may consider MirrorLink Client AppCertFilter settings, 28

for the restricted/nonRestricted entries to filter apps, but only based on locale information. 29

• The Launcher Application shall make all applications accessible that are 30

• CCC base or drive certified for the current region 31

• Member certified with the certifying entity matching the Client manufacturer name 32

• All UI elements rendered by the Launcher App should be accessible with rotary knob controls 33

• The Launcher App shall maintain the certification status of certified applications that it launches. 34



CCC-RQ-005


Confidential

8 TEST CONSIDERATIONS 1

In order to aid testing, developers need to provide a completed User Interface Flow Diagram to allow for 2

assessment and evaluation of applications as part of their submission for certification. Additionally, 3

developers need to provide documentation on color combinations and font formatting. 4

8.1 UI Flow Diagram 5

The UI Flow Diagram describes the various screens displayed by the application while in Drive Mode, and 6

how the user reaches each screen. The purpose is to inform the test lab of what elements of the application 7

need to be evaluated for compliance with the requirements, and to ensure that the testing covers all essential 8

elements of the application. 9

The UI Flow Diagram includes the following, for each screen within the application: 10

- A diagram of the screen (screen shots preferred) 11

- A description of the screen 12

- A description of any voice commands supported 13

- A listing of the content categories 14

- Any FM Literal information displayed on the screen [JP/Global only] 15

- Description of variations of that screen (see below) 16

8.1.1 Screen Variation 17

Applications may change the layout of screens based on multiple factors: 18

• Available controls (rotary vs. touch vs. multitouch, voice commands, etc.) 19

• Client display size 20

• Language localization 21

• Day/night mode 22

• Others 23

Applications have to comply with the requirements for all variations. Developers shall tell the testers about 24

any variations of the screen in the UI Flow Diagram. 25

8.1.2 Client Display Size Variant Testing 26

Applications are tested at the Reference Client Display. If the app varies the layout of the screen based on the 27

client display size, compliance with the control/text size requirements will be checked at other screen sizes 28

as well. Developers need to submit information about how their application adapts to the ML Client’s display 29

capabilities in the UI Flow Diagram to aid in testing, including: 30

- Any threshold resolutions/aspect ratios that trigger a reorganization of the controls and text on a 31

screen. (e.g. if the resolution is 1024 x 768 or larger, the app organizes the screen differently than 32

for smaller resolutions) 33

- Any variations in UI flow based on the screen size. 34

Driver Workload verification testing will be performed at the reference-display minimum size. 35

8.2 Task List 36

The Task List describes each task performed by the user within the application while in Drive Mode is 37

provided in the Task List. A task should be “traceable” through the UI flow diagram. 38

Any variations in how tasks are performed based on client display size, available input schemes, or 39

localization scheme should be described for each task; or described within the relevant portions of the UI 40

Flow Diagram. 41

42



CCC-RQ-005


Confidential

8.3 Example UI Flow Diagram: Find Nearest Gas Station 1

This provides an example UI Flow Diagram and Task List for a simple “Find the Nearest Gas Station” 2

application. 3

8.3.1 UI Flow Diagram 4

The application has three screens (see Figure 7). The application is designed to provide the same interface, 5

whether or not the application is in park or drive mode. 6

7

8

Figure 7: UI Flow Diagram (Example) 9

8.3.1.1 Splash Screen 10

Welcome to

Find Nearest Gas Station

Figure 8: Splash Screen (Example) 11

Description (see Figure 8) 12

Shown on initial launch of the app. Shown for at most 1 second before transitioning to the Search Screen. 13

Pop-Up Messages 14

None 15

FM Literal Displays 16

None 17

Voice Command Support 18

• The application supports the use of a voice commands on this screen. The application responds to 19

the following commands: “Go to Nearest”, “Next”, “Previous”, “Refresh” and “Select”. 20

Categories 21

The application at launch reports the following categories: 22

• Application Category: General Navigation 23

• Video Category: Image 24

Variation 25

• Display Size 26

o None – Displays a static image that is scaled to the full available screen size. 27

• Control Scheme 28

Splash Screen Search Screen Route Screen



CCC-RQ-005


Confidential

o None 1

• Localization 2

o None. 3

• Orientation 4

o None 5

• Drive/Park Mode 6

o None 7

• Day/Night Mode 8

o Displays a darker-toned image if in night mode. 9

8.3.1.2 Search Screen 10

[Info Panel]

Big Ed’s Gas Farm

Distance: 3.2 miles

Unleaded: $2.99

Speak: Go to Nearest, Next, Previous, Select or Refresh

Refresh

Next

Previous

Select

Figure 9: Search Screen (Example) 11

Description (see Figure 9) 12

Consists of five major elements, an info panel and four buttons: 13

• Info Panel – Displays information about the gas station, distance, price, etc. 14

• Refresh – Search for the nearest gas stations 15

• Next – Proceed to the next nearest gas station 16

• Previous – Proceed to the previous nearest gas station. 17

• Select – Route to the selected gas station (proceed to the Route Screen) 18

Pop-Up Messages 19

None 20


None 22


• The application supports the use of a voice commands on this screen. The application responds to 24

the following commands: “Go to Nearest”, “Next”, “Previous”, “Refresh” and “Select”. 25

Categories 26

The following categories are reported on this screen: 27

• Application Category: General Navigation 28

• Video Category: User Interface 29

• Audio Category: Miscellaneous Content 30

Variations 31

• Display Size 32

o If the aspect ratio is narrow, the buttons are arrayed at the bottom of the screen. 33

▪ If the ML Client is over 1000 pixels tall, the buttons are scaled down in height to 34

consume less of the screen. 35

o If the aspect ratio is wide, the buttons are arrayed at the right of the screen 36

▪ If the ML Client is over 1000 pixels wide, the buttons are scaled down in width to 37




CCC-RQ-005


Confidential


o If the client supports touch screen, the search screen is shown as described. 2

o If the client has a rotary knob, the buttons are replaced with labels providing instructions 3

on how to use the shift knob: rotate clock-wise for next, counter-clock-wise for previous, 4

push to select, shift up to refresh. 5

• Localization 6

o Use different units and language based on system preference, but layout does not change. 7

• Orientation 8

o None 9


o None 11


o Displays a darker-toned background color if in night mode. 13

8.3.1.3 Route Screen 14

Map

- +

Cancel

Distance

2.7 km

ETA

3:27

Figure 10: Route Screen (Example) 15

Description (see above figure) 16

Consists of four major elements: a map, a cancel button, a distance display, and an estimated time of arrival 17

display. The Map includes a vehicle icon giving the current position, a callout of the destination (if visible), 18

and zoom-in and zoom out buttons. 19

NOTE: Panning in the map is not allowed. 20

Pop-Up Messages 21

None 22


None 24


- The application supports the use of a voice commands on this screen. The application responds to 26

the following command: “Cancel”. 27

Categories 28

The following categories are reported on this screen: 29

- Application Category: General Navigation 30

- Video Category: Vector Graphics 31

- Audio Category: Miscellaneous Content 32

Variations 33

• Display Size 34

o If the aspect ratio is narrow, the cancel buttons and distance/ETA labels are arrayed at the 35

bottom of the screen. 36

▪ If the ML Client is over 1000 pixels tall, the buttons are scaled down in height to 37


Big Ed’s

Gas

Farm



CCC-RQ-005


Confidential

o If the aspect ratio is wide, the cancel buttons and distance/ETA labels are arrayed at the 1

right of the screen 2

▪ If the ML Client is over 1000 pixels wide, the buttons are scaled down in width to 3



o If the client supports touch screen, the route screen is shown as described. 6

o If the client has a rotary knob, the cancel button is replaced with a label saying, “Push to 7

cancel”. In addition the zoom in/out buttons are replaced with a “twist to zoom” label. 8

• Localization 9

o Use different units and language based on system preference, but layout does not change. 10

• Orientation 11

o None 12


o None 14


o Displays a darker-toned background color in map area if in night mode. 16

8.3.2 Task List 17

There are four major tasks: 18

• Launch application. When the application is launched it initially shows a splash screen and then goes to 19

the search screen. The app automatically runs a “refresh” to search for nearest gas station. No user 20

interaction required. 21

• Search for a gas station. When the user first launches the application, the app searches for the nearest gas 22

stations based on the user’s current location, which returns a list of 10 gas stations. The user can re-run 23

the search at any time by pressing refresh (or pressing up on the rotary knob). They can then select from 24

the list of gas stations by selecting next or previous (or turning the rotary knob), which displays the 25

distance to the gas station and the price per gallon (if known). They press select (or push in on the rotary 26

knob) to select the current gas station. 27

• Route to the gas station. The app provides turn-by-turn navigation to the destination. The map supports 28

zoom but not pan, either by button or use of the shift knob. The UI updates automatically as the user 29

drives. 30

• Cancel a Route. While in the “route” task, the user can press the cancel button (or push the rotary knob) 31

to return to the “Search” screen. 32

8.3.3 Localization Support 33

This application support Japanese, Chinese and English. There are no major layout variations based on 34

language. 35

8.3.4 Testing the Example App 36

For this example application, the test lab would evaluate the Restricted Content and Accessibility 37

requirements for the Search and Route screens in the following configurations: 38

• Minimum reference display size with a touch screen interface 39

• Minimum reference display size with a rotary controller interface (if supported by the MirrorLink 40

App) 41

Spot checks would also be performed of the screens, on some set of the following combinations: 42

• With a large display (over 1200 pixels wide) with a wide aspect ratio 43

• With a large display (over 1000 pixels tall) with a narrow aspect ratio 44

• All of the above with in English, and in Japanese or Chinese. 45

• Day/Night mode. 46



CCC-RQ-005


Confidential

Driver Workload verification testing would be performed for the Search task in the preferred language for 1

that lab (English for US-based test lab, Japanese for a Japan-based test lab, etc.), on a minimum-size reference 2

display. 3

8.4 Recording color combinations and font dimensions 4

8.4.1 Application RGB Combination List 5

The developer needs to report color combinations in the Color List as identified in Appendix A (see Figure 6

11). Test labs will confirm the list and examine any unreported color combinations. 7

8

Figure 11: Application RGB Combination List (Example) 9

8.4.2 Application Font List 10

The developer needs to report all fonts used in the application using in the Font List. All pre-approved fonts 11

can be used. If non-pre-approved fonts are used, the font will have to be examined for compliance. 12

13

Figure 12: Font List (Example) 14



CCC-RQ-005


Confidential

(NORMATIVE): 1

COLOR CONTRAST ASSESSMENT 2

This appendix provides additional information on how to assess compliance with the color contrast 3

requirements. 4

A.1 UI Element Compliance 5

This section describes how to identify the background and foreground colors for evaluating compliance with 6

the requirements in section 5.3.6 Contrast. 7

A.1.1 Foreground Color Identification 8

The foreground color of a UI element’ is the elements intended color. (Shown in Figure 17 as “Text Color” 9

and “Symbol Color”.) 10

If the element contains a border, the border color, not the fill color, is considered as the foreground color. 11

A.1.2 Background Color Identification 12

The color that is most proximal to a foreground-related pixel is the background color (white in Figure 13). 13

A.1.3 Anti Aliasing 14

Anti-aliasing pixels are not considered as a foreground color or background color. 15

16

17

Figure 13: Foreground and Background Color Example 18

A.1.4 Background Gradients 19

If a color gradient is used in the background, foreground elements with the same color borders should be 20

grouped as shown in Figure 14 (i.e., Group 1 and Group 2). Within the confine of each Group Border, the 21



CCC-RQ-005


Confidential

background color with the most similar Brightness to the foreground color for that group is considered to be 1

the background color for that group (see section 5.3.6 Contrast). 2

Example In Figure 14, for the two groupings the background color that has the most similar Brightness 3

to the foreground color for that group is along the right of the group regions, and are labeled as 4

“Group 1 Background Color” and “Group 2 Background Color”. 5

6

Figure 14: Background Gradient Example 7

A.1.5 Foreground Gradients 8

If a color gradient is used in a foreground element, the color with the Brightness that is most similar to the 9

background Brightness is considered as the foreground color for that element (see section 5.3.6 Contrast). 10

Example In Figure 15, the left-most tip of the upper “A” is considered as the foreground color for the 11

upper “ABC”. For the lower “ABC”, the left-most portion of each letter is the foreground color 12

for that letter. 13



CCC-RQ-005


Confidential

1

Figure 15: Foreground Gradient Example. 2

A.2 Complex Elements 3

In instances when the foreground element has different colors contacting the same background color and/or 4

there are foreground elements within a foreground element (e.g., text overlaid on a button), each foreground 5

and background color will be examined for compliance with the requirements in section 5.3.6 Contrast. For 6

some UI elements, a single color may count as a foreground and a background color. 7

Example: Figure 16 is an example complex user interface element, which would not be compliant. The 8

following combinations would need to comply with the requirements in section 5.3.6 Contrast: 9

▪ Foreground Element 1A and Background 1A&B (not compliant) 10

▪ Foreground Element 1B and Background 1A&B. 11

▪ Foreground Element 2 and Background 2 12

▪ Foreground Element 3 and Background 3 13

By adding a black border, as shown in Figure 17, the UI element is made compliant, as the 14

border color would count as the foreground color. 15

Foreground color.

Foreground color. Foreground color. Foreground color.



CCC-RQ-005


Confidential

1

Figure 16: Complex UI Element (1) 2

Example: If Figure 16 were to be given a border (as shown in Figure 17), the border would act as the 3

foreground element reference color and only a single color combination will be reported by the 4

developer in the RGB combination list (i.e., color combination [RGB: “Foreground”, RGB: 5

“Background”]). 6

7

Figure 17: Complex UI Element (2) 8

A.3 Typographic Requirements 9

Note: All Android stock fonts are pre-approved. If one of those fonts is used, this section can be ignored. 10



CCC-RQ-005


Confidential

A.3.1 Font Requirements – Alphanumeric 1

All fonts used within the application shall either be a font pre-approved by the CCC, OR a font that complies 2

with the following requirements (see Figure 18 for measurement details). 3

A.3.2 Character Width to Height 4

The Width (W) to Height (H) ratio shall be between 0.5 and 1.0 inclusive. 5

0.5 ≤ W/H ≤ 1.0 6

A.3.3 Average Stroke to Height 7

The Stroke (S) to Height (H) ratio shall be between 0.08 and 0.2 inclusive. 8

0.08 ≤ S/H ≤ 0.2 9

A.3.4 Character Spacing 10

The spacing between adjacent characters with parallel lines (P) shall be greater or equal to SMIN. 11

P ≥ SMIN 12

A.3.5 Word Spacing 13

Word spacing (N) shall be equal or greater than one-half the width of lowercase letter “o” (Wo). 14

N ≥ 0.5 * Wo 15

A.3.6 Line Spacing 16

Line Spacing (T) shall be greater or equal to SMIN. 17

T ≥ SMIN 18

Where the dimensions are defined as: 19

• H = Height of the capital letter “H”. 20

• W = Width of the capital letter “W” (extra width added by capping is ignored). 21

• SMIN = Stroke Minimum of the thinnest diagonal stroke on a capital letter “A” 22

• SMAX = Stroke Maximum of the thickest diagonal stroke on a capital letter “A” 23

• S = Stroke average = 0.5 * (SMIN + SMAX) 24

• P = Minimum character distance for two adjacent capital “H”s (“HH”) 25

• Wo = Width of lower case letter “o” 26

• N = Word spacing, defined as the distance between two adjacent capital letter “V”s with a space in 27

between 28

• T = Line spacing, defined as the space between a lowercase letter “p” on the first line and a lowercase 29

letter “h” on the second line 30



CCC-RQ-005


Confidential

1 Figure 18: Character Dimensions 2

A.3.7 Korean Character Fonts 3

In case of Korean character fonts, the font dimensions shall be measured as given below and shown in Figure 4

19: 5

• H = Height of the letter "맴". 6

• W = Width of the capital letter "맴". 7

• SMIN = Stroke Minimum of the thinnest diagonal stroke on a capital letter "시". 8

• SMAX = Stroke Maximum of the thickest diagonal stroke on a capital letter "시". 9

• P = Minimum character distance for two adjacent capital "맴"s ("맴맴") 10

• Wo = Width of lower case letter “니” 11

• N = Word spacing, defined as the distance between two adjacent capital letter "시"s with a space in 12

between. 13

• T = Line spacing, defined as the space between a lowercase letter “니” on the first line and a 14

lowercase letter "하" on the second line. 15

16

Figure 19: Character Dimensions (Korean Font) 17



CCC-RQ-005


Confidential

(INFORMATIVE): 1

DESIGN RECOMMENDATIONS 2

This section offers design heuristics for minimizing driver workload. An application adhering to these 3

heuristics will be more likely to comply with the Driver Workload requirements in Section 6. Heuristics 4

presented below are suggestions, not requirements. 5

B.1 Discouraged Visual Content [Global, NA, EU, JP] 6

These heuristics are for visual content that should be avoided. 7

• Photo Viewer. A notable discouraged use case is an application that allows the driver to browse 8

through vacation photos. 9

• Excessive Text Content (exceeding 100 roman characters). Notable use cases are social media 10

content and web pages. Characters on interactive elements are not considered as part of this limit. 11

B.2 List Management [Global, NA, EU, JP] 12

These heuristics are for design of compliant list and table interfaces (see Figure 22). 13

• Limit visual and auditory list length 14

• Make list scrolling circular (effectively reduces list length by half) 15

• Sort lists in a systematic way (e.g., alphabetically, chronologically) 16

• Use a group header (e.g., "B", "M") 17

• Smart Scrollers (e.g., alphabetic scroller made of letters that jumps to the alphabetical section the 18

user is touching) 19

• Use a List Item Height min. of 17mm (see below) 20

21

Figure 20: List Item Height 22

B.3 Menu Management [Global, NA, EU, JP] 23

These heuristics are for design of compliant menu trees. 24

• Limit menu depth to < 3 levels (starting an application is not considered a task) 25

• Allow the user to go backtrack within the menu structure 26

B.4 Discouraged Manual Interactions [Global, NA, EU, JP] 27

These are heuristics for discouraged manual interactions. 28

• Applications should not allow text entry via keyboard, using the touch screen or rotary knob control. 29

• Avoid interactions that require extended physical contact with a control mechanism. A notable use 30

case is touching and holding an icon to rearrange its position on the home screen. 31

List

Item

Height



CCC-RQ-005


Confidential

• Avoid use of user-controlled scrolls (e.g., smartphone web-page scrolling). A page-by-page screen 1

switch style (“paged swiping”) is a preferred alternative as it is not as visually or manually intensive. 2

Text Formatting & Font Selection [Global, NA, EU, JP] 3

These heuristics are for formatting text and selecting fonts. 4

• Text flourishes tend to reduce legibility and are likely violate mandatory guidelines presented in the 5

accessibility chapter. These fonts would likely be rejected: 6

7

• Text should generally be conventionally oriented (e.g., English words should be presented left to 8

right). (Text on album is a notable exception to this suggestion.) 9

B.5 Notifications [Global, NA, EU, JP] 10

These heuristics are for use of notifications within the application: 11

• Notifications should be presented using the MirrorLink Client’s Notification System, if available. 12

See the Common API [6] for information on using the MirrorLink Client’s Notification System. 13

• Notifications should be used sparingly. 14

• Text in notifications should be limited. 15

• Applications should use graphical notification rather than text. 16

Example: If the application notifies the user of incoming emails, the application should use an “Incoming 17

Message Count” displayed on an icon, rather than bombarding the user with multiple “You have 18

received a message from…” notifications. 19

B.6 Responsiveness [Global, NA, EU, JP] 20

These heuristics are for responsiveness to user input: 21

• The application should respond within 250 ms of any user interaction, with either a visual or auditory 22

indication. 23

• If an activity is going to take more than 2 seconds to complete, a “Pending” indicator to the user 24

should be provided. 25

B.7 Dynamic Information Display Management [Global, JP] 26

When the application displays dynamic information, it is preferable that the following heuristics be used. 27

B.7.1 Optimization of Information Volume on a Map 28

If information on road congestion and traffic controls is simply superimposed on a map, the volume or density 29

of information displayed on the screen increases, resulting in taking too much time for the driver to read the 30

necessary information. Therefore, it is advisable to use a number of methods for optimizing the volume of 31

information on the screen. 32

Example 1: For indicating traffic congestion information, delete symbols and letters from the original map. 33

Example 2: Indicate only the traffic congestion and controls information relating to routes to the destination. 34

B.7.2 Display of Warning Information 35

The following description refers to the Vehicle Information and Communication System (VICS) as used in 36

Japan, however, this could be applied to other cases on displaying warning information. 37



CCC-RQ-005


Confidential

VICS supplies emergency information such as earthquake reporting to road vehicle drivers. Since this type 1

of information appears on the display monitor abruptly regardless of the driver's wishes, such information is 2

recommended to be easily and quickly comprehensible by drivers. 3

B.7.3 Display of Traveling Time 4

The following description is an example of VICS case, however, this could be applied to other cases on 5

displaying travelling time. 6

VICS presents traveling time information between links and between specific points, and such information 7

needs to be quickly comprehensible. Consequently, it is not recommended that, for example, drivers have to 8

add time taken to access each point to determine the total hours for reaching a destination. 9

B.8 Navigation Related Restrictions [Global, JP] 10

These heuristics are for reducing complex or time-consuming operations: 11

• The application should not allow the driver to change a navigation destination with 12

cursor/key/switch. 13

• The application should not allow the driver to select an area map (e.g., city region). 14

• The application should not allow the driver to search from addresses and facility names when 15

choosing a navigation destination. 16

• The application should not allow the driver to search for general information (addresses, phone 17

numbers, etc.) on restaurants, hotels and other facilities. 18

• The application should not allow the driver to select the display area for dynamic information such 19

as traffic information or weather information. 20



CCC-RQ-005


Confidential

(INFORMATIVE): 1

DEFINITIONS IN JAMA GUIDELINES [4] 2

(1) "Minor road" means a road less than 5.5m wide, excluding major trunk roads such as national highways, 3

major regional roads, and prefectural roads. 4

(2) "Important road in the road network" means a road that is less than 5.5m wide, linked to a non- minor 5

road, and deemed to be contributing to the smoothing of traffic flow. A non-minor road that has narrow 6

sections less than 5.5m wide is treated as an "important road" if the deletion of these sections from 7

display causes confusion to drivers. 8

(3) "Scroll" means the display of information in continuous motion, including the display of letters in 9

motion. 10

(4) "Scrolling" means the continuous moving of the displayed information by operating a key. 11

(5) "Dynamic information" means the types of information, including traffic congestion information, which 12

the display system receives from the outside through a telecommunication or broadcast network and 13

whose content constantly changes. For example, information on engine speed which constantly changes 14

is not dynamic information because it is not obtained from the outside. The names of information 15

suppliers (broadcasting corporations, etc.) titles of the programs, and time of display are not deemed to 16

be dynamic information even if they are obtained from the outside. 17

(6) "Task" means a series of operations performed by the driver to start the desired action of a display 18

system or to have the desired information displayed. 19

(7) "Occlusion method" means the technique of controlling shutter opening/closing time, often using a 20

liquid crystal shutter, in order to measure the total shutter opening time between the start and end of a 21

task. 22

(8) "Improved and simplified" operation means a display system operation whereby the screen image is 23

changed according to memorized conditions so as to prevent the driver from gazing at the screen 24

continuously. 25

(9) Definitions of major FM Literal Information are as follows: 26

• "Emergency information" refers to disaster reporting such as earthquake, tsunami, extreme weather, 27

serious accident, etc., provided by the broadcast station. 28

• "Traffic information" refers to traffic information such as traffic jam, road blocked, alternate route, 29

accident, tourist information, etc., provided by the broadcast station. 30

• “Program information” refers to information for certain programs that are selected and displayed 31

in parallel with the radio broadcast, and that are relatively easy to read, e.g. artist names and song 32

titles. Selection criteria are decided by each broadcasting station. 33

• "Weather information" refers to nationwide weather forecast, weekly weather forecast, earthquake 34

reporting, tsunami reporting, snow condition reporting, etc., provided by the broadcast station. 35



CCC-RQ-005


Confidential

(INFORMATIVE): 1

AUTHORS AND CONTRIBUTORS 2

The following people have contributed to the present document: 3

Editor: Jörg Brakensiek, E-Qualus (for Car Connectivity Consortium LLC) 4

Other contributors: Norichika Bando, Fujitsu Ten Limited. 5

Hideo Furukawa, Honda R&D Co., Ltd. 6

Daniel Glaser, General Motors 7

Kensuke Hanaoka, Toyota 8

Christian Heinrich, Daimler 9

Alice Gross, Carmeq/Volkswagen 10

Matthias Henning, Carmeq/Volkswagen 11

Hitoki Matsuda, Alpine 12

Kenji Nishimura, Panasonic 13

Ed Pichon, E-Qualus (for Car Connectivity Consortium LLC) 14

Mahfuzur Rahman, Samsung 15

Christopher Seubert, Carmeq/Volkswagen 16

Shoji Suzuki, Clarion Co., Ltd. 17

Makiko Tauchi, Denso 18



CCC-RQ-005


Confidential

HISTORY 1

Version Date Comment

1.0.25 4 March 2016 • Handling user logins required by applications [all regions].

• Requirements for Launcher Applications [all regions].

• Restriction for maximum text length [NA].

• Restriction for visual advertisement [NA].

• Restriction for graphics and images [NA].

• Restriction for additional details in maps [NA].

• Restriction for text entry [NA].

• Editorial changes.

1.0.26 8 March 2016 • Overlays over the app UI [all regions].

• Added section Client Display Size Variant Testing.

• Editorial changes to section Adaptation.

1.0.27 19 April 2016 • Added section General Phone Call.

• Clarification in section Maps [NA].

2.01 28 June 2016 • Simplification and re-work of wording and structure of the document while maintaining the same requirements

• Added base cert requirements

2.0.2 09 Aug • Fixed copy/paste errors.

• Rotary knob support set to recommended instead of mandatory.

• Amended max. text length NA.

• Added requirements for UI variations.

2.0.3 23 Aug 2016 • Rework based on comments from App CB.

2.0.4 30 Aug 2016 • Clarification for audio categories.

2.0.5 07 Feb 2017 • Set minimum text height for supplemental text to 3.1 mm.

• Static labels on tabs or tabbed interfaces may use supplemental text.

2.0.6 25 Apr 2017 • Clarified requirements for portrait/landscape mode support.

• Added requirement for resuming blocked audio.

• Alignment with test spec.

• Clarification for images in selection tasks.

2.0.7 3 October 2017 • Note that Immersive and Classic mode requirements are a duplicate of requirements in CCC-TS-087.

• Added exception for icon color-contrast with text labels.

• Added exceptions/clarifications to the restriction on animations.

2.0.8 23 May 2019 • Update document template.

• Added Definitions and Abbreviations section.

• Added section on Korean fonts.

• Added statement on Default region.

2

car connectivity consortium

Documents