CN114461172A - Barrier-free screen reading method and device - Google Patents

Barrier-free screen reading method and device Download PDF

Info

Publication number
CN114461172A
CN114461172A CN202210122998.7A CN202210122998A CN114461172A CN 114461172 A CN114461172 A CN 114461172A CN 202210122998 A CN202210122998 A CN 202210122998A CN 114461172 A CN114461172 A CN 114461172A
Authority
CN
China
Prior art keywords
barrier
view
free
screen reading
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210122998.7A
Other languages
Chinese (zh)
Inventor
韩维
杨光
丛明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202210122998.7A priority Critical patent/CN114461172A/en
Publication of CN114461172A publication Critical patent/CN114461172A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/16Sound input; Sound output
    • G06F3/167Audio in a user interface, e.g. using voice commands for navigating, audio feedback
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • G06F3/04883Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures for inputting data by handwriting, e.g. gesture or text
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Multimedia (AREA)
  • Health & Medical Sciences (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • General Health & Medical Sciences (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

The application discloses a barrier-free screen reading method and device, and relates to the technical field of computers. The method comprises the following steps: responding to touch operation of a target object on a user-defined control in the IOS equipment, calling a barrier-free screen reading program to read the screen of the user-defined control based on a first application program interface which is configured in advance, wherein the user-defined control is a subclass of a user interface view, and the first application program interface is used for realizing access of the barrier-free screen reading program to the user-defined control; and when the popup view appears in the IOS equipment, calling a barrier-free screen reading program to read the popup view based on a second application program interface which is configured in advance, wherein the second application program interface is used for realizing the focusing and the access of the barrier-free screen reading program to the popup view. The method and the device solve the technical problems that barrier-free screen reading function cannot be realized for the user-defined control in the IOS device, and barrier-free focus penetration is difficult to realize when the page layout is complex.

Description

Barrier-free screen reading method and device
Technical Field
The application relates to the technical field of computers, in particular to a barrier-free screen reading method and device.
Background
VoiceOver is an innovative screen reading technology applied to IOS equipment, and serves as a medium between a user interface in application and user touch, and can provide audio description for views, controls and the like in application.
Currently, an API (Application Programming Interface) -Accessibility (barrier-free access Programming Interface) is provided to help an Application program provide information required by VoiceOver to describe a user Interface, so as to realize barrier-free screen reading. However, the existing solutions can only achieve barrier-free screen reading of standard UIKit controls and views, barrier-free screen reading functions cannot be achieved for custom controls, and barrier-free focus penetration is also a problem when page layout is complex.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the application provides a barrier-free screen reading method and device, and the technical problems that a barrier-free screen reading function cannot be realized for a user-defined control in IOS equipment, and barrier-free focus penetration is difficult to realize when a page layout is complex are at least solved.
According to an aspect of an embodiment of the present application, there is provided an obstacle-free screen reading method, including: responding to a touch operation of a target object on a user-defined control in the IOS equipment, and calling a barrier-free screen reading program to read the screen of the user-defined control based on a first application program interface which is configured in advance, wherein the user-defined control is not a subclass of a user interface view, and the first application program interface is used for realizing the access of the barrier-free screen reading program on the user-defined control; and when the popup view appears in the IOS equipment, calling a barrier-free screen reading program to read the popup view based on a second application program interface which is configured in advance, wherein the second application program interface is used for realizing the focusing and the access of the barrier-free screen reading program to the popup view.
Optionally, 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 an implementation interface of the single view or instantiation code of the single view so as to realize the barrier-free access of the barrier-free screen reading program to the custom control; when the user-defined control is a view container comprising a plurality of sub-views, setting the accessibility state of each sub-view in the view container in an implementation interface of the view container so as to realize barrier-free access of the barrier-free screen reading program to the user-defined control.
Optionally, setting an accessibility state of the single view in an implementation interface of the single view includes: implementing a user interface element barrier-free access protocol in an implementation interface of the single view, wherein the user interface element barrier-free access protocol is used to enable access to the single view by the barrier-free screen reading program; in "the single view is clear to access the element" return "yes".
Optionally, setting an accessibility state of the single view in instantiation code of the single view comprises: assigning a value to the barrier-free access element attribute corresponding to the single view; the "the single view is unobstructed access element" is set to "yes".
Optionally, setting an accessibility state of each view in the view container in an implementation interface of the view container includes: implementing a user interface view container barrier-free access protocol in an implementation interface of the view container, wherein the user interface view container barrier-free access protocol is used for implementing access of the barrier-free screen reading program to each sub-view in the view container.
Optionally, implementing a user interface view container barrier-free access protocol in an implementation interface of the view container includes: defining a variable array; creating a corresponding number of barrier-free access elements based on the number of sub-views in the view container, specifying attributes of the barrier-free access elements based on information of the sub-views, and adding the barrier-free access elements to the variable array, wherein the barrier-free access elements are used for realizing access of the barrier-free screen reading program to the sub-views corresponding to the barrier-free access elements; in "the view container is barrier-free access element" return "no"; returning the number of the sub-views supporting barrier-free screen reading; returning the directory corresponding to the child view supporting barrier-free screen reading; and returning the barrier-free access element attribute under the directory.
Optionally, the second application program interface configuring process includes: and setting the property that the barrier-free access view is the popup window corresponding to the popup window view as 'yes', so as to focus the focus of the barrier-free screen reading program to the popup window view and access the popup window view.
According to another aspect of the embodiments of the present application, there is also provided an obstacle-free screen reading device, including: the system comprises a first screen reading module, a second screen reading module and a third screen reading module, wherein the first screen reading module is used for responding to touch operation of a target object on a user-defined control in the IOS equipment and calling a barrier-free screen reading program to read the screen of the user-defined control based on a first application program interface which is configured in advance, the user-defined control is a subclass of a user interface view, and the first application program interface is used for realizing access of the barrier-free screen reading program on the user-defined control; and the second screen reading module is used for calling a barrier-free screen reading program to read the screen of the popup view based on a second application program interface which is configured in advance when the popup view appears in the IOS device, wherein the second application program interface is used for realizing focusing and accessing of the barrier-free screen reading program to the popup view.
According to another aspect of the embodiments of the present application, there is also provided a processor, configured to execute a program, where the program executes the barrier-free screen reading method described above.
According to another aspect of embodiments of the present application, there is also provided an electronic device, including one or more processors and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the above-mentioned barrier-free screen reading method.
In the embodiment of the application, corresponding application program interfaces are configured in advance and are respectively used for realizing the access of a barrier-free screen reading program to a user-defined control and the focusing and accessing of the barrier-free screen reading program to a popup view, so that the IOS equipment can respond to the touch operation of a target object to the user-defined control, the barrier-free screen reading program is called based on a first application program interface to read the user-defined control, and when the popup view appears in the IOS equipment, the barrier-free screen reading program is called based on a second application program interface to read the popup view, thereby solving the technical problems that the barrier-free screen reading function cannot be realized for the user-defined control in the IOS equipment, and the barrier-free focus penetration is difficult to realize when the page layout is complex.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic flow chart of a barrier-free screen reading method according to an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating an unobstructed access to information provided according to an embodiment of the application;
fig. 3 is a schematic structural diagram of an obstacle-free screen reading device according to an embodiment of the present application;
fig. 4 is a schematic diagram of an electronic device provided according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For a better understanding of the embodiments of the present application, some of the terms or expressions appearing in the course of describing the embodiments of the present application are to be interpreted as follows:
IOS voice over function: 1) sliding browsing: sliding left or right, and switching focus among various contents on the screen; 2) touch browsing: touching the screen with a single finger, and dragging the finger to slide over the content until the focus moves to the required content; 3) activating the selected item: double clicking at any position on the screen; 4) scrolling the screen or list: the method comprises the steps of firstly focusing a voice-over focus on any element in a region needing to be scrolled, and then rapidly sliding on a screen by three fingers at the same time.
UIkit: the UIKit provides comprehensive HTML, CSS and JS components, is simple to use and is easy to customize and expand.
UIView (user interface view): the UIView is a basic element forming a picture, is a quadrangle with a position attribute and a certain size, generally has a background color, and can contain content such as character strings or pictures. UIView may have a subclass of UIView types, so UIView may be easily added to UIView to create various pictures.
Accessibility (barrier free access programming interface): two informal protocols and one class are generally included, as follows:
uiaccess availability (user interface barrier free access): and the object implementing the UIAccessability protocol reports the barrier-free access state (namely whether barrier-free access exists) of the object, provides descriptive information about the object, and implements the UIAccessability protocol by standard UIKit controls and views under the default condition.
Uiaccessiitycontainer (user interface view container unobstructed access): informal agreements, a subclass commonly used for UIView, may have some of the child UIs it contains accessed as separate elements. This protocol is useful when the child objects contained in a view are not a subclass of UIView, resulting in an inability to be accessed automatically and without obstruction.
Uiaccessitivelement (user interface element accessible): class, which by default implements the uiaccess protocol, may create an instance of the class for an object that cannot be accessed automatically and without obstruction (e.g., an object that is not a subclass of UIView or does not exist) so that it may be accessed without obstruction.
The attribute describing the user interface barrier-free access element is the core of uiaccess capability, and VoiceOver provides corresponding attribute information when a user accesses or interacts with a control or view. Uiaccess identity defines the following attributes:
label: a short localization word or phrase that is used to briefly describe the control or view, but not to define the element type. Such as "add" or "play".
Traits (characteristics): a combination of one or more individual features, each feature describing some aspect of the state, behavior, or use of the element. For example, an element appears as a Keyboard Key and is currently Selected, and this element may use a combined feature of Keyboard Key (Keyboard Key) and Selected (Selected).
Hint (cue): a brief, localized phrase that describes the result of an element action, such as: "add title" or "open shopping list".
Frame (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.
Value: a current value of an element when the value cannot be presented using the tag. For example, the label for a slider bar may be "speed," but its current value may be "50%".
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 presentation, analyzed data, etc.) referred to in the present disclosure are information and data authorized by the user or sufficiently authorized by each party.
The solution of the present application is described below with reference to preferred examples.
Example 1
In accordance with an embodiment of the present application, there is provided an unobstructed screen reading method for application to an IOS device, it being noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.
Fig. 1 is a schematic flow chart of an alternative barrier-free screen reading method according to an embodiment of the present application, and as shown in fig. 1, the method at least includes steps S102-S106, where:
step S102, responding to the touch operation of a target object on a user-defined control in the IOS equipment, and calling a barrier-free screen reading program to read the screen of the user-defined control based on a first application program interface which is configured in advance, wherein the user-defined control is not a subclass of a user interface view, and the first application program interface is used for realizing the access of the barrier-free screen reading program to the user-defined control.
The barrier-free screen reading program can be VoiceOver, which serves as a medium between a user interface in application and user touch control, and can provide audio description for views, controls and the like in application, so that a user can obtain corresponding voice prompt information only by touching a screen, and can completely control equipment without watching the screen, namely, barrier-free screen reading is realized.
Since the custom control is usually not a subclass of the ui view, and cannot be accessed by VoiceOver automatically without any obstacle, at this time, a corresponding first application program interface needs to be configured, and the access of VoiceOver to the custom control is realized by setting the accessibility state of the custom control.
Specifically, the custom control may be a single view or a view container including multiple sub-views, and the following respectively describes the configuration process of the first application program interface in these two cases.
When the user-defined control is a single view, two schemes are provided, and the accessibility state of the single view is set in an implementation interface of the single view or instantiation code of the single view respectively, so that the accessible of the user-defined control by a barrier-free screen reading program is realized.
When the accessibility state of the single view is set in the implementation interface of the single view, a barrier-free access protocol of the user interface element is implemented in the implementation interface of the single view, and the barrier-free access element is returned to 'yes' in the single view, wherein the barrier-free access protocol of the user interface element, namely UIAccessabilityElement, is used for realizing the access of a barrier-free screen reading program to the single view. Specific codes can be referred to as:
-(BOOL)isAccessibilityElement{
return YES;
}
optionally, when the accessibility state of the single view is set in the instantiation code of the single view, assigning a value to the barrier-free access element attribute corresponding to the single view; the "single view to unobstructed access element" is set to "yes". Specific codes can be referred to as:
view.isAccessibilityElement=YES
when the custom control is a view container comprising a plurality of sub-views, since the sub-views in the view container are required to be accessed rather than the view container, the accessibility states of the sub-views in the view container can be set in the implementation interface of the view container, so that the accessible screen reading program can access the custom control.
In some optional embodiments of the present application, a user interface view container barrier-free access protocol may be implemented in an implementation interface of a view container, where the user interface view container barrier-free access protocol is uiaccessibliitycontainer, and is used to implement access of a barrier-free screen reading program to each sub-view in the view container. Specifically, the following processes can be referred to:
defining a variable array NSMutableArray for storing the accessible elements;
establishing a corresponding number of barrier-free access elements based on the number of the sub-views in the view container, specifying the attribute of each barrier-free access element based on each sub-view information, and adding each barrier-free access element to a variable array, wherein each barrier-free access element corresponds to one UIAccessibilityElement and is used for realizing the access of a barrier-free screen reading program to the sub-views corresponding to the barrier-free access elements;
in the case that the "view container is an unobstructed access element" return "no", the specific code may refer to:
-(BOOL)isAccessibilityElement{
return NO;
}
and returning the number of the sub-views supporting barrier-free screen reading, wherein specific codes refer to:
-(NSInteger)accessibilityElement Count{
return[[self accessibleElements]count];
}
and returning a directory corresponding to the child view supporting barrier-free screen reading, wherein the specific code can refer to:
-(id)accessibilityElement At Index:(NSInteger)index{
return[[self accessibleElements]object At Index:index];
}
and returning the attribute of the barrier-free access element under the directory, wherein the specific code can refer to:
-(NSInteger)index Of AccessibilityElement:(id)element{
return[[self accessibleElements]index Of Object:element];
}
and step S104, when the popup view appears in the IOS device, calling a barrier-free screen reading program to read the popup view based on a second application program interface which is configured in advance, wherein the second application program interface is used for realizing focusing and accessing of the barrier-free screen reading program to the popup view.
It can be understood that when a popup view appears in a device, such as a popup prompt message, VoiceOver needs to focus on the popup view, and preferably implement barrier-free screen reading of the popup view, and at this time, a corresponding second application program interface needs to be configured to implement focusing and accessing of a barrier-free screen reading program to the popup view.
Specifically, when the second application program interface is configured, the property that the "barrier-free access view is a popup" corresponding to the popup view may be set to "yes", so that the focus of the barrier-free screen reading program is focused on the popup view, and the popup view is accessed. Specific codes can be referred to as:
-view.accessibilityViewIsModal=YES
alternatively, the user may also choose to manually focus the focus to the pop-up view.
In some optional embodiments of the present application, the specific descriptive clear access information may also be viewed based on an Interface Builder window provided by the IOS device, as shown in fig. 2, which shows the clear access information of the text field.
In the embodiment of the application, corresponding application program interfaces are configured in advance and are respectively used for realizing the access of a barrier-free screen reading program to a user-defined control and the focusing and accessing of the barrier-free screen reading program to a popup view, so that the IOS equipment can respond to the touch operation of a target object to the user-defined control, the barrier-free screen reading program is called based on a first application program interface to read the user-defined control, and when the popup view appears in the IOS equipment, the barrier-free screen reading program is called based on a second application program interface to read the popup view, thereby solving the technical problems that the barrier-free screen reading function cannot be realized for the user-defined control in the IOS equipment, and the barrier-free focus penetration is difficult to realize when the page layout is complex.
Example 2
According to an embodiment of the present application, there is also provided an unobstructed screen reading device for implementing the unobstructed screen reading method, as shown in fig. 3, the device at least includes a first screen reading module 30 and a second screen reading module 32, where:
the first screen reading module is used for responding to touch operation of a target object on a user-defined control in the IOS equipment, calling a barrier-free screen reading program to read the screen of the user-defined control based on a first application program interface which is configured in advance, wherein the user-defined control is a subclass of a user interface view, and the first application program interface is used for realizing access of the barrier-free screen reading program to the user-defined control.
Since the custom control is usually not a subclass of the ui view, and cannot be accessed by VoiceOver automatically without any obstacle, at this time, a corresponding first application program interface needs to be configured, and the access of VoiceOver to the custom control is realized by setting the accessibility state of the custom control.
Specifically, the custom control may be a single view or a view container including multiple sub-views, and the following respectively describes the configuration process of the first application program interface in these two cases.
When the user-defined control is a single view, two schemes are provided, and the accessibility state of the single view is set in an implementation interface of the single view or instantiation code of the single view respectively, so that the accessible of the user-defined control by a barrier-free screen reading program is realized.
When the accessibility state of the single view is set in the implementation interface of the single view, the barrier-free access protocol of the user interface elements is implemented in the implementation interface of the single view, and the barrier-free access element is returned to 'yes' in the 'single view', wherein the barrier-free access protocol of the user interface elements, namely UIAccessibilityElement, is used for implementing the access of the barrier-free screen reading program to the single view.
Optionally, when the accessibility state of the single view is set in the instantiation code of the single view, assigning a value to the barrier-free access element attribute corresponding to the single view; the "single view to unobstructed access element" is set to "yes".
When the custom control is a view container comprising a plurality of sub-views, since the sub-views in the view container are required to be accessed rather than the view container, the accessibility states of the sub-views in the view container can be set in the implementation interface of the view container, so that the accessible screen reading program can access the custom control.
In some optional embodiments of the present application, a user interface view container barrier-free access protocol may be implemented in an implementation interface of a view container, where the user interface view container barrier-free access protocol is uiaccessibliitycontainer, and is used to implement access of a barrier-free screen reading program to each sub-view in the view container. Specifically, the following processes can be referred to:
defining a variable array NSMutableArray for storing the accessible elements;
establishing a corresponding number of barrier-free access elements based on the number of the sub-views in the view container, specifying the attribute of each barrier-free access element based on each sub-view information, and adding each barrier-free access element to a variable array, wherein each barrier-free access element corresponds to one UIAccessibilityElement and is used for realizing the access of a barrier-free screen reading program to the sub-views corresponding to the barrier-free access elements;
in "view container is barrier free access element" return "no";
returning the number of the sub-views supporting barrier-free screen reading;
returning a directory corresponding to the child view supporting barrier-free screen reading;
the barrier-free access element attribute under the directory is returned.
And the second screen reading module is used for calling a barrier-free screen reading program to read the screen of the popup view based on a second application program interface which is configured in advance when the popup view appears in the IOS device, wherein the second application program interface is used for realizing focusing and accessing of the barrier-free screen reading program to the popup view.
When the popup view appears in the device, for example, the popup prompt message pops up, VoiceOver needs to focus a focus on the popup view, and preferably implements barrier-free screen reading of the popup view, at this time, a corresponding second application program interface needs to be configured to implement focusing and accessing of a barrier-free screen reading program to the popup view.
Specifically, when the second application program interface is configured, the property that the "barrier-free access view is a popup" corresponding to the popup view may be set to "yes", so that the focus of the barrier-free screen reading program is focused on the popup view, and the popup view is accessed.
In the embodiment of the application, based on the application program interface which is configured in advance, access of a barrier-free screen reading program to a user-defined control and focusing and access of the barrier-free screen reading program to a popup view are respectively realized, so that the IOS device can respond to touch operation of a target object to the user-defined control, the barrier-free screen reading program is called based on a first application program interface to read a screen of the user-defined control, and when the popup view appears in the IOS device, the barrier-free screen reading program is called based on a second application program interface to read the popup view, thereby solving the technical problems that barrier-free screen reading function cannot be realized for the user-defined control in the IOS device, and barrier-free focus penetration is difficult to realize when the page layout is complex.
Example 3
According to an embodiment of the present application, there is also provided a computer-readable storage medium on which a program is stored, the program implementing the barrier-free screen reading method in embodiment 1 when executed by a processor.
According to an embodiment of the present application, there is also provided a processor configured to run a program, where the program executes the barrier-free screen reading method in embodiment 1 when running.
According to an embodiment of the present application, there is also provided an electronic device, where the electronic device includes one or more processors and memories, and the memories are used to store one or more programs, and an alternative structure is shown in fig. 4, where the electronic device 40 includes at least a memory 400 and a processor 402, and when the programs are executed by the processor, the processor implements the barrier-free screen reading method in embodiment 1.
Specifically, when the program runs, the following steps can be executed: responding to touch operation of a target object on a user-defined control in the IOS equipment, calling a barrier-free screen reading program to read the screen of the user-defined control based on a first application program interface which is configured in advance, wherein the user-defined control is a subclass of a user interface view, and the first application program interface is used for realizing access of the barrier-free screen reading program to the user-defined control; and when the popup view appears in the IOS equipment, calling a barrier-free screen reading program to read the popup view based on a second application program interface which is configured in advance, wherein the second application program interface is used for realizing the focusing and the access of the barrier-free screen reading program to the popup view.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, electronic devices according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (10)

1. A barrier-free screen reading method is applied to IOS equipment and is characterized by comprising the following steps:
responding to a touch operation of a target object on a user-defined control in the IOS equipment, and calling a barrier-free screen reading program to read the screen of the user-defined control based on a first application program interface which is configured in advance, wherein the user-defined control is not a subclass of a user interface view, and the first application program interface is used for realizing the access of the barrier-free screen reading program on the user-defined control;
and when the popup view appears in the IOS equipment, calling a barrier-free screen reading program to read the popup view based on a second application program interface which is configured in advance, wherein the second application program interface is used for realizing the focusing and the access of the barrier-free screen reading program to the popup view.
2. The method of claim 1, wherein the first application program interface configuration process comprises:
when the custom control is a single view, setting the accessibility state of the single view in an implementation interface of the single view or instantiation code of the single view so as to realize the barrier-free access of the barrier-free screen reading program to the custom control;
when the user-defined control is a view container comprising a plurality of sub-views, setting the accessibility state of each sub-view in the view container in an implementation interface of the view container so as to realize barrier-free access of the barrier-free screen reading program to the user-defined control.
3. The method of claim 2, wherein setting the accessibility state of the single view in the implementation interface of the single view comprises:
implementing a user interface element barrier-free access protocol in an implementation interface of the single view, wherein the user interface element barrier-free access protocol is used to enable access to the single view by the barrier-free screen reading program;
in "the single view is clear to access the element" return "yes".
4. The method of claim 2, wherein setting the accessibility state of the single view in instantiation code of the single view comprises:
assigning a value to the barrier-free access element attribute corresponding to the single view;
the "the single view is unobstructed access element" is set to "yes".
5. The method of claim 2, wherein setting an accessibility state of each view in the view container in an implementation interface of the view container comprises:
implementing a user interface view container barrier-free access protocol in an implementation interface of the view container, wherein the user interface view container barrier-free access protocol is used for implementing access of the barrier-free screen reading program to each sub-view in the view container.
6. The method of claim 5, wherein implementing a user interface view container barrier-free access protocol in an implementation interface of the view container comprises:
defining a variable array;
creating a corresponding number of barrier-free access elements based on the number of sub-views in the view container, specifying attributes of the barrier-free access elements based on information of the sub-views, and adding the barrier-free access elements to the variable array, wherein the barrier-free access elements are used for realizing access of the barrier-free screen reading program to the sub-views corresponding to the barrier-free access elements;
in "the view container is barrier-free access element" return "no";
returning the number of the sub-views supporting barrier-free screen reading;
returning the catalog corresponding to the child view supporting barrier-free screen reading;
and returning the barrier-free access element attribute under the directory.
7. The method of claim 1, wherein the second application program interface configuration process comprises:
and setting the property that the barrier-free access view is the popup window corresponding to the popup window view as 'yes', so as to focus the focus of the barrier-free screen reading program to the popup window view and access the popup window view.
8. An accessible screen reading device, comprising:
the system comprises a first screen reading module, a second screen reading module and a third screen reading module, wherein the first screen reading module is used for responding to touch operation of a target object on a user-defined control in the IOS equipment and calling a barrier-free screen reading program to read the screen of the user-defined control based on a first application program interface which is configured in advance, the user-defined control is a subclass of a user interface view, and the first application program interface is used for realizing access of the barrier-free screen reading program on the user-defined control;
and the second screen reading module is used for calling a barrier-free screen reading program to read the screen of the popup view based on a second application program interface which is configured in advance when the popup view appears in the IOS device, wherein the second application program interface is used for realizing focusing and accessing of the barrier-free screen reading program to the popup view.
9. A processor, characterized in that the processor is configured to run a program, wherein the program is configured to execute the barrier-free screen reading method according to any one of claims 1 to 7 when running.
10. An electronic device comprising one or more processors and memory storing 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 of any one of claims 1-7.
CN202210122998.7A 2022-02-09 2022-02-09 Barrier-free screen reading method and device Pending CN114461172A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210122998.7A CN114461172A (en) 2022-02-09 2022-02-09 Barrier-free screen reading method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210122998.7A CN114461172A (en) 2022-02-09 2022-02-09 Barrier-free screen reading method and device

Publications (1)

Publication Number Publication Date
CN114461172A true CN114461172A (en) 2022-05-10

Family

ID=81413973

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210122998.7A Pending CN114461172A (en) 2022-02-09 2022-02-09 Barrier-free screen reading method and device

Country Status (1)

Country Link
CN (1) CN114461172A (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106406867A (en) * 2016-09-05 2017-02-15 深圳市联谛信息无障碍有限责任公司 Android system-based screen reading method and apparatus
CN111324275A (en) * 2018-12-17 2020-06-23 腾讯科技(深圳)有限公司 Broadcasting method and device for elements in display picture
CN113660376A (en) * 2021-07-13 2021-11-16 汕头大学 Barrier-free entity interface interaction system based on smart phone interface

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106406867A (en) * 2016-09-05 2017-02-15 深圳市联谛信息无障碍有限责任公司 Android system-based screen reading method and apparatus
CN111324275A (en) * 2018-12-17 2020-06-23 腾讯科技(深圳)有限公司 Broadcasting method and device for elements in display picture
CN113660376A (en) * 2021-07-13 2021-11-16 汕头大学 Barrier-free entity interface interaction system based on smart phone interface

Similar Documents

Publication Publication Date Title
US11399090B2 (en) Page control for history pages of browsed data
US10896192B2 (en) Allowing in-line edit to data table of linked data of a data store
KR100953806B1 (en) System and method for making user interface elements known to an application and user
CN106610774B (en) Webpage table editing method and device
Reid jQuery Mobile
CN107368511B (en) Information display method and device
CN112770187B (en) Shop data processing method and device
WO2016138510A1 (en) Contextual zoom
CN107590205A (en) A kind of service showing method, device and equipment
CN105573574A (en) Application interface navigation method and apparatus
CN110647272A (en) Display control method and device
CN110069734A (en) A kind of page assembly shows method and apparatus
CN105279431B (en) Method, device and system for recording operation information in mobile equipment
CN109582305B (en) Encoding method and device for mobile application page elements and electronic equipment
CN110262749B (en) Webpage operation method, device, container, equipment and medium
CN111897607A (en) Application interface loading and interaction method, device and storage medium
CN111381745B (en) Page switching method, device and equipment
CN114995699B (en) Interface interaction method and device
CN114461172A (en) Barrier-free screen reading method and device
CN107818000B (en) Operation method and device of page table
Freeman Pro jQuery 2.0
CN112597416A (en) Webpage element display method, device, server and storage medium
CN112558845A (en) Form operation method and form operation device
CN111198830B (en) Identification method and device of mobile storage equipment, electronic equipment and storage medium
CN114546554B (en) Control display method, device and equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination