HOME   Cart(0)   Quotation   About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189759 (19 Oct 2025)

GB/T 36443-2018 English PDF

US$1024.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 36443-2018: Information technology -- Framework for specifying a common access profile (CAP) of needs and capabilities of users, systems and their environments
Status: Valid
Standard IDContents [version]USDSTEP2[PDF] delivered inStandard Title (Description)StatusPDF
GB/T 36443-2018English1024 Add to Cart 5 days [Need to translate] Information technology -- Framework for specifying a common access profile (CAP) of needs and capabilities of users, systems and their environments Valid GB/T 36443-2018

PDF similar to GB/T 36443-2018


Standard similar to GB/T 36443-2018

GB/T 44130.1   GB/T 38555   GB/T 39105   GB/T 45693   GB/T 36441   

Basic data

Standard ID GB/T 36443-2018 (GB/T36443-2018)
Description (Translated English) Information technology -- Framework for specifying a common access profile (CAP) of needs and capabilities of users, systems and their environments
Sector / Industry National Standard (Recommended)
Classification of Chinese Standard L73
Classification of International Standard 35.240.20
Word Count Estimation 54,520
Date of Issue 2018-06-07
Date of Implementation 2019-01-01
Issuing agency(ies) State Administration for Market Regulation, China National Standardization Administration

GB/T 36443-2018: Information technology -- Framework for specifying a common access profile (CAP) of needs and capabilities of users, systems and their environments


---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Information technology--Framework for specifying a common access profile (CAP) of needs and capabilities of users, systems and their environments ICS 35.240.20 L73 National Standards of People's Republic of China Information technology users, systems and their environment needs and Capability Public Access Profile (CAP) Framework (ISO /IEC 24756.2009, IDT) Published on.2018-06-07 2019-01-01 implementation State market supervision and administration China National Standardization Administration issued

Content

Foreword III Introduction IV 1 Scope 1 2 Compliance 1 3 Normative references 1 4 Terms and Definitions 1 5 Accessibility Model 2 6 Format for identifying access potential 4 6.1 Introduction to Public Access Profiles 4 6.2 Public Access Profile 5 6.3 Describe the overall CAP 6 6.4 Description of interactive components 6 6.5 Describe IC component features 7 6.6 Specific Mode Information 9 6.7 Specific Capability Information 12 6.8 Specific Processing Information 16 6.9 Extending CAP 18 7 CAPs operation 19 7.1 CAP operator 19 7.2 Unary operation 19 7.2.1 Requirements (SHALL) 19 7.2.2 Optional (MAY) 19 7.2.3 Exclusion (NOT) 20 7.3 binary operator 20 7.3.1 Include (AND) 20 7.3.2 Alternative (OR) 20 7.3.3 Mutual exclusion (XOR) 21 8 Using CAP 21 8.1 Introduction to CAP Usage 21 8.2 Identifying obstacles using CAP 21 8.3 Using CAP to Select AT 22 8.4 Management of AT 23 with CAP 8.4.1 Development Basic Configuration 23 8.4.2 Development of alternative configurations 23 8.4.3 Reconfiguring the Current Configuration 23 Appendix A (informative) CAP construction example 25 A.1 Introduction 25 A.2 User 25 A.2.1 User CAP Introduction 25 A.2.2 Description of the sample user Johann 26 A.2.3 Notes on hearing 27 A.2.4 Johann's CAP 28 A.3 System 35 A.3.1 Introduction to System CAP 35 A.3.2 System CAP method 35 A.3.3 Describe an example system 36 A.3.4 Example System CAP 36 A.4 More information 49 Reference 50

Foreword

This standard was drafted in accordance with the rules given in GB/T 1.1-2009. This standard uses the translation method equivalent to ISO /IEC 24756.2009 "Information technology users, systems and their environment needs and capabilities Public Access Profile (CAP) Framework. The documents of our country that have a consistent correspondence with the international documents referenced in this standard are as follows. ---GB/T 4880.3-2009 Language name code Part 3. 3-letter code for all languages (ISO 639-3.2007, IDT) Please note that some of the contents of this document may involve patents. The issuing organization of this document is not responsible for identifying these patents. This standard is proposed and managed by the National Information Technology Standardization Technical Committee (SAC/TC28). This standard was drafted. China Electronics Technology Standardization Institute, China Disabled Persons Federation Information Center, Chengdu Information Processing Product Inspection Testing Center, Chengdu Millennium Standardization Co., Ltd., Sichuan Soft Testing Technology Testing Center Co., Ltd. The main drafters of this standard. Cui Huiping, Zhou Qin, Che Rongjun, Zhou Pengcheng, Shen He, Zhao Jinghua, Xu Yang, Wang Jing, Fan Xing.

Introduction

Users in different environments and on different systems may experience temporary or persistent inaccessibility. Potential user needs assessment system for the system Accessibility in the intended use environment. Due to environmental barriers or design flaws, it can lead to inaccessibility, and these users can assist Technology (ATs) to guarantee the necessary level of accessibility. Currently, there is no public framework for describing accessibility needs and capabilities. This promotes Enable each potential user to develop their own assessment methods and use this to investigate and evaluate different systems and assistive technologies. Due to the lack of one Existing methods may lack relevant information on different systems and assistive technology capabilities, resulting in inefficiency, confusion, obstruction, and user satisfaction Generally lower. Various difficulties may arise when attempting to develop suitable assistive technologies to improve accessibility. Accessibility questions encountered by potential users The problem limits their access to the information they need to identify possible assistive technologies to help improve accessibility. Lack of assistance Technical experience may also affect information technology support staff who are trying to help potential users. Accessibility requirements span all systems that potential users may access. Letter on accessibility issues and solutions for individual users The ability to collect information across systems and environments is essential. This standard introduces an accessibility model as an understanding The basis for accessing users and systems in different environments. Accessibility is multi-dimensional; it exists at multiple levels. The model shows that users and systems must share communication capabilities. Provided by this standard a framework for specifying the public access capabilities of interactive systems, users, and their environment, which is necessary to make accessibility possible need. The CAP is specified as a top-down approach that provides scalability that adds step-by-step detail. Information technology users, systems and their environment needs and Capability Public Access Profile (CAP) Framework

1 Scope

This standard specifies a requirement and capability for specifying users, computing systems, and their environments, including access supported by assistive technologies. The public access profile framework provides the foundation for identifying and handling cross-platform accessibility issues in a standard way. This standard is intended to assess the accessibility of existing systems for specific users in a particular environment.

2 Compliance

Specifications for systems and/or system components, including assistive technologies, are in compliance with this standard if they comply with Chapters 6 and 7.

3 Normative references

The following documents are indispensable for the application of this document. For dated references, only dated versions apply to this article. Pieces. For undated references, the latest edition (including all amendments) applies to this document. ISO 639-3 Language Name Code Part 3. 3-letter code for languages (Codesfortherepresentationofnames oflanguages-Part 3. Alpha-3codeforcomprehensivecoverageoflanguages) ISO 15924 information and documentation script name representation code (Informationanddocumentation-Codesforthe Representationofnamesofscripts) ISO 80000 quantity and unit (Quantitiesandunits)

4 Terms and definitions

The following terms and definitions apply to this document. 4.1 Accessibility For users, the availability of products, services, environments or tools for the widest range of capabilities. Note 1. The concept of accessibility is aimed at a full range of user capabilities and is not limited to users who are formally identified as having a disability. Note 2. The concept of usability-oriented accessibility is designed to achieve the highest possible level of effectiveness, efficiency and efficiency in the context of specific use contexts. Satisfaction, with a special focus on a fully capable user base. 4.2 Usability usability The extent to which a product is used by a particular user in a particular application scenario to achieve a particular utility, efficiency, and satisfaction goal. 4.3 Assistive technology assistivetechnology; AT Hardware or software added to or added to the system to increase accessibility for a single individual. Examples. Blind displays, screen readers, screen magnification software, and eye tracking devices are all assistive technologies. 4.4 Application scenario contextofuse Users, tasks, equipment (hardware, software, and materials) and physical and social environments used by the product. 4.5 Handicap Anything that can hinder the accessibility of the user and system interaction.

5 accessibility model

Accessibility includes the interactions available between the user and the system. Interaction occurs in systems, users, users' tasks, and environments. Use week territory. Figure 1 illustrates the environment in which interaction occurs. A barrier is anything that can hinder the accessibility of users and system interactions. The source of the barrier may be one or more of a system, a user, an interaction, and/or an environment. The model is "disclaimer" because it resolves the interaction Obstacles are important compared to the source of imputational barriers. Figure 1 User and system interaction model Figure 1 uses a pipeline to represent the flow of interaction between the user and the system, with valves representing different levels of barriers in the interaction. User and system The shadow stream between them represents the possibility of multiple communications occurring in both directions. A fully open valve indicates barrier-free interaction. Fully closed valve The door indicates that the interaction is completely blocked. Any other setting of the valve indicates that the interaction is partially blocked. Although the use of generic design-specific components reduces the barriers to interaction, it does not eliminate the barriers to interaction in all situations. Assistive technology Surgery is one way to reduce these obstacles. Although users of assistive technology may not have differences in physical function, some components in the interaction are still Will hinder them. If someone attends a lecture, the speaker uses a language that the listener does not understand. Since most people know that With less than one language, the listener may eventually know the language of the speech, but at this point the interaction between the speaker and the listener is not Knowing the language used by another person is a hindrance. The listener could not understand the details of the speech without using the translator. In the In the scene, the translator is an auxiliary technology. Computer-related assistive technologies can be implemented by replacing input devices (such as trackballs, left-handed mice, blow-up systems), alternatives Output devices (such as sound, braille displays), accessible software (such as screen control software), and "universal design" (ie, barrier-free design). Due to Intertwined, an accessible computing experience is achieved by reducing these barriers. The assistive technology can be modeled in a way that opens the valve between the user and the system, as shown in Figure 2. Figure 2 Auxiliary technology in user interaction with the system Accessibility depends on the compatible interface that the user interacts with the system. Figure 3 contains an assistive technique that allows for two Do conversion between incompatible interfaces. In order to assess the current and future planned accessibility, a standard method description is required across all System and user user-system accessibility and user-assisted technology-system accessibility. Figure 3 Interaction between components The goal of accessibility is to make the system accessible to users. However, different scenarios require different system packages. When the user’s goal is When interacting with a specific application package, the user can select an operating system, computer, peripherals, and other assistive technologies to make the application The order is the easiest to access. Accessible when the user's goal is to interact with an application package that is part of an existing hard/software system Sexual goals may require assistive technology. Regardless of where the system boundary is located, the model shown in Figure 3 summarizes all situations. In this model, assistive technology can be considered Anything added to the underlying system that makes it accessible to users. Can be used as an assistive technology for a wide range of objects, including dedicated assistance Technology, universal remote controllers, intelligent agents, and components specifically tailored to meet the needs of specific users. Multiple assistive technologies It can be used in order and/or in parallel to support access. Figure 4 illustrates the path between the user and its final destination, the application (A1, A2, A3) that the user wishes to use. Between components Multiple communications can be made in each direction of the cable. The application being used must be user accessible. For this reason, the software can be used as a machine Software-based assistive technology (SAT), when used as part of a system or software added to a system to increase the accessibility of individual users, Software may be needed. Examples of software-based assistive technologies include added or built-in screen readers. Figure 4 Accessibility components Every level between the user and the application (operating system, hardware, peripherals, assistive technology, and environment), although traditionally not considered It is an assistive technology, but it can achieve the same effect as the assistive technology to increase or decrease the access. Actions selected for use with the application The system (OS1, OS2) can limit or enhance user access to the application. When it does not support some form of user and application Access is restricted when interacting. When it supports the interaction between the user and the application in one form to another, Enhanced access. The computer (C) with which the operating system interacts further limits the user experience. Users are also available for peripherals of computers The ability to prepare (P1, P2, P3) is limited. As shown by the dashed box in the figure, the user may have a combination of applications, operating systems, computers, and peripherals as a single system. When considering accessibility, these components can be modeled separately or as a single system. Assistive technology (AT1, AT2) can be used to convert peripheral interactions for greater accessibility. Environmental conditions (E) can enter One step reduces the accessibility of specific interactions. For the user, after experiencing the accessibility of each component, it is possible to perceive the accessibility of the entire system. For evaluating users Accessibility, it is necessary to specify the accessibility of the entire system.

6 Identify the format of the access potential

6.1 Introduction to public access profiles Communication is transmitted (through the system, the user, or through the aid of the channel and the environment) to the intended recipient (system, user or assistive technology) Technology). This includes the flow of information from the system to the user and from the user to the system. The characteristics of these streams are not necessarily consistent (eg, the system can output The voice that the user can hear, however, if the user has no ability to speak, then choose to use the keyboard to enter information into the system). When the senses can receive And when the message from the transmission is understood, the access exists. In this standard, systems, users, assistive technologies, environments, and channels will be considered as interactive components. (ICs). Personal communication can be modeled by the sensory, channel, and transmitter that complete the communication. Interaction involves two-way transmission between ICs in interaction Multiple communication sets that are lost. The access framework models a collection of all transmitters, channels, and receivers, including possible interactions between special users and special systems. Used to assess the accessibility of a particular user to a system within a given environment. The access framework consists of multiple collections. {Interaction, each interaction consists of one or more {receiver, channel, transmitter} collection} Instead of dealing with each interaction, modeling the potential intersection based on an understanding of the compatibility of the transmitter, receiver, and channel characteristics of the ICs Mutual collection is possible. 6.2 Public access profile A complete public access profile (CAPO) is made up of each of the different interaction components (ICs) of CAPIC, including the following. Users (CAPUSE), System (CAPSYS), Assistive Technology (CAPAT), and Environment (CAPENV). (CAPO)=Σ(CAPIC)=any(CAPUSE)∪ Any(CAPSYS)∪ Any(CAPAT)∪ Any(CAPENV) Note. The joint operation (∪) is used to indicate that the low-level CAPs are combined (collected) into suitable CAPs. In this standard, the combination is further cited as specific CAP's "low-level CAP connection" (see Table 2 and Table 3). The CAPIC of each IC (user, system, assistive technology, environment) is further CAP(s) group of each of its component features (CAPCF) The details and procedures for providing various directional communications include. CAPIR for each input receiver (IR), each output emission (OT) CAPOT, and CAPPF for each processing function (PF). Description PFs are optional for users and systems, but for ATs Required. (CAPIC)=Σ(CAPCF)=any(CAPIR)∪ Any(CAPOT)∪ Any(CAPPF)∪ ICs can use one or more OTs and/or IRs. In the case where multiple OTs or IRs are required, it will be performed within the CAP specification. And (ANDed) operation. In the case of OTs or IRs replacement, OR operation is performed within the CAP specification. Note. (IR1ANDIR2) is equivalent to (IR1, IR2). Example. (IR1AND(IR2ORIR3)) requires that the input receiver IR1 be used all the time, and choose to use the input receiver IR2 or input the receiver IR3 one. The purpose of the system is to help users perform tasks. The system can be accessed directly by the user or not directly by the user. systematic The CAP provides a starting point for user assessment and improved system accessibility for a given environment. The environment can reduce the accessibility of the system. Assistive techniques can be used to enhance the accessibility of the system. Therefore, the assessment of access includes systems, users, environments and assistive technologies. Analysis of CAP(s). Figure 5 shows the structure of the CAP. The four-layer structure will be CF specific type of information [ie mode (CAPM), capability (CAPC) and processing (CAPP)] is placed in its special form. For the sake of simplicity and saving layout, only the applicable records are indicated. Figure 5 CAP structure 6.3 Describe the overall CAP The overall CAPO of a group of ICs shall be specified in detail as summarized in Table 1. Each CAPO specification has an identification information section that contains CAPO's unique name Name, type Type (ie CAPO) and qualifier Qualifier information. It may also contain an unstructured Narrative description. Narrative Description Description can be used to record preliminary information and/or give structure to all CAP specifications An easy-to-read introduction to the details. All available CAPO specifications have one or more connections to CAPIC and can have other CAPOs The connection. Table 1 High-level CAPO structure Describe possible values Identification Type of record type CAPO The identifier of the name CAPO or a well-known name (must be unique within the CAP) Qualifier unary operator that limits the record to the required, optional, or excluded One of the following three qualifiers. {SHALL MAY One of NOT} Describe a narrative description used to record preliminary information, and/or an in-depth description of the object's optional annotations Join Peer-CAPO The CAPO peer CAPO { \u003ccap-o-name,linkage-type\u003e , \u003ccap-o-name,linkage-type\u003e , Lower- CAPIC IC used by the CAPO { \u003ccap-ic-name,linkage-type\u003e , \u003ccap-ic-name,linkage-type\u003e , The connection is described as \u003ccap-name,linkage-type\u003e Correct. The cap-name field is the name of the target CAP. Linkage-type field describes this The applicable binary operators (ie, AND, OR, XOR) implied by the link, but if left blank, it will mean that the IC type is missing. The type of connection is (ie, AND in the case of CAPSYS/CAPAT/CAPENV and OR in the case of CAPUSE). See more information 7.3. 6.4 Describe interactive components Each CAPIC shall be detailed as outlined in Table 2. Each CAPIC specification has an identification information section that contains CAPIC Unique name and type Type (ie CAPUSE, CAPSYS, CAPAT, orCAPENV of the IC specification and an unstructured The narrative describes the Descriptions and qualifiers. All CAPIC specifications have one or more IR/OT/PF component characteristics The canonical join and the CAPO join to which it belongs. Table 2 Interactive component CAPIC structure Describe possible values Identification Type of type record One of the following four types of CAP. {CAPUSE CAPSYS CAPAT CAPENV} Name IC identifier or publicly known name any (must be unique within the CAP) Qualifier unary operator that limits the record to the required, optional, or excluded One of the following three qualifiers. {SHALL MAY One of NOT} description A narrative description used to record preliminary information, and/or an in-depth description of the object's optional Comment any Join Higher-CAPO CAPO to which this IC belongs { \u003ccap-o-name,linkage-type\u003e , \u003ccap-o-name,linkage-type\u003e , Peer-CAPIC The IC is equivalent to the IC. The connection to the IC channel indicates the connection letter that the IC has Number of tracks { \u003ccap-ic-name,linkage-type\u003e , \u003ccap-ic-name,linkage-type\u003e , Lower-CAPIR IR used in this IC { \u003ccap-ir-name,linkage-type\u003e , \u003ccap-ir-name,linkage-type\u003e , Lower-CAPPF PF used in this IC { \u003ccap-pf-name,linkage-type\u003e , \u003ccap-pf-name,linkage-type\u003e , Lower- CAPOT OT used in this IC { \u003ccap-ot-name,linkage-type\u003e , \u003ccap-ot-name,linkage-type\u003e , 6.5 Describe the characteristics of IC components Communication is only possible when the corresponding IRs of the OTs are used. Therefore, a common format is used to describe both IRs and OTs. The environment can be modeled as a component with its own IR and OT and with the ability to handle potentially suppressed access. Processing converts input and output The communication between them is therefore expressed as a pair of input and output formats along with the rules describing the conversion. User and system processing is usually evaluated Outside the scope. Environmental processing only affects the availability of communications. AT processing affects communication by transforming its characteristics. Each CAPIR, CAPOT, or CAPPF shall be detailed as summarized in Table 3. IC component feature (CF) specification has a standard The information part contains the type name of the CF unique name Name, CAPCF specification (ie CAPIR, CAPOT, or CAPPF). its It can also contain an unstructured narrative description Descriptions and a qualifier Qualifier. Table 3 IC component features CAPCF common format Describe possible values Identification Type of type record {CAPIR CAPPF One of CAPOT} The identifier of the name CF or the publicly known name any (must be unique within the CAP) Qualifier unary operator that limits the record to the required, optional, or exclusive {SHALL MAY One of NOT} description A narrative description used to record preliminary information, and/or an in-depth description of the object's optional Comment any Join Higher- CAPIC The CAPIC to which this CF belongs { \u003ccap-ic-name,linkage-type\u003e , \u003ccap-ic-name,linkage-type\u003e , Peer-CAPIR The IR used by the CF { \u003ccap-ir-name,linkage-type\u003e , \u003ccap-ir-name,linkage-type\u003e , Peer-CAPPF The PF used by the CF { \u003ccap-pf-name,linkage-type\u003e , \u003ccap-pf-name,linkage-type\u003e , Peer-CAPOT The OT used by the CF { \u003ccap-ot-name,linkage-type\u003e , \u003ccap-ot-name,linkage-type\u003e , Lower-CAPM The CF mode specification { \u003ccap-m-name,linkage-type\u003e , \u003ccap-m-name,linkage-type\u003e , Lower-CAPC The ability of the CF { \u003ccap-c-name,linkage-type\u003e , \u003ccap-c-name,linkage-type\u003e , Lower-CAPP The CF specification { \u003ccap-p-name,linkage-type\u003e , \u003ccap-p-name,linkage-type\u003e , Table 3 (continued) Describe possible values Connectivity The maximum number of channels that the channel capacity CF can accept {1 Any other specified integer One of N} Dedicated channel required for shared capacity CF {SHARABLE DEDICATED One of POSSIBLE} The number of times the CF ope...

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of GB/T 36443-2018_English be delivered?

Answer: Upon your order, we will start to translate GB/T 36443-2018_English as soon as possible, and keep you informed of the progress. The lead time is typically 3 ~ 5 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of GB/T 36443-2018_English with my colleagues?

Answer: Yes. The purchased PDF of GB/T 36443-2018_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Question 3: Does the price include tax/VAT?

Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countries

Question 4: Do you accept my currency other than USD?

Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.