Interface interaction method, system and equipment and storage medium

Abstract

The embodiment of the invention relates to an interface interaction method, system and device and a storage medium. A method presented herein includes determining a barrier-free event associated with a view within a client; determining a target barrier-free interface corresponding to the barrier-free event from a group of barrier-free interfaces provided by the client, the definition of the group of barrier-free interfaces being independent of a target platform corresponding to the client; and responding to the barrier-free event by using the platform capability corresponding to the target barrier-free interface in the target platform. In this way, the embodiment of the invention can support a user to more efficiently process the barrier-free event associated with the view in the client, so that the development efficiency is improved.

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, systems, devices, and computer-readable storage media for interface interaction. Background Art

[0002] With the development of computer technology, barrier-free development has also received widespread attention. People hope to use a more convenient and simple development model when conducting barrier-free development, thereby reducing the requirements for barrier-free development capabilities and the cost of barrier-free development. Summary of the invention

[0003] In a first aspect of the present disclosure, a method for interface interaction is provided. The method includes: determining an accessibility event associated with a view in a client; determining a target accessibility interface corresponding to the accessibility event from a set of accessibility interfaces provided by the client, wherein the definition of the set of accessibility interfaces is independent of a target platform corresponding to the client; and responding to the accessibility event using a platform capability corresponding to the target accessibility interface in the target platform.

[0004] In a second aspect of the present disclosure, a system for interface interaction is provided. The system includes: a front-end layer, the front-end layer is configured to trigger an accessibility event associated with a view in a client; a native layer, the native layer is configured to provide a set of accessibility interfaces, the definition of the set of accessibility interfaces is independent of the target platform corresponding to the client, wherein the native layer is further configured to: determine a target accessibility interface corresponding to the accessibility event from the set of accessibility interfaces provided; and respond to the accessibility event using a platform capability corresponding to the target accessibility interface in the target platform.

[0005] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. When the instructions are executed by the at least one processing unit, the device executes the method of the first aspect.

[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.

[0007] In a fifth aspect of the present disclosure, a computer program product is provided, which is tangibly stored in a computer storage medium and includes computer executable instructions, which when executed by a device cause the device to perform the method of the first aspect.

[0008] It should be understood that the contents described in this content section are not intended to limit the key features or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0010] Figure 1 A schematic diagram showing an example environment in which embodiments according to the present disclosure may be implemented;

[0011] Figure 2 A flowchart showing an example process of interface interaction according to some embodiments of the present disclosure;

[0012] Figure 3 An example process of interface interaction according to some embodiments of the present disclosure is shown;

[0013] Figure 4 A schematic structural block diagram showing an example system for interface interaction according to some embodiments of the present disclosure; and

[0014] Figure 5 A block diagram of an electronic device capable of implementing various embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0015] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0016] It should be noted that the titles of any sections / subsections provided herein are not restrictive. Various embodiments are described throughout this article, and any type of embodiment may be included under any section / subsection. In addition, the embodiments described in any section / subsection may be combined in any manner with any other embodiments described in the same section / subsection and / or different sections / subsections.

[0017] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below. The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0018] The embodiments of the present disclosure may involve user data, data acquisition and / or use, etc. These aspects are subject to the corresponding laws, regulations and relevant provisions. In the embodiments of the present disclosure, all data collection, acquisition, processing, processing, forwarding, use, etc. are carried out on the premise that the user knows and confirms. Accordingly, when implementing each embodiment of the present disclosure, the type, scope of use, usage scenario, etc. of the data or information that may be involved should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with the relevant laws and regulations. The specific notification and / or authorization method can vary according to the actual situation and application scenario, and the scope of the present disclosure is not limited in this respect.

[0019] In this specification and the embodiments, if personal information processing is involved, it will be processed on the premise of having a legal basis (such as obtaining the consent of the subject of personal information, or it is necessary to perform a contract, etc.), and will only be processed within the scope of regulations or agreements. If a user refuses to process personal information other than the necessary information for basic functions, it will not affect the user's use of basic functions.

[0020] According to traditional solutions, most platforms provide a rich set of accessible application programming interfaces, which means that users of cross-end frameworks need to perform differentiated processing for different platforms, affecting the user experience.

[0021] The embodiment of the present disclosure proposes a scheme for interface interaction. According to the scheme, an accessibility event associated with a view in a client can be determined; a target accessibility interface corresponding to the accessibility event can be determined from a set of accessibility interfaces provided by the client, wherein the definition of the set of accessibility interfaces is independent of the target platform corresponding to the client; and the accessibility event can be responded to by utilizing the platform capability corresponding to the target accessibility interface in the target platform.

[0022] In this way, the embodiments of the present disclosure can support users to more efficiently handle accessibility events associated with views within the client, thereby improving development efficiency.

[0023] Various example implementations of the solution are described in detail below in conjunction with the accompanying drawings.

[0024] Example Environment

[0025] Figure 1 1 is a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. Figure 1 As shown, example environment 100 may include electronic device 110 .

[0026] In this example environment 100, the electronic device 110 may run an application 120 that supports interface interaction. The application 120 may be any appropriate type of application for interface interaction, examples of which may include, but are not limited to, development applications, code editing applications, video applications, social applications, or other appropriate applications. The user 140 may interact with the application 120 via the electronic device 110 and / or its attached devices.

[0027] exist Figure 1 In the environment 100, if the application 120 is in an active state, the electronic device 110 can present an interface 150 for supporting interface interaction through the application 120.

[0028] In some embodiments, the electronic device 110 communicates with the server 130 to provide services for the application 120. The electronic device 110 can be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a handheld computer, a portable game terminal, a VR / AR device, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio receiver, an e-book device, a game device, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the electronic device 110 can also support any type of interface for the user (such as a "wearable" circuit, etc.).

[0029] The server 130 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks, and big data and artificial intelligence platforms. The server 130 may include, for example, a computing system / server, such as a mainframe, an edge computing node, a computing device in a cloud environment, etc. The server 130 may provide background services for the application 120 that supports content presentation in the electronic device 110.

[0030] A communication connection may be established between the server 130 and the electronic device 110. The communication connection may be established in a wired manner or a wireless manner. The communication connection may include, but is not limited to, a Bluetooth connection, a mobile network connection, a Universal Serial Bus (USB) connection, a Wireless Fidelity (WiFi) connection, etc., and the embodiments of the present disclosure are not limited in this respect. In the embodiments of the present disclosure, the server 130 and the electronic device 110 may implement signaling interaction through the communication connection between the two.

[0031] It should be understood that the structure and function of the various elements in the environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure.

[0032] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.

[0033] Example Process

[0034] Figure 2 FIG. 2 is a flowchart of an example interface interaction process 200 according to some embodiments of the present disclosure. The process 200 may be implemented at the electronic device 110. Figure 1 Process 200 is described.

[0035] like Figure 2 As shown, at block 210 , the electronic device 110 determines an accessibility event associated with a view within a client.

[0036] For ease of description, the following will refer to Figure 3 Some embodiments of the present disclosure are introduced.

[0037] In some embodiments, such a client (e.g., client a, client b) may be a group of clients corresponding to different operating systems, illustratively, client a corresponds to operating system a, client b corresponds to operating system b, etc. It is to be understood that the present disclosure is not intended to limit the type and / or number of operating systems.

[0038] In some embodiments, the electronic device 110 may determine accessibility events associated with views in such a group of clients. Such accessibility events may, for example, indicate events corresponding to common accessibility capabilities in various operating systems and / or browsers, events corresponding to basic accessibility capabilities, or events corresponding to accessibility capabilities without platform differences.

[0039] In some embodiments, such accessibility events may include, for example, marking accessible content. In order to break through the client view hierarchy limitation, the electronic device 110 may mark accessible content for any single view element in the client. As an example, the electronic device 110 may mark the content expressed by the accessibility focus in a single view element (e.g., view element a, view element b, or view element c), such as text content, image content, status information, and interaction prompts.

[0040] In some embodiments, such an accessibility event may also include managing an accessibility focus. As an example, the electronic device 110 may focus the accessibility focus on the corresponding accessibility text by managing the accessibility focus to indicate that the accessibility text is selected.

[0041] In some embodiments, such accessibility events may also include broadcasting of accessibility content. As an example, in response to a pop-up window appearing on the client, the electronic device 110 may call a screen reading interface to play the content corresponding to the pop-up window.

[0042] Further, in order to improve the efficiency of barrier-free interaction, the electronic device 110 may determine a set of barrier-free interfaces based on the barrier-free events described above, and such a set of barrier-free interfaces may be determined based on the intersection of multiple sets of barrier-free capabilities provided by multiple platforms (e.g., operating system a, operating system b, and / or browser). In some embodiments, such a set of barrier-free interfaces may include a first barrier-free interface 301 for marking barrier-free content; a second barrier-free interface 302 for managing barrier-free focus; and a third barrier-free interface 303 for broadcasting barrier-free content.

[0043] In this way, the electronic device 110 can determine a set of accessibility interfaces corresponding to the accessibility events in the client to facilitate subsequent packaging and calling.

[0044] return Figure 2 In box 220, the electronic device 110 determines a target accessibility interface corresponding to the accessibility event from a set of accessibility interfaces provided by the client, and the definition of the set of accessibility interfaces is independent of the target platform corresponding to the client.

[0045] As an example, the electronic device 110 reads the accessible content in response to the accessibility event indication, and the electronic device 110 may determine that the target accessible interface is the third accessible interface 303 from a group of accessible interfaces provided by the client.

[0046] In some embodiments, the definition of such a set of barrier-free interfaces is independent of the target platform corresponding to the client. Such a target platform may indicate the operating system running the client, for example, operating system a or operating system b.

[0047] In order to uniformly manage the client accessible view elements, in some other embodiments, the client may also provide an element management interface provided by encapsulating a set of accessible interfaces. Figure 3 In some embodiments, such an element management interface may include a first management interface 304 for controlling the order in which accessible content is read aloud. In some embodiments, the electronic device 110 may customize the order in which accessible view elements are read aloud. As an example, the electronic device 110 may customize the order in which the contents corresponding to view element a, view element b, and view element c are read aloud, respectively. As another example, the electronic device 110 may customize the order in which the contents corresponding to view element b, view element c, and view element a are read aloud, respectively. In some embodiments, the electronic device 110 may control the order in which accessible content is read aloud based on the order of identifiers of accessible view elements.

[0048] In some embodiments, such an element management interface may further include a second management interface 305 for monitoring view changes associated with accessible content. Such view changes may, for example, indicate changes in rendering content, style, layout, and view hierarchy corresponding to accessible view elements. Figure 3 For example, the electronic device 110 may monitor whether the nodes corresponding to the view element a, the view element b and / or the view element c are deleted.

[0049] In order to facilitate monitoring of the switching action of the client's barrier-free focus, in some embodiments, such an element management interface may further include a third management interface 306 for switching the barrier-free focus. As an example, the electronic device 110 may switch the barrier-free focus at the position of view element a to the position corresponding to view element b based on the interaction between the user and the client.

[0050] In some embodiments, such an element management interface may further include a fourth management interface 307 for focusing on a specified element. As an example, the electronic device 110 may actively control a client accessible view element (eg, view element a) to be focused.

[0051] In this way, the electronic device 110 may respond to an accessibility event based on a target accessibility interface in a set of accessibility interfaces and / or a target management interface in an element management interface.

[0052] return Figure 2 , in box 230 , the electronic device 110 responds to the accessibility event using the platform capability corresponding to the target accessibility interface in the target platform.

[0053] In other embodiments, the electronic device 110 may also respond to accessibility events based on a target accessibility interface and / or an element management interface.

[0054] For ease of description, the following article takes the example of an interface element being an accessible control.

[0055] Continue to refer Figure 3 , in box 308, the electronic device 110 may create an accessibility control on the front end. In box 309, the electronic device 110 may initialize the accessibility control. In some examples, this step may be implemented, for example, by the front end calling a first accessibility interface 301 for marking accessible content in a set of accessibility interfaces provided by the client. In box 310, the electronic device 110 may create a node and position corresponding to the accessibility control based on the front end. In box 311, the electronic device 110 may be configured to focus on the accessibility control based on the user's operation. In some examples, this step may be implemented, for example, by the front end calling the first accessibility interface 301 and the second management interface 305 in the element management interface.

[0056] Further, in box 312, the electronic device 110 may determine whether the interface element corresponding to the accessibility event is associated with composite information. As an example, such composite information may indicate that in addition to reading the corresponding text, the accessibility control also needs to read the interface to be jumped after triggering the accessibility control.

[0057] In box 313, the electronic device 110 responds to the interface element corresponding to the accessibility event being associated with the composite information, and can use the platform capability to read the composite information aloud. Specifically, the electronic device 110 can process the composite information based on the composite information management module 314 provided by the front end. In some embodiments, such a composite information management module 314 can be implemented based on calling an application program interface in the client, and such an application program interface can be, for example, a set of accessibility interfaces and / or element management interfaces. Specifically, such an application program interface can be, for example, a third accessibility interface 303 for broadcasting accessible content and a fourth management interface 307 for focusing on a specified element.

[0058] In block 315, the electronic device 110 may initiate event monitoring associated with the interface element in response to the interface element corresponding to the accessibility event not being associated with the composite information or the electronic device 110 having completed processing of the composite information. As an example, the electronic device 110 may initiate loop monitoring 315 of events associated with the accessibility control in response to the accessibility control being able to implement a state change based on a user's operation.

[0059] Further, in box 316, the electronic device 110 can update the interface element in response to monitoring the update event associated with the interface element. As an example, assuming that the current user triggers focus on this barrier-free control, the electronic device 110 can update the style of this barrier-free control in response to monitoring the user's further preset operation (e.g., double-click operation) on this barrier-free control, for example, highlighting this barrier-free control. In some embodiments, updating the interface element can be implemented based on, for example, the second management interface 305 called by the front end for monitoring view changes associated with barrier-free content.

[0060] In some embodiments, the electronic device 110 may trigger an additional accessibility event associated with the updated interface element to read aloud the updated composite information associated with the updated interface element. As an example, the electronic device 110 may continuously monitor the additional accessibility event for the accessibility control, and use the front end to call a set of accessibility interfaces and / or element management interfaces based on the additional accessibility event to read aloud the updated composite information associated with the accessibility control.

[0061] In response to monitoring that the focus on the barrier-free control disappears, the electronic device 110 may end monitoring the barrier-free focus in block 317. In some examples, this step may be implemented by the electronic device 110 invoking the third management interface 306 for switching the barrier-free focus based on the front end.

[0062] In this way, the embodiments of the present disclosure can support users to more efficiently handle accessibility events associated with views within the client. Specifically, the front end can dynamically call a set of accessibility interfaces and / or focus element interfaces provided by the client based on different interaction states to form a complex and efficient accessibility interaction effect, thereby improving development efficiency.

[0063] Example Systems and Devices

[0064] The embodiments of the present disclosure also provide a corresponding system for implementing the above method or process. Figure 4 A schematic structural block diagram of an example system 400 for interface interaction according to some embodiments of the present disclosure is shown. The system 400 may be implemented as or included in the electronic device 110. Each module / component in the system 400 may be implemented by hardware, software, firmware, or any combination thereof.

[0065] like Figure 4As shown, system 400 includes a front-end layer 410, which is configured to trigger an accessibility event associated with a view in a client; and a native layer 420, which is configured to provide a set of accessibility interfaces, and the definition of the set of accessibility interfaces is independent of the target platform corresponding to the client, wherein the native layer is further configured to: determine a target accessibility interface corresponding to the accessibility event from the set of accessibility interfaces provided; and respond to the accessibility event by utilizing the platform capabilities corresponding to the target accessibility interface in the target platform.

[0066] In some embodiments, a set of accessible interfaces is determined based on an intersection of multiple sets of accessibility capabilities provided by multiple platforms.

[0067] In some embodiments, a set of accessibility interfaces includes multiple items of the following: a first accessibility interface for marking accessible content; a second accessibility interface for managing accessibility focus; and a third accessibility interface for broadcasting accessible content.

[0068] In some embodiments, the client also provides an element management interface provided by encapsulating a set of accessibility interfaces, and the element management interface includes at least one of the following: a first management interface for controlling the reading order of accessible content; a second management interface for monitoring view changes associated with accessible content; a third management interface for switching accessibility focus; and a fourth management interface for focusing on a specified element.

[0069] In some embodiments, the native layer 420 is further configured to respond to the interface element corresponding to the accessibility event being associated with the composite information and to read the composite information aloud using the platform capability.

[0070] In some embodiments, the system 400 further includes a start module configured to start event monitoring associated with the interface element.

[0071] In some embodiments, system 400 also includes a processing module configured to update the interface element in response to monitoring an update event associated with the interface element; and trigger an additional accessibility event associated with the updated interface element to read aloud the updated composite information associated with the updated interface element.

[0072] In some embodiments, the target platform indicates the operating system on which the client is running.

[0073] The modules included in the system 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or as an alternative to machine executable instructions, some or all of the modules in the system 400 can be implemented at least in part by one or more hardware logic components. As an example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0074] like Figure 5 As shown, the electronic device 500 is in the form of a general electronic device. The components of the electronic device 500 may include, but are not limited to, one or more processors or processing units 510, a memory 520, a storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 510 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 520. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 500. Figure 5 The electronic device 500 shown can be used to implement Figure 1 An electronic device 110.

[0075] The electronic device 500 typically includes a plurality of computer storage media. Such media may be any accessible media that is accessible to the electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 520 may be a volatile memory (e.g., registers, caches, random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 may be a removable or non-removable medium, and may include a machine-readable medium, such as a flash drive, a disk, or any other medium, which may be capable of being used to store information and / or data and may be accessed within the electronic device 500.

[0076] The electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Figure 5As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. The memory 520 may include a computer program product 525 having one or more program modules that are configured to perform various methods or actions of various embodiments of the present disclosure.

[0077] The communication unit 540 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 500 can be implemented in a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 500 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0078] The input device 550 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 560 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 500 may also communicate with one or more external devices (not shown) through the communication unit 540 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 500, or communicate with any device that allows the electronic device 500 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0079] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0080] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0081] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0082] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0083] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0084] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.

Claims

1. A method for interface interaction, comprising: Determine accessibility events associated with views within the client; Determining a target accessibility interface corresponding to the accessibility event from a set of accessibility interfaces provided by the client, wherein a definition of the set of accessibility interfaces is independent of a target platform corresponding to the client; as well as The accessibility event is responded to by utilizing a platform capability in the target platform corresponding to the target accessibility interface. 2 . The method of claim 1 , wherein the set of accessible interfaces is determined based on an intersection of multiple sets of accessibility capabilities provided by multiple platforms.

3. The method of claim 1, wherein the set of accessible interfaces includes multiple of the following: The first accessibility interface is used to mark accessible content; The second accessibility interface is used to manage accessibility focus; The third barrier-free interface is used to broadcast barrier-free content.

4. The method according to claim 1, wherein the client further provides an element management interface provided by encapsulating the set of accessibility interfaces, the element management interface comprising at least one of the following: A first management interface, used to control the reading order of accessible content; A second management interface for monitoring view changes associated with accessible content; The third management interface is used to switch the accessibility focus; The fourth management interface is used to focus on a specified element.

5. The method according to claim 1, wherein responding to the accessibility event by using a platform capability corresponding to the target accessibility interface in the target platform comprises: In response to the interface element corresponding to the accessibility event being associated with composite information, the composite information is read aloud using the platform capability.

6. The method according to claim 5, further comprising: Start the event listener associated with the interface element.

7. The method according to claim 6, further comprising: In response to monitoring an update event associated with the interface element, updating the interface element; as well as An additional accessibility event associated with the updated interface element is triggered to read aloud updated composite information associated with the updated interface element. The method according to claim 1 , wherein the target platform indicates an operating system on which the client runs.

9. A system for interface interaction, comprising: A front-end layer configured to trigger accessibility events associated with views within the client; A native layer, wherein the native layer is configured to provide a set of barrier-free interfaces, wherein the definition of the set of barrier-free interfaces is independent of a target platform corresponding to the client, The native layer is further configured to: determine a target accessibility interface corresponding to the accessibility event from a set of accessibility interfaces provided; and respond to the accessibility event using a platform capability in the target platform corresponding to the target accessibility interface.

10. An electronic device, comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 8 when executed by the at least one processing unit.

11. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 8.

12. A computer program product tangibly stored in a computer storage medium and comprising computer executable instructions which, when executed by a device, cause the device to perform the method according to any one of claims 1 to 8.

Images