• Home
• About SNAPI
• Related information
• What’s new
• Contact

Proposed revised version of EN 1332-4

Identification Card Systems - Man-Machine Interface - Part 4 : Coding of user requirements for people with special needs.

---

5 User interface data objects

5.1 General remarks

Information shall only be stored on a card with the consent of the user.

The interface device shall not retain the data elements or objects stored on the card.

If a separate updating process exists it may retain a copy of the preference information in a database. This database must conform to relevant data protection legislation.

For each data object, the following descriptors may be present :

Absence of a data object in the card indicates that no special requirements apply in the area concerned.

Subclause 5.4 uses private tags under an ISO/IEC JTC 1 SC17 registered Cardholder Included Requirements tag and defines data objects which may be present within an integrated circuit(s) card to indicate user interface preferences, but always recognising the terminal may not be able to provide the precise options requested.

The ISO registered tag for Cardholder Requirements Included Features is 7F22.

5.2 Principles

The following principles apply to the identification of user preference data objects within this standard:

5.3 Data object structure and byte settings

5.3.1 Data object structure

The following data object structures conforming to ISO/IEC 7816-4 are supported :

primitive data object

T

L

V

where T = Tag, L = Length, V = Value

constructed data object

T

L

T1

L1

V1

T2

L2

V2

...

Tn

Ln

Vn

T = Tag of constructed data object
L = Length of the string (template) T1 to Vn
T1 = Tag of a data object
L1 = Length of V1
V1 = Value

5.3.2 Structure of the tag

The tag consists of one or two bytes. The coding of these bytes shall be consistent with the basic encoding rules of ASN.1 as defined in ISO/IEC 8825. Table 1 defines the first byte.

Table 1 - Structure of the first byte of the tag

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
0	0	-	-	-	-	-	-	Not defined in this standard
0	1	-	-	-	-	-	-	Defined in this standard. Application class, unambiguous identification
1	0	-	-	-	-	-	-	Defined in this document and only to be used within a template
1	1	-	-	-	-	-	-	Private tags defined in this document
-	-	0	-	-	-	-	-	Primitive data object
-	-	1	-	-	-	-	-	Constructed data object
-	-	-	1	1	1	1	1	Tag number contained in the next byte - range 31..127
-	-	-	x	x	x	x	x	Tag number - range 0 - 30 Not all equal to 1

The coding of the second byte of the tag, when present, is :

b8 = 0

b7 to b1 = binary value of the tag number in the range 31..127.

Note. The first byte of tags of the primitive data objects defined in this document has the value 'DF'.

5.3.3 Structure of the length

All lengths are expressed in bytes.

The length consists of one or more bytes. The coding of these bytes shall be consistent with the basic encoding rules of ASN.1 as defined in ISO/IEC 8825 and shall be as defined in Table 2.

Table 2 - Coding of the length value

Range	Number of bytes	1st byte	2nd byte	3rd byte
0..127	1	binary value	none	none
0..255	2	‘81’	binary value	none
0..65,535	3	‘82’	binary ms byte	value ls byte

5.4 Coding of user requirements

5.4.1 Symbols

Purpose:	To indicate the preferred method of presentation of visual information, either via text, symbols, Braille or a combination of both.
Format:	1 byte binary.
Content:	The content of this field is in accordance with Table 3.

Table 3 - Content of the symbols data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Text required
-	-	-	-	-	-	1	-	Symbols required
-	-	-	-	-	1	-	-	Sign language required
-	-	-	-	1	-	-	-	Braille output required
x	x	x	x	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF50’.

Note. If Braille, b4, is set the default setting of tag DF6F is Grade 1, 6 dot Braille.

5.4.2 Character size

Purpose:	This data object enables the preferred size of any text information to be provided to the terminal device.
Format:	1 byte coded as two BCD digits.
Content:	The height of characters in millimetres. The width of characters shall be in proportion to the specified height for the particular font being displayed.

Remark - This data object is addressed through the use of tag number ‘DF51’.

5.4.3 Screen colour

Purpose:	To indicate preferred colours for the presentation of visual information.
Format:	1 byte binary.
Content:	The coding of the screen colour byte shall be in accordance with Table 4.

Table 4 - Content of the screen colours data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Use application default colours
-	-	-	-	x	x	x	-	Preferred colour for text according to the values specified below
-	x	x	x	-	-	-	-	Preferred background colour according to the values specified below
1	-	-	-	-	-	-	-	Plain background

Colour coding scheme for text and background:

000 : white
001 : red
010 : orange
011 : yellow
100 : green
101 : blue
110 : purple
111 : black

Note. Settings for text and background colours should be different.

Remark - This data object is addressed through the use of tag number ‘DF52’.

5.4.4 Colour avoidance

Purpose:	To indicate specific colours or combination of colours to be avoided when displaying visual information to the user.
Format:	1 byte binary.
Content:	The coding of the colour avoidance byte shall be in accordance with Table 5.

Table 5 - Content of the colour avoidance data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Avoid display of information in red
-	-	-	-	-	-	1	-	Avoid red/green colour combination
-	-	-	-	-	1	-	-	Avoid blue/yellow colour combination
-	-	-	-	1	-	-	-	Maximum contrast monochrome
x	x	x	x	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF53’.

5.4.5 Position of screen

Purpose:	To enable automatic height positioning of a screen to assist users in the reading of information.
Format:	1 byte coded as two BCD digits.
Content:	The value of this object denotes the desired height of the centre of a visual display in decimetres (multiples of 100mm) relative to the ground or floor level.

Remark - This data object is addressed through the use of tag number ‘DF54’.

5.4.6 Speech output

Purpose:	To indicate the preferred device for the speech related information.
Format:	1 byte binary.
Content:	The coding of the speech output byte shall be in accordance with Table 6.

Table 6 - Content of the speech output data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Loudspeaker output required
-	-	-	-	-	-	1	-	Headset output required
-	-	-	-	-	1	-	-	Hearing aid - magnetic inductive coupling required
x	x	x	x	x	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF55’.

5.4.7 Sound amplification

Purpose:	To enable sound amplification to be performed by the terminal for voice or other output information.
Format:	1 byte binary.
Content:	The coding of the sound amplification byte shall be in accordance with Table 7.

Table 7 - Content of the sound amplification data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	x	x	x	x	x	x	x	Offset amount in dBA from the terminal’s normal sound level
0	-	-	-	-	-	-	-	Positive value denoted in bits b1 to b7
1	-	-	-	-	-	-	-	Negative value denoted in bits b1 to b7

Remark - This data object is addressed through the use of tag number ‘DF56’.

5.4.8 High frequency amplification

Purpose:	To enable sound amplification to be performed by the terminal for high frequency voice or other output information.
Format:	1 byte binary.
Content:	The coding of the high frequency amplification byte shall be in accordance with Table 8.

Table 8 - Content of the high frequency amplification data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	x	x	x	x	x	x	x	Offset amount in dBA from the terminal’s normal sound level
0	-	-	-	-	-	-	-	Positive value denoted in bits b1 to b7
1	-	-	-	-	-	-	-	Negative value denoted in bits b1 to b7

Remark - This data object is addressed through the use of tag number ‘DF57’.

Note. The threshold between audible high and low frequency noise occurs at 1kHz.

5.4.9 Low frequency amplification

Purpose:	To enable sound amplification to be performed by the terminal for low frequency voice or other output information.
Format:	1 byte binary.
Content:	The coding of the low frequency amplification byte shall be in accordance with Table 9.

Table 9 - Content of the low frequency amplification data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	x	x	x	x	x	x	x	Offset amount in dBA from the terminal’s normal sound level
0	-	-	-	-	-	-	-	Positive value denoted in bits b1 to b7
1	-	-	-	-	-	-	-	Negative value denoted in bits b1 to b7

Remark - This data object is addressed through the use of tag number ‘DF58’.

Note. The threshold between audible high and low frequency noise occurs at 1kHz.

5.4.10 Input requirements

Purpose:	To indicate the preferred method for input of data into the terminal.
Format:	1 byte binary.
Content:	The coding of the input requirements bytes shall be in accordance with Table 10.

Table 10 - Content of the input requirements data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Voice input required
-	-	-	-	-	-	1	-	Keyboard input required
-	-	-	-	-	1	-	-	Connect special keyboard
-	-	-	-	1	-	-	-	Wireless
x	x	x	x	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF59’.

Note. For SMS input or output see table 13.

5.4.11 Keyboard characteristics

Purpose:	To indicate the preferred keyboard characteristics.
Format:	2 bytes binary.
Content:	The coding of the input requirements bytes shall be in accordance with Table 11 & 12.

Table 11: Content of the keyboard characteristics first data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	PIN pad top row denotes the digits 1,2,3
-	-	-	-	-	-	1	-	PIN pad top row denotes the digits 7,8,9
-	-	-	-	-	1	-	-	Alphanumeric layout (QWERTY)
-	-	-	-	1	-	-	-	Alphanumeric layout (AZERTY)
-	-	-	1	-	-	-	-	Alphanumeric layout (alphabetic)
x	x	x	-	-	-	-	-	Reserved for future use. All bits set to zero

Table 12 - Content of the keyboard input requirements second data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Repeat keys (eg auto-repeat when held down)
-	-	-	-	-	-	1	-	Chording input (eg for braille)
-	-	-	-	-	1	-	-	Sticky keys
-	-	-	-	1	-	-	-	Debounce
x	x	x	x	-	-	-	-	Reserved for future use. All bits set to zero

Remark: These data objects are addressed through the use of tag number 'DF5E'.

5.4.12 SMS communication

Purpose:	To indicate the SMS communication required.
Format:	1 byte binary.
Content:	The coding of the input requirements byte shall be in accordance with Table 13.

Table 13 - Content of the SMS communication data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	SMS input required
-	-	-	-	-	-	1	-	SMS output required
x	x	x	x	x	x	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF5F’.

5.4.13 Non-keyboard input requirements

Purpose:	To indicate the preferred method for input of data via a keyboard into the terminal.
Format:	1 byte binary.
Content:	The coding of the input requirements byte shall be in accordance with Table 14.

Table 14 - Content of the non-keyboard input requirements data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Voice input required - letter by letter
-	-	-	-	-	-	1	-	Voice input required - words
-	-	-	-	-	1	-	-	Voice input required - natural language
-	-	-	-	1	-	-	-	Feedback on voice input
-	-	-	1	-	-	-	-	Pointing device
x	x	x	-	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF6B’.

5.4.14 Touch screen

Purpose:	To indicate the preferred layout and icon characteristics for a touch screen input device.
Format:	1 byte binary.
Content:	The coding of the touch screen byte shall be in accordance with Table 15.

Table 15 - Content of the touch screen data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	0	1	Large button size required
-	-	-	-	-	-	1	0	Very large button size required
-	-	-	-	-	0	-	-	Finger entering touch-sensitive area
-	-	-	-	-	1	-	-	Finger exiting touch-sensitive area
x	x	x	x	x	-	-	-	Reserved for future use. All bits set to zero

Remark - In the above table, "button" refers to the target area to be touched on the screen to activate the input.

This data object is addressed through the use of tag number ‘DF5A’.

5.4.15 Position of input device

Purpose:	To enable automatic height positioning of a data input device to assist users in the entry of information.
Format:	1 byte coded as two BCD digits.
Content:	The value of this object denotes the desired height of the centre of the input device in decimetres (multiples of 100mm) from ground level.

Remarks - This data object is addressed through the use of tag number ‘DF5B’.

5.4.16 Time-outs

Purpose:	To indicate a requirement for additional time beyond the normal time-out to complete user input processes, thus reducing the potential for errors caused by device time-outs.
Format:	1 byte coded as two BCD digits.
Content:	The number of seconds of time required before a time-out or a series of time-outs shall come into force.

Remarks - This data object is addressed through the use of tag number ‘DF5C’.

5.4.17 Language

Purpose:	To indicate up to 4 preferred languages in order of user preference.
Format:	2 alphabetic characters per language.
Content:	This element is coded in accordance with ISO 639 tag number '5F 2D' as defined in EN ISO/IEC 7816-6.

Remarks - This data object is addressed through the use of tag number ‘DF 2D’.

5.4.18 Interface complexity level

Purpose:	To indicate the preferred level of complexity for dialogue or text presented to the user.
Format:	1 byte binary.
Content:	The coding of the interface complexity level byte shall be in accordance with Table 16.

Table 16 - Content of the interface complexity level data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	0	1	Simplified dialogue level required
-	-	-	-	-	-	1	0	Very simplified dialogue required
-	-	-	-	-	-	1	1	Reserved for future use
-	-	-	-	0	1	-	-	Simplified text required
-	-	-	-	1	0	-	-	Very simplified text required
-	-	-	-	1	1	-	-	Reserved for future use
-	-	0	1	-	-	-	-	Low text density required
-	-	1	0	-	-	-	-	Very low text density required
-	-	1	1	-	-	-	-	Reserved for future use
x	x	-	-	-	-	-	-	Reserved for future use. Both bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF5D’.

5.4.19 Screen reader

Purpose:	To indicate a requirement for specific reader software.
Format:	1 byte binary.
Content:	The coding of the selection of preferred screen reader byte shall be in accordance with Table 17.

Table 17 - Content of the screen reader data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Use default screen reader
-	-	-	-	-	-	1	-	Use other screen reader
-	-	-	-	-	1	-	-	Announce events on screen
-	-	-	-	1	-	-	-	Speech output of input characters as they are typed
-	-	-	1	-	-	-	-	Move mouse pointer to the active item
-	-	1	-	-	-	-	-	Start narrator minimised
x	x	-	-	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF61’.

5.4.20 Links

Purpose:	To indicate preferred audio output for links (as in HTML).
Format:	1 byte binary.
Content:	The coding of the links audio presentation byte shall be in accordance with Table 18.

Table 18 - Content of the links data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Speak links
-	-	-	-	-	-	1	-	Different voice
-	-	-	-	-	1	-	-	Sound effect
x	x	x	x	x	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF62’.

5.4.21 Speech rate

Purpose:	To indicate a requirement for preferred speech output rate.
Format:	1 byte coded as two BCD digits.
Content:	The number of decawords (multiples of ten words) per minute.

Remark - This data object is addressed through the use of tag number ‘DF63’.

5.4.22 Screen enhancement software

Purpose:	To indicate a requirement for specific screen enhancement software.
Format:	1 byte binary.
Content:	The coding of the selection of common settings for the screen enhancement software byte shall be in accordance with Table 19.

Table 19 - Content of the screen enhancement software data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Use default magnifying software
-	-	-	-	-	-	1	-	Use other magnifying software
-	-	-	-	-	1	-	-	Follow mouse cursor
-	-	-	-	1	-	-	-	Follow keyboard focus
-	-	-	1	-	-	-	-	Follow text editing
-	0	1	-	-	-	-	-	Magnification - low
-	1	0	-	-	-	-	-	Magnification - medium
-	1	1	-	-	-	-	-	Magnification - high
1	0	0	-	-	-	-	-	Magnification - very high
1	0	1	-	-	-	-	-	Magnification - maximum
1	1	-	-	-	-	-	-	Reserved for future use. All bits set to zero.

Remark - This data object is addressed through the use of tag number ‘DF64’.

5.4.23 Font

Purpose:	To indicate a requirement for specific type of fonts.
Format:	1 byte binary.
Content:	The coding of the preferred style of font byte shall be in accordance with Table 20.

Table 20 - Content of the font data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	No moving or flashing text
-	-	-	-	-	0	1	-	Use serif font
-	-	-	-	-	1	0	-	Use sans-serif font
-	-	-	-	-	1	1	-	Use mono-spaced font
x	x	x	x	x	-	-	-	Reserved for future use.

Remark - This data object is addressed through the use of tag number ‘DF65’.

5.4.24 Icons

Purpose:	To indicate preferred presentation for icons.
Format:	1 byte binary.
Content:	The coding of the icons style byte shall be in accordance with Table 21.

Table 21 - Content of the icons data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Enlarge icons
-	-	-	-	-	-	1	-	Increase contrast
-	-	-	-	-	1	-	-	Show text description
-	-	-	-	1	-	-	-	Use application default colours for symbols
-	x	x	x	-	-	-	-	Preferred colour for symbol according to the values specified below
x	-	-	-	-	-	-	-	Reserved for future use. All bits set to zero

Colour coding scheme for symbols.

000 : white
001 : red
010 : orange
011 : yellow
100 : green
101 : blue
110 : purple
111 : black

Note. The symbol colour setting should be different from the background colour set using tag DF52.

Remark - This data object is addressed through the use of tag number ‘DF66’.

5.4.25 Pointer buttons

Purpose:	To indicate preferred pointer button settings.
Format:	1 byte binary.
Content:	The coding of the settings for the pointer buttons byte shall be in accordance with Table 22.

Table 22 - Content of the pointer buttons data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Switch primary and secondary buttons
-	-	-	-	-	0	1	-	Double click speed - slow
-	-	-	-	-	1	0	-	Double click speed - normal
-	-	-	-	-	1	1	-	Double click speed - fast
-	-	-	-	1	-	-	-	Turn on ClickLock
x	x	x	x	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF67’.

5.4.26 Pointer characteristics

Purpose:	To indicate preferred pointer characteristics.
Format:	1 byte binary.
Content:	The coding of the settings for the pointer characteristics byte shall be in accordance with Table 23.

Table 23 - Content of the pointer characteristics data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	0	1	Pointer speed - slow
-	-	-	-	-	-	1	0	Pointer speed - normal
-	-	-	-	-	-	1	1	Pointer speed - fast
-	-	-	-	-	1	-	-	Snap to
-	-	-	-	1	-	-	-	Display pointer trails
-	-	-	1	-	-	-	-	Hide pointer while typing
-	-	1	-	-	-	-	-	Show location of pointer when designated key (CTRL) is pressed
-	1	-	-	-	-	-	-	Use keypad to move pointer
1	-	-	-	-	-	-	-	Large pointer

Remark - This data object is addressed through the use of tag number ‘DF68’.

5.4.27 On-screen keyboard

Purpose:	To indicate preferred presentation of an on-screen keyboard.
Format:	1 byte binary.
Content:	The coding of the settings for the presentation of an on-screen keyboard byte shall be in accordance with Table 24.

Table 24 - Content of the on-screen keyboard data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	0	1	Enhanced keyboard
-	-	-	-	-	-	1	0	Standard keyboard
-	-	-	-	0	1	-	-	Regular layout
-	-	-	-	1	0	-	-	Block layout
-	-	0	1	-	-	-	-	101 keys
-	-	1	0	-	-	-	-	102 keys
-	-	1	1	-	-	-	-	106 keys
x	x	-	-	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF69’.

5.4.28 Numeric, time and date presentation

Purpose:	To indicate preferred numeric delimiter for showing the decimal point and preferred format for time and date.
Format:	1 byte binary.
Content:	The coding of the settings for the numeric presentation byte shall be in accordance with Table 25.

Table 25 - Content of the numeric, time and date presentation data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Use comma for decimal point
-	-	-	-	-	-	1	-	Use period (fullstop) for decimal point
-	-	-	-	-	1	-	-	Use space for decimal point
-	-	-	-	1	-	-	-	Use 12 hour clock
-	-	-	1	-	-	-	-	Use 24 hour clock
-	-	1	-	-	-	-	-	Use day, month, year
-	1	-	-	-	-	-	-	Use month, day, year
1	-	-	-	-	-	-	-	Use year, month, day

Remark - This data object is addressed through the use of tag number ‘DF6A’.

5.4.29 ALT text

Purpose:	To indicate preferred presentation of ALT text (as in HTML).
Format:	1 byte binary.
Content:	The coding of the settings for the presentation of ALT text byte shall be in accordance with Table 26.

Table 26 - Content of the ALT text data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Speak the ALT text
x	x	x	x	x	x	x	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF6C’.

5.4.30 Speech output of non-alphanumeric characters

Purpose:	To indicate preferred speech output of non-alphanumeric characters.
Format:	1 byte binary.
Content:	The coding of the settings for the speech output byte shall be in accordance with Table 27.

Table 27 - Content of the speech output of non-alphanumeric characters data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Speak tabs
-	-	-	-	-	-	1	-	Speak punctuation
-	-	-	-	-	1	-	-	Speak buttons
x	x	x	x	x	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF6D’.

5.4.31 Braille display

Purpose:	To indicate settings for Braille display.
Format:	1 byte binary.
Content:	The coding of Braille display settings byte shall be in accordance with Table 28.
Note.	Tag DF50 should be present and the Braille bit, b4, set

Table 28 - Content of the braille display data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	0	1	Grade 1 braille
-	-	-	-	-	-	1	0	Grade 2 (contracted) braille
-	-	-	-	0	1	-	-	6 dot cell
-	-	-	-	1	0	-	-	8 dot cell
-	-	-	1	-	-	-	-	Mark highlighted text
-	-	1	-	-	-	-	-	Mark bold, italic, underlined and strikeout text
-	1	-	-	-	-	-	-	Mark coloured text
x	-	-	-	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF6F’.

5.4.32 Captions (subtitles)

Purpose:	To indicate type of captions.
Format:	1 byte binary.
Content:	The coding of the preferred settings for speed of captions, veiling (the level of transparency of the background to the text), and enhanced captions (eg include description of sound effects) byte shall be in accordance with Table 29.

Table 29 - Content of the captions data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	0	1	Maximum speed of presentation - slow
-	-	-	-	-	-	1	0	Maximum speed of presentation - normal
-	-	-	-	-	-	1	1	Maximum speed of presentation - fast
-	-	-	-	0	1	-	-	Veiling - low
-	-	-	-	1	0	-	-	Veiling - medium
-	-	-	-	1	1	-	-	Veiling - high
-	-	-	1	-	-	-	-	Enhanced captions
x	x	x	-	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF70’.

5.4.33 Audio description

Purpose:	To indicate preferred settings for audio description.
Format:	1 byte binary.
Content:	The coding of the settings for the level of description (eg how detailed is the description) byte shall be in accordance with Table 30.

Table 30 - Content of the audio description data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	0	1	Level of description - low
-	-	-	-	-	-	1	0	Level of description - normal
-	-	-	-	-	-	1	1	Level of description - high
x	x	x	x	x	x	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF71’.

5.4.34 Clean audio

Purpose:	To indicate preference for no background audio.
Format:	1 byte binary.
Content:	The coding of the settings for the clean audio byte shall be in accordance with Table 31.

Table 31 - Content of the clean audio data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	No background music or non-essential noise
x	x	x	x	x	x	x	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF72’.

5.4.35 Menu selection mode

Purpose:	To indicate preferred settings for menu selections.
Format:	1 byte binary.
Content:	The coding of the settings for Preferred modes (eg select by number rather than highlight) byte shall be in accordance with Table 32.

Table 32 - Content of the menu selection data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	0	1	Select by highlight
-	-	-	-	-	-	1	0	Select from numbered list
x	x	x	x	x	x	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF73’.

5.4.36 Scrolling mode

Purpose:	To indicate preferred settings for scrolling mode.
Format:	1 byte binary.
Content:	The coding of the preferred settings for scrolling mode (eg scrolling wheel, up/down, left/right buttons) and scrolling speed byte shall be in accordance with Table 33.

Table 33 - Content of the scrolling mode object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	0	1	Scrolling wheel
-	-	-	-	-	-	1	0	Up/down buttons
-	-	-	-	-	-	1	1	Left/right buttons
-	-	-	-	0	1	-	-	Speed - slow
-	-	-	-	1	0	-	-	Speed - normal
-	-	-	-	1	1	-	-	Speed - fast
x	x	x	x	-	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF74’.

5.4.37 Animation

Purpose:	To indicate the preferred settings for animation.
Format:	1 byte binary.
Content:	The coding of the preferred settings for the speed of animation byte shall be in accordance with Table 34.

Table 34 - Content of the animation object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Turn off animation
-	-	-	-	-	0	1	-	Animation speed - slow
-	-	-	-	-	1	0	-	Animation speed - normal
-	-	-	-	-	1	1	-	Animation speed - fast
x	x	x	x	x	-	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF76’.

5.4.38 Biometric characteristics

Purpose:	To indicate the preferred biometric.
Format:	2 byte binary.
Content:	For people with physical or cultural problems in using specific biometric systems. The coding of the biometric characteristcs byte shall be in accordance with Tables 35 and 36.

Table 35 - Content of the biometric characteristics first data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Use PIN instead of biometric characteristics
-	-	-	-	-	-	1	-	Use biometric characteristic, not a PIN
-	-	-	-	-	1	-	-	Cannot use iris recognition
-	-	-	-	1	-	-	-	Cannot use left eye iris
-	-	-	1	-	-	-	-	Cannot use right eye iris
-	-	1	-	-	-	-	-	Cannot use fingerprint
-	1	-	-	-	-	-	-	Restricted fingers available for fingerprints
x	-	-	-	-	-	-	-	Reserved for future use. All bits set to zero

Table 36 - Content of the biometric characteristics second data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	Cannot use facial recognition
-	-	-	-	-	-	1	-	Allow more time to use the biometric
x	x	x	x	x	x	-	-	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF77’.

5.4.39 Visible output of audible prompts

Purpose:	To indicate the preferred settings for the visual signal generated to indicate an audible prompt.
Format:	1 byte binary.
Content:	The coding of the preferred settings for the visible output of audible prompts byte shall be in accordance with Table 37.

Table 37: Content of the visible output of audible prompts data object

b8	b7	b6	b5	b4	b3	b2	b1	Meaning
-	-	-	-	-	-	-	1	No visual signal
-	-	-	-	-	-	1	-	Flash entire screen
-	-	-	-	-	1	-	-	Flash active window
-	-	-	-	1	-	-	-	Flash title bar of active window
-	x	x	x	-	-	-	-	Colour settings for the visible signal when a full screen text mode application generates a sound
x	-	-	-	-	-	-	-	Reserved for future use. All bits set to zero

Colour coding scheme for text and background:

000 : white
001 : red
010 : orange
011 : yellow
100 : green
101 : blue
110 : purple
111 : black

Remark : This data object is addressed through the use of tag number 'DF6E'.

5.4.40 Duration of a visible signal indicating audible output

Purpose:	To indicate the duration of the visual signal in seconds when a full screen text mode application generates a sound.
Format:	1 byte coded as two BCD digits.
Content:	The value is the duration of the visible signal specified as a number of tenths of a second.

Remark : This data object is addressed through the use of tag number 'DF7A'.

5.4.41 Pre-stored message

Purpose:	To request a specific pre-stored message to be displayed on an assistant's screen.
Format:	1 byte binary.
Content:	The messages shall be in accordance with Table 38.

Table 38 - Pre-stored message

Value	Meaning
0 1	Please talk slowly and clearly
x x	Reserved for future use. All bits set to zero

Remark - This data object is addressed through the use of tag number ‘DF78’.

5.4.42 Variable message

Purpose:	To request that a message stored on the card is displayed on an assistant's screen.
Format:	n bytes ASCII alphanumeric characters.
Content:	The message to be displayed.

Remark - This data object is addressed through the use of tag number ‘DF79’.

5.4.43 Application specific requirements

Purpose:	To indicate the set of user requirements which are specific to the application being implemented.
Format:	n bytes binary (n is dependent on the number of requirements specified).
Content:	A constructed data object comprising the individual interface requirements

Remarks - User requirements applicable for a given ICC application shall be encapsulated in the template of the data object with tag 7F22, which shall be retrievable using the GET DATA command after selection of the respective application.

Previous page

Contents page

Next page

• Join email list
• Privacy policy
• Links