Barrier-free screen reading method and device

Abstract

The present application discloses an accessible screen reading method and device, which relates to the field of computer technology. The method comprises: in response to a touch operation of a target object on a custom control in an IOS device, calling an accessible screen reading program based on a pre-configured first application interface to read the custom control, wherein the custom control is a subclass of the user interface view, and the first application interface is used to implement the accessibility of the screen reading program to the custom control; when a pop-up window view appears on the IOS device, calling an accessible screen reading program based on a pre-configured second application interface to read the pop-up window view, wherein the second application interface is used to implement the focus and access of the pop-up window view by the accessible screen reading program. The present application solves the technical problems that the accessible screen reading function cannot be implemented for custom controls in IOS devices, and that it is difficult to implement accessible focus penetration when the page layout is complex.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to a barrier-free screen reading method and device. Background Art

[0002] VoiceOver is an innovative screen reading technology used in iOS devices. It acts as a medium between the user interface in an application and the user's touch, and can provide audio descriptions for views and controls in an application. Through this technology, users only need to touch the screen to get the corresponding voice prompt information, and then make correct and expected operations. In other words, users can fully control their devices without watching the screen, which is especially beneficial for the visually impaired, achieving barrier-free screen reading.

[0003] Currently, an API (Application Programming Interface) - Accessibility (Accessibility Programming Interface) is provided to help applications provide VoiceOver with the information needed to describe the user interface to achieve barrier-free screen reading. However, existing solutions can usually only achieve barrier-free screen reading for standard UIKit controls and views, and cannot achieve barrier-free screen reading for custom controls. In addition, barrier-free focus penetration is also a problem when the page layout is complex.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide an accessible screen reading method and device to at least solve the technical problems that the accessible screen reading function cannot be implemented for custom controls in iOS devices, and that it is difficult to achieve accessible focus penetration when the page layout is complex.

[0006] According to one aspect of an embodiment of the present application, a barrier-free screen reading method is provided, comprising: in response to a target object's touch operation on a custom control in the IOS device, calling an accessible screen reading program based on a preconfigured first application interface to read the custom control, wherein the custom control is a subclass of a non-user interface view, and the first application interface is used to implement access to the custom control by the accessible screen reading program; when a pop-up view appears on the IOS device, calling the accessible screen reading program based on a preconfigured second application interface to read the pop-up view, wherein the second application interface is used to implement focus and access to the pop-up view by the accessible screen reading program.

[0007] Optionally, the first application interface configuration process includes: when the custom control is a single view, setting the accessibility status of the single view in the implementation interface of the single view or the instantiation code of the single view to achieve barrier-free access to the custom control by the accessible screen reader; when the custom control is a view container including multiple subviews, setting the accessibility status of each subview in the view container in the implementation interface of the view container to achieve barrier-free access to the custom control by the accessible screen reader.

[0008] Optionally, setting the accessibility status of the single view in the implementation interface of the single view includes: implementing a user interface element accessibility protocol in the implementation interface of the single view, wherein the user interface element accessibility protocol is used to implement access to the single view by the accessible screen reader; and returning "yes" when "the single view is an accessible element".

[0009] Optionally, setting the accessibility state of the single view in the instantiation code of the single view includes: assigning a value to an accessibility element attribute corresponding to the single view; and setting "the single view is an accessibility element" to "yes".

[0010] Optionally, the accessibility status of each view in the view container is set in the implementation interface of the view container, including: implementing a user interface view container accessibility access protocol in the implementation interface of the view container, wherein the user interface view container accessibility access protocol is used to implement the accessibility screen reader's access to each subview in the view container.

[0011] Optionally, a user interface view container accessibility protocol is implemented in the implementation interface of the view container, including: defining a variable array; creating a corresponding number of accessibility elements based on the number of sub-views in the view container, and specifying the attributes of each accessibility element based on the information of each sub-view, and adding each accessibility element to the variable array, wherein the accessibility element is used to implement the accessibility screen reader's access to the sub-view corresponding to the accessibility element; returning "No" when "the view container is an accessibility element"; returning the number of sub-views that support accessibility screen reading; returning the directory corresponding to the sub-view that supports accessibility screen reading; and returning the accessibility element attributes under the directory.

[0012] Optionally, the second application interface configuration process includes: setting the "Accessibility view is a pop-up window" attribute corresponding to the pop-up view to "Yes" to focus the accessibility screen reader program on the pop-up view and access the pop-up view.

[0013] According to another aspect of an embodiment of the present application, an accessible screen reading device is also provided, including: a first screen reading module, for responding to a target object's touch operation on a custom control in an IOS device, and calling an accessible screen reading program based on a pre-configured first application interface to read the custom control, wherein the custom control is a subclass of a user interface view, and the first application interface is used to implement access to the custom control by the accessible screen reading program; a second screen reading module, for calling an accessible screen reading program based on a pre-configured second application interface to read the pop-up view when a pop-up view appears on the IOS device, and wherein the second application interface is used to implement focus and access to the pop-up view by the accessible screen reading program.

[0014] According to another aspect of an embodiment of the present application, a processor is further provided, wherein the processor is used to run a program, wherein the above-mentioned barrier-free screen reading method is executed when the program is running.

[0015] According to another aspect of an embodiment of the present application, an electronic device is also provided, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the above-mentioned barrier-free screen reading method.

[0016] In an embodiment of the present application, corresponding application programming interfaces are pre-configured to respectively enable access to custom controls by an accessible screen reader and to enable focus and access to a pop-up view by the accessible screen reader. This allows the IOS device to respond to a touch operation of the custom control by a target object, call the accessible screen reader based on a first application programming interface to read the custom control, and call the accessible screen reader based on a second application programming interface to read the pop-up view when a pop-up view appears on the IOS device. This solves the problem that the accessible screen reader function cannot be implemented for custom controls in IOS devices, and that it is difficult to implement accessible focus penetration technology when the page layout is complex. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 It is a flowchart of a barrier-free screen reading method provided according to an embodiment of the present application;

[0019] Figure 2is a schematic diagram of barrier-free access information provided according to an embodiment of the present application;

[0020] Figure 3 is a schematic structural diagram of a barrier-free screen reading device provided according to an embodiment of the present application;

[0021] Figure 4 It is a schematic diagram of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0024] In order to better understand the embodiments of the present application, some nouns or terms that appear in the description of the embodiments of the present application are translated and explained as follows:

[0025] IOS narration function: 1) Slide to browse: swipe left or right to switch the focus between the items on the screen; 2) Touch to browse: touch the screen with one finger, then drag your finger across the content until the focus moves to the desired content; 3) Activate the selected item: double-click anywhere on the screen; 4) Scroll the screen or list: first focus the narration on any element in the area to be scrolled, then quickly slide three fingers on the screen at the same time.

[0026] UIkit: is a lightweight, modular front-end framework that can quickly build powerful web front-end interfaces. UIKit provides comprehensive HTML, CSS and JS components. It is simple to use and easy to customize and expand.

[0027] UIView (User Interface View): It is the basic element of the screen. UIView is a quadrilateral with position attributes and a certain size. It usually has a background color and can contain strings or pictures. UIView can have subclasses of the UIView type, so that you can easily add UIView to UIView to create various screens.

[0028] Accessibility (Accessibility Programming Interface): Usually includes two informal protocols and one class, as follows:

[0029] UIAccessibility (User Interface Accessibility): An informal protocol. Objects that implement the UIAccessibility protocol report their accessibility status (i.e., whether they are accessible) and provide descriptive information about themselves. By default, standard UIKit controls and views implement the UIAccessibility protocol.

[0030] UIAccessibilityContainer (Accessibility of User Interface View Container): An informal protocol, generally used for subclasses of UIView, which allows some of its sub-UIs to be accessed as separate elements. This protocol is very useful when the sub-objects contained in a view are not subclasses of UIView and cannot be automatically accessible.

[0031] UIAccessibilityElement (User Interface Element Accessibility): Class, this class implements the UIAccessibility protocol by default, and can create an instance of this class for an object that cannot be automatically accessible to an object (such as a non-UIView subclass or a non-existent object), so that it can be accessible.

[0032] The properties that describe the accessible elements of the user interface are the core of UIAccessibility. When the user accesses or interacts with a control or view, VoiceOver will provide the corresponding property information. UIAccessibility defines the following properties:

[0033] Label: A short, localized word or phrase that succinctly describes a control or view but does not define the element type. For example, "Add" or "Play".

[0034] Traits: A combination of one or more independent traits, each of which describes an aspect of an element's state, behavior, or purpose. For example, if an element behaves like a keyboard key and is currently selected, the element can use the combined traits of Keyboard Key and Selected.

[0035] Hint: A brief, localized phrase that describes the result of an element's action, such as "add title" or "open shopping list."

[0036] Frame: The frame of an element is the coordinates of the element on the screen, indicating the position and size of the element on the screen.

[0037] Value: The current value of an element, when the value cannot be represented using a label. For example, a slider might be labeled "Speed", but its current value might be "50%".

[0038] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0039] The present application scheme is described below in conjunction with preferred embodiments.

[0040] Example 1

[0041] According to an embodiment of the present application, an accessible screen reading method applied to an IOS device is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0042] Figure 1 is a flowchart of an optional barrier-free screen reading method according to an embodiment of the present application, such as Figure 1 As shown, the method at least includes steps S102-S106, wherein:

[0043] Step S102, in response to the target object's touch operation on the custom control in the IOS device, calling an accessible screen reader program to read the custom control based on a pre-configured first application interface, wherein the custom control is a subclass of a non-user interface view, and the first application interface is used to implement accessibility to the custom control.

[0044] Among them, the barrier-free screen reading program may be VoiceOver, which acts as a medium between the user interface in the application and the user touch, and can provide audio descriptions for the views and controls in the application, so that the user only needs to touch the screen to get the corresponding voice prompt information, and can fully control the device without watching the screen, thus achieving barrier-free screen reading.

[0045] Since custom controls are usually not subclasses of the user interface view UIView, they cannot be automatically and barrier-freely accessed by VoiceOver. In this case, it is necessary to configure the corresponding first application interface to enable VoiceOver to access the custom control by setting the accessibility status of the custom control.

[0046] Specifically, the custom control may be a single view or a view container including multiple subviews. The configuration process of the first application program interface in these two cases is described below respectively.

[0047] When the custom control is a single view, two solutions are provided, namely, setting the accessibility status of the single view in the implementation interface of the single view or in the instantiation code of the single view, so as to enable barrier-free screen reader programs to access the custom control.

[0048] When setting the accessibility status of a single view in the implementation interface of a single view, implement the user interface element barrier-free access protocol in the implementation interface of the single view, and return "yes" in "a single view is a barrier-free access element". The user interface element barrier-free access protocol is UIAccessibilityElement, which is used to implement barrier-free screen reader access to a single view. For specific codes, please refer to:

[0049] -(BOOL)isAccessibilityElement{

[0050] return YES;

[0051] }

[0052] Optionally, when setting the accessibility status of a single view in the instantiation code of a single view, assign a value to the accessible element attribute corresponding to the single view; set "Single view is accessible element" to "Yes". For specific codes, refer to:

[0053] view.isAccessibilityElement=YES

[0054] When the custom control is a view container that includes multiple subviews, since what needs to be accessed specifically is the individual subviews in the view container rather than the view container itself, the accessibility status of each subview in the view container can be set in the implementation interface of the view container to enable accessibility screen readers to access the custom control.

[0055] In some optional embodiments of the present application, the user interface view container barrier-free access protocol can be implemented in the implementation interface of the view container, wherein the user interface view container barrier-free access protocol, namely UIAccessibilityContainer, is used to implement the accessibility screen reader to the various subviews in the view container. For details, please refer to the following process:

[0056] Define a mutable array NSMutableArray to store accessible elements accessibleElements;

[0057] Create a corresponding number of accessibility elements based on the number of subviews in the view container, specify the properties of each accessibility element based on the information of each subview, and add each accessibility element to a mutable array, where each accessibility element corresponds to a UIAccessibilityElement, which is used to enable accessibility screen readers to access the subviews corresponding to the accessibility elements;

[0058] When "View container is an accessible element" returns "No", please refer to the specific code:

[0059] -(BOOL)isAccessibilityElement{

[0060] return NO;

[0061] }

[0062] Returns the number of subviews that support barrier-free screen reading. For specific codes, please refer to:

[0063] -(NSInteger)accessibilityElement Count{

[0064] return[[self accessibleElements]count];

[0065] }

[0066] Returns the directory corresponding to the subviews that support barrier-free screen reading. For specific codes, please refer to:

[0067] -(id)accessibilityElement At Index:(NSInteger)index{

[0068] return[[self accessibleElements]object At Index:index];

[0069] }

[0070] Returns the accessible element attributes under the directory. For specific codes, please refer to:

[0071] -(NSInteger)index Of AccessibilityElement:(id)element{

[0072] return[[self accessibleElements]index Of Object:element];

[0073] }

[0074] Step S104, when a pop-up view appears on the IOS device, calling an accessible screen reader program to read the pop-up view based on a pre-configured second application interface, wherein the second application interface is used to enable the accessible screen reader program to focus on and access the pop-up view.

[0075] It is understandable that when a pop-up view appears on the device, such as a pop-up prompt message, VoiceOver needs to focus on the pop-up view and give priority to barrier-free screen reading of the pop-up view. At this time, it is necessary to configure the corresponding second application interface to enable the barrier-free screen reading program to focus on and access the pop-up view.

[0076] Specifically, when configuring the second application interface, the "Accessibility View is a Pop-up" property corresponding to the pop-up view can be set to "Yes" to focus the accessibility screen reader on the pop-up view and access the pop-up view. For specific codes, please refer to:

[0077] -view.accessibilityViewIsModal=YES

[0078] Optionally, the user can also choose to manually focus on the pop-up view.

[0079] In some optional embodiments of the present application, specific descriptive accessibility information can also be viewed based on the Interface Builder (interface creation) inspector window provided by the iOS device, such as Figure 2, which displays accessibility information for a text field.

[0080] In an embodiment of the present application, corresponding application programming interfaces are pre-configured to respectively enable access to custom controls by an accessible screen reader and to enable focus and access to a pop-up view by the accessible screen reader. This allows the IOS device to respond to a touch operation of the custom control by a target object, call the accessible screen reader based on a first application programming interface to read the custom control, and call the accessible screen reader based on a second application programming interface to read the pop-up view when a pop-up view appears on the IOS device. This solves the problem that the accessible screen reader function cannot be implemented for custom controls in IOS devices, and that it is difficult to implement accessible focus penetration technology when the page layout is complex.

[0081] Example 2

[0082] According to an embodiment of the present application, a barrier-free screen reading device for implementing the barrier-free screen reading method is also provided, such as Figure 3 As shown, the device at least includes a first screen reading module 30 and a second screen reading module 32, wherein:

[0083] The first screen reading module is used to respond to the target object's touch operation on the custom control in the IOS device, and call the accessible screen reading program based on a pre-configured first application interface to read the custom control, wherein the custom control is a subclass of the user interface view, and the first application interface is used to implement accessibility The screen reading program access to the custom control.

[0084] Since custom controls are usually not subclasses of the user interface view UIView, they cannot be automatically and barrier-freely accessed by VoiceOver. In this case, it is necessary to configure the corresponding first application interface to enable VoiceOver to access the custom control by setting the accessibility status of the custom control.

[0085] Specifically, the custom control may be a single view or a view container including multiple subviews. The configuration process of the first application program interface in these two cases is described below respectively.

[0086] When the custom control is a single view, two solutions are provided, namely, setting the accessibility status of the single view in the implementation interface of the single view or in the instantiation code of the single view, so as to enable barrier-free screen reader programs to access the custom control.

[0087] Among them, when setting the accessibility status of a single view in the implementation interface of a single view, the user interface element accessibility access protocol is implemented in the implementation interface of the single view, and "yes" is returned in "the single view is an accessible element", wherein the user interface element accessibility access protocol is UIAccessibilityElement, which is used to implement accessibility screen reading programs to access a single view.

[0088] Optionally, when setting the accessibility state of a single view in the instantiation code of the single view, assign a value to the accessibility element attribute corresponding to the single view; set "Single View is Accessibility Element" to "Yes".

[0089] When the custom control is a view container that includes multiple subviews, since what needs to be accessed specifically is the individual subviews in the view container rather than the view container itself, the accessibility status of each subview in the view container can be set in the implementation interface of the view container to enable accessibility screen readers to access the custom control.

[0090] In some optional embodiments of the present application, the user interface view container barrier-free access protocol can be implemented in the implementation interface of the view container, wherein the user interface view container barrier-free access protocol, namely UIAccessibilityContainer, is used to implement the accessibility screen reader to the various subviews in the view container. For details, please refer to the following process:

[0091] Define a mutable array NSMutableArray to store accessible elements accessibleElements;

[0092] Create a corresponding number of accessibility elements based on the number of subviews in the view container, specify the properties of each accessibility element based on the information of each subview, and add each accessibility element to a mutable array, where each accessibility element corresponds to a UIAccessibilityElement, which is used to enable accessibility screen readers to access the subviews corresponding to the accessibility elements;

[0093] Return "No" on "View container is an accessible element";

[0094] Returns the number of subviews that support accessibility;

[0095] Returns the directory corresponding to the subviews that support barrier-free screen reading;

[0096] Returns the accessibility attributes of a directory element.

[0097] The second screen reading module is used to call an accessible screen reading program to read the pop-up view based on a pre-configured second application interface when a pop-up view appears on the IOS device, wherein the second application interface is used to enable the accessible screen reading program to focus on and access the pop-up view.

[0098] When a pop-up view appears on the device, such as a pop-up prompt message, VoiceOver needs to focus on the pop-up view and give priority to barrier-free screen reading of the pop-up view. At this time, it is necessary to configure the corresponding second application interface to enable the barrier-free screen reading program to focus on and access the pop-up view.

[0099] Specifically, when configuring the second application interface, the "Accessibility view is a pop-up window" property corresponding to the pop-up window view can be set to "Yes" to focus the accessibility screen reader on the pop-up window view and access the pop-up window view.

[0100] In an embodiment of the present application, based on a pre-configured corresponding application program interface, access to custom controls by an accessible screen reader is implemented, as is focusing on and accessing a pop-up view by the accessible screen reader, so that the IOS device can respond to the touch operation of the target object on the custom control, call the accessible screen reader based on the first application program interface to read the custom control, and when a pop-up view appears on the IOS device, call the accessible screen reader based on the second application program interface to read the pop-up view, thereby solving the problem that the accessible screen reading function cannot be implemented for custom controls in IOS devices, and it is difficult to implement accessible focus penetration technology when the page layout is complex.

[0101] Example 3

[0102] According to an embodiment of the present application, a computer-readable storage medium is also provided, on which a program is stored. When the program is executed by a processor, the barrier-free screen reading method in Example 1 is implemented.

[0103] According to an embodiment of the present application, a processor is also provided, which is used to run a program, wherein the barrier-free screen reading method in Example 1 is executed when the program is running.

[0104] According to an embodiment of the present application, an electronic device is also provided, the electronic device includes one or more processors and a memory, the memory is used to store one or more programs, and an optional structure thereof is as follows: Figure 4 As shown, the electronic device 40 includes at least a memory 400 and a processor 402. When the program is executed by the processor, the processor implements the barrier-free screen reading method in Example 1.

[0105] Specifically, the following steps can be executed when the program is running: in response to the target object's touch operation on the custom control in the IOS device, calling the accessible screen reader program to read the custom control based on the pre-configured first application interface, wherein the custom control is a subclass of the user interface view, and the first application interface is used to implement the accessibility screen reader program to access the custom control; when a pop-up view appears on the IOS device, calling the accessible screen reader program to read the pop-up view based on the pre-configured second application interface, wherein the second application interface is used to implement the accessibility screen reader program to focus on and access the pop-up view.

[0106] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0107] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0108] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0109] The present application is described with reference to the flowcharts and / or block diagrams of the methods, apparatuses, and electronic devices according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0110] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0111] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0112] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0113] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0114] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0115] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0116] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A barrier-free screen reading method, applied to an IOS device, characterized in that: include: In response to a touch operation of a target object on a custom control in the iOS device, calling an accessible screen reader program to read the custom control based on a pre-configured first application program interface, wherein the custom control is a subclass of a non-user interface view, and the first application program interface is used to implement access to the custom control by the accessible screen reader program; When a pop-up window view appears on the iOS device, calling an accessible screen reader program to read the pop-up window view based on a pre-configured second application program interface, wherein the second application program interface is used to enable the accessible screen reader program to focus on and access the pop-up window view; Wherein, the first application program interface configuration process includes: when the custom control is a single view, setting the accessibility state of the single view in the implementation interface of the single view or the instantiation code of the single view, so as to achieve barrier-free access to the custom control by the barrier-free screen reader; when the custom control is a view container including multiple subviews, setting the accessibility state of each subview in the view container in the implementation interface of the view container, so as to achieve barrier-free access to the custom control by the barrier-free screen reader; The second application interface configuration process includes: setting the "Accessibility view is a pop-up window" attribute corresponding to the pop-up view to "Yes" to focus the accessibility screen reader program on the pop-up view and access the pop-up view.

2. The method according to claim 1, characterized in that Setting the accessibility state of the single view in the implementation interface of the single view includes: Implementing a user interface element barrier-free access protocol in the implementation interface of the single view, wherein the user interface element barrier-free access protocol is used to implement access to the single view by the barrier-free screen reader; Returns "Yes" for "The single view is an accessible element".

3. The method according to claim 1, characterized in that Setting the accessibility state of the single view in the instantiation code of the single view includes: Assigning values ​​to the accessibility element attributes corresponding to the single view; Set Make this single view an accessible element to Yes.

4. The method according to claim 1, characterized in that: Setting the accessibility status of each view in the view container in the implementation interface of the view container includes: A user interface view container barrier-free access protocol is implemented in the implementation interface of the view container, wherein the user interface view container barrier-free access protocol is used to enable the barrier-free screen reader to access each subview in the view container.

5. The method according to claim 4, characterized in that Implementing the user interface view container accessibility protocol in the implementation interface of the view container includes: Define a mutable array; Creating a corresponding number of accessibility elements based on the number of subviews in the view container, specifying properties of each accessibility element based on information about each subview, and adding each accessibility element to the variable array, wherein the accessibility element is used to enable the accessibility screen reader to access the subviews corresponding to the accessibility element; Return "No" if "The view container is an accessible element"; Returns the number of subviews that support accessibility; Returns the directory corresponding to the subview that supports barrier-free screen reading; Returns the accessibility attributes of the element under the specified directory.

6. A barrier-free screen reading device, characterized in that: include: A first screen reading module is used to respond to a touch operation of a target object on a custom control in an IOS device, and to call an accessible screen reading program to read the custom control based on a pre-configured first application program interface, wherein the custom control is a subclass of a user interface view, and the first application program interface is used to implement access to the custom control by the accessible screen reading program, and the first application program interface configuration process includes: when the custom control is a single view, setting the accessibility state of the single view in the implementation interface of the single view or the instantiation code of the single view to implement accessible access to the custom control by the accessible screen reading program; when the custom control is a view container including multiple subviews, setting the accessibility state of each subview in the view container in the implementation interface of the view container to implement accessible access to the custom control by the accessible screen reading program; The second screen reading module is used to call an accessible screen reading program to read the pop-up view based on a pre-configured second application interface when a pop-up view appears on the IOS device, wherein the second application interface is used to enable the accessible screen reading program to focus on and access the pop-up view; the second application interface configuration process includes: setting the "Accessibility View as Pop-up" attribute corresponding to the pop-up view to "Yes" to focus the accessible screen reading program on the pop-up view and access the pop-up view.

7. A processor, characterized in that: The processor is used to run a program, wherein the program, when running, executes the barrier-free screen reading method described in any one of claims 1 to 5.

8. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the barrier-free screen reading method described in any one of claims 1 to 5.

Images