>302 causes an update to the component data structure 404. As a result of the update, components of the attendees 308 such as the user identifiers 406A-406C and 408 are tagged within the component data structure 404 for transmission to the accessibility module 406. Conversely, components not associated with the attendees 308 such as the personal tray 306 are not tagged for transmission and are thus not communicated to the user via the computing device 114. Accordingly, the user identifiers 406A-406C and 408 are communicated to the user via utilizing the user's preferred modality such as audio, magnified visuals, haptic feedback and so forth. In this way, a user with disabilities can gain a sense of position and space with respect to fellow users within the three-dimensional environment 100.

Turning now to FIG. 4C, the user selects the presentation 310 from the component groups 302. In response, informational panels 410 and 412 are generated and presented within the three-dimensional environment 100 to identify the virtual screen 104 and any content currently being presented. Similar to the user identifiers 406A-406C and 408, the informational panels 410 and 412 are positioned within the three-dimensional environment 100 to be visually associated with the virtual screen 104. As shown, the informational panel 410 states that a presentation from Cornelia's desktop is currently displayed on the virtual screen three meters from the user. In addition, the informational panel 412 states that the attendee panel displaying various users appearing as a two-dimensional renderings of an image 102A-102D is five meters from the user. Consequently, in this example, components (e.g., user interface elements) that are displayed and/or read out are associated with a shared attribute such as “content presentation” in the 3D environment.

Furthermore, the selection of the presentation 310 component group 302 causes an update to the component data structure 404. Components associated with the presentation 310 such as the informational panels 410 and 412 are tagged within the component data structure 404 for transmission to an accessibility module 406. Other components not associated with the presentation 310 are not transmitted to the accessibility module 406. Accordingly, the informational panels 410 and 412 can be processed by an accessibility module 406 at a computing device 114 to enable a user with disabilities to gain a sense of space and orient themselves within the virtual environment 100 with respect to the virtual screen 104.

As shown now in FIG. 4D, the user selects the room information 312 from the component groups 302. In response, additional informational panels 414A-414E are generated and positioned within the three-dimensional environment 100. The informational panels 414A-414E provide additional information on the appearance and spaces within the three-dimensional environment 100. For example, the informational panel 414A states that the user currently in conference room A which comprises a glass ceiling, brick walks, glass windows, and two breakout rooms to facilitate small group meetings. In addition, the informational panel 414A states that the current lighting in the room is bright. Similarly, the informational panel 414D states that the meeting includes four seats and that one seat is available. In this way, a blind or visually impaired user can visualize the three-dimensional environment 100 without necessarily viewing the space physically. Other informational panels 414B, 414C, and 414E provide information on additional features of the three-dimensional environment 100 in terms of their distance to the user. For instance, the informational panel 414C states that break room 1 is ten meters to the front right of the user. Consequently, in this example, components (e.g., user interface elements) that are displayed and/or read out are associated with a shared attribute such as “virtual environment composition” (e.g., the layout or arrangement of less important aspects of the room—walls, windows, tables, etc.)

In addition, the user selection of the room information component group 312 causes an update to the component data structure 404. Components of the room information component group 312 such as the informational panels 414A-414E are tagged within the component data structure 404 for transmission to the accessibility module 406. Conversely, components not associated with the room information 312 group are not tagged for transmission to the accessibility module 406. The informational panels 414A-414E are then processed by the accessibility module 406 and communicated to a user via the computing device 144 (e.g., through a screen reader). Stated another way, selecting the room information component group 312 can cause the system to produce and transmit a summary of the three-dimensional environment 100 to the user. This further enhances the user's sense of space within the three-dimensional environment 100 and empowers users with disabilities to richly interact with the space.

By presenting information in a layered, hierarchical format using the component groups 302, the disclosed techniques improve the quality of the user experience for users with disabilities (e.g., blind, visually impaired). For instance, a three-dimensional environment 100 can be highly complex containing many objects, renderings of users, virtual screens, additional rooms, and so forth. Rather than bombard a blind user with disjointed information, the component groups 302 improve the user's perception of the space by organizing the constituent components of the three-dimensional environment 100 into well-defined layers based on shared attributes (e.g., session, info, UI, user renderings). Moreover, by empowering users with disabilities with options for customizing how and when to receive information, the disclosed techniques can provide equity in experience for all users.

Turning now to FIG. 5, aspects of an accessibility environment 502 for creating and customizing a three-dimensional object 504 are shown and discussed. In various examples, a three-dimensional experience (e.g., a 3D real-time development platform such as UNITY) such as an avatar customizer is translated into a user accessible experience such as a two-dimensional experience (e.g., in HTML) to accommodate various user needs. Similar to the above examples, this can be accomplished by translating a three-dimensional environment 505 (e.g., a wardrobe) using a translation module 507. For example, a user with limited mobility may not be able to utilize handheld remotes to interact with a three-dimensional experience and require simplified inputs via a keyboard. In another example, a visually impaired user can utilize a screen reader to navigate user interfaces thereby requiring a transformation of the three-dimensional environment 505 for interoperability with the screen reader.

As shown, the accessibility environment 502 includes a main menu 506 encapsulating broad categories of functionality in which a user can advanced through and select a category with a first user input. For instance, the main menu 506 includes a section for the figure of the three-dimensional object 504, in this case, a user avatar. The figure defines general appearance such as gender, facial features, and other aspects. In the current example, the user is focused on the wardrobe section in which the user can select clothing items, accessories, and other components of their avatar object 504. Within the wardrobe section, the user can then select from a component group sub-menu 508 such as the base layer component group 510. The base layer component group 510 further comprises a plurality of components 512 including clothing items such as shirts which the user can place on their avatar object 504.

Utilizing a component selector 514 and a well-defined flow through the components 512 as indicated by the arrows, the user can utilize a simple input (e.g., arrow keys) to advance through the components 512. In addition, a current component 516 indicates which component 512 is presently highlighted by the component selector 514 (e.g., a short sleeve polo). Furthermore, the accessibility environment 502 can receive additional inputs for customizing the appearance of the current component 516 such as the color 518 although other aspects of the component can be modified as well (e.g., size). By providing another user input, the user can subsequently confirm selection of the current component 516. The final selected component 520 is then applied to the three-dimensional object 504.

Organizing what was originally a three-dimensional experience into a hierarchical flow of menus within an accessibility environment 502 enables processing by an accessibility module 406 similar to the examples described above. For instance, the accessibility module 406 can be a screen reader which utilizes audio to inform a user of their current location within the menus (e.g., main menu 506, component group sub-menu 508, components 512). In another example, the accessibility module 406 is a simplified input system for accommodating users with limited dexterity and/or mobility. In still another example, the accessibility module 406 is a force feedback device that provides a haptic force for informing the user of their environment. Providing the hierarchical menus to the simplified input system improves the efficiency of the accessibility module 406 and thereby the overall experience for users with disabilities.

Proceeding to FIG. 6A, another example of an interaction flow 600 for interacting with a plurality of spaces 602A-602E within in an accessibility environment 604. In various examples, a space 602A can be a three-dimensional space 100 such as the ones described above. As a user can be involved in different spaces 602A-602E, the translation module 606 can extract data from multiple three-dimensional environments 608 to construct the accessibility environment 604.

As shown in FIG. 6A, a user can interact with the accessibility environment 604 by selecting a space 602A. This can be achieved through any combination of input modality and assistive technology that accommodates the unique situation of each user. For instance, a user who is blind can utilize keyboard inputs and a screen reading to cycle through the spaces 602A-602E assisted by a screen reader via the accessibility module. In another example, the user may utilize voice inputs to interact with the accessibility environment 604. Accordingly, the user can say the name of the space 602A to make their selection (e.g., “development team meeting space”) and proceed to similarly interact with various entities contained in the space 602A.

Within a space 602A, the user can subsequently select from a set people 610A-610F and/or objects 612A-612C which can be grouped based on an entity type (e.g., people, inanimate objects). The set of people 610A-610F and objects 612A-612C can be analogous to and function similarly to the component group submenu 508 and component selector 514 discussed above. Namely, that people 610A-610F and objects 612A-612C can be considered components of a space 602A. As will be discussed below, selecting a person 610B from the set of people 610A-610F can expose a set of interactions that the user can take with respect to the person 610B. Similarly, the user can additionally select an object 612A to perform other interactions and/or invoke functionality within the space 602A. Moreover, an individual object 612A can have additional objects 614A and 614B nested within. The additional objects 614A and 614B may be physically associated with the object 612A (e.g., cushions on a couch). In this way, the accessibility environment 604 can enable a user with disabilities to take a layered approach to interacting with spaces 602A-602E, people 610A-610F, and objects 612A-614B.

Proceeding to FIG. 6B, in response to selecting an entity within the space 602A such as the person 610B, the accessibility environment 604 can surface a set of interactions 616A-616F that define various actions that can be taken with respect to the selected entity. For example, an interaction 616A can cause the user to follow the person 610B within the space 602A. Accordingly, a position of the user within the space 602A can change to match a position of the person 610B. Upon following the person 610B using the interaction 616A, the set of interactions 616A-616F may change as the position and thus the immediate context of the user has changed. For instance, now that the user is near the person 610B, an interaction 616B can enable the user to greet the person 610B. Another interaction 616C can enable the user to speak to the person 610B.

The set of interactions 616A-616F can also change and adapt to nearby objects 612A-612C. For example, an interaction 616C can enable the user to manipulate a nearby object 612A while speaking to a person 610B (e.g., a visual aid). In this way, the set of interactions 616A-616F can dynamically adjust to the immediate special and social context of the user. As such, rather than passively attending a space 602A, the user can be empowered to craft a personal experience for themselves through enhanced agency provided by the accessibility environment.

Furthermore, the interactions 616A-616F can be configured to react to events within the space 602A. For instance, a sound can cause the set of interactions 616A-616F to update and focus on a person 610B and/or object 612B associated with the sound. In a specific example, a person 610B may use an audio queue to get the attention of users within the space 602A. In response, an interaction 616D can be updated to enable the user to focus on the person 610B (e.g., turning an avatar). Moreover, sounds that cause the set of interactions 616A-616F to update can include a spatial component. For example, a user who is blind can receive audio via the accessibility module 406 that is formatted for providing a sense of directional perception (e.g., panned right).

Moreover, the interactions 616 can continuously update as a context of the user changes. For instance, in a social context, if the user is actively interacting with a person 610B, an interaction 616A can adapt accordingly to provide the user with options to enrich the interaction (e.g., virtual emotes) and/or switch focus to another person 610C. In another example, the interactions 616 can adapt to a spatial context of the user. For example, in response to a user moving into a section of a three-dimensional space 602A (e.g., a breakout room), the interactions 616 can enable the user to interact with nearby objects 612, people 610, and the like.

In addition, audio queues for updating the set of interactions 616A-616F can be customized for user preferences. For example, a user can configure the accessibility environment 604 to generate an audio queue in response to a person 610B approaching. Stated another way, if a person 610B moves within a threshold distance of the present location of the user, a spatial audio queue can be generated to indicate the direction of the approaching person 610B and the set of interactions 616A-616F can be updated accordingly. For example, in response to a person 610B approaching from the left, the accessibility module 406 can generate a spatial audio queue that appears to originate from the left of the user to draw their attention.

In another example, spatial audio can be triggered when a user faces, interacts with, or is within proximity of an object 612A. For instance, moving a cursor within the accessibility environment can translate to movement within the three-dimensional environment of a space 602A (e.g., turning around). In response to moving a cursor to change a direction, the accessibility module 406, along with the translation module 606, can trigger audio that is embedded in the space 602A for people 610 and/or objects 612 in the direction. For instance, spatial audio can be triggered in response to the user moving a cursor to turn and face a person 610B. If the person is speaking, the speech audio can be transmitted to the user via the accessibility module 406. Alternatively, a simple audio queue can be triggered to inform the user that there is a person 610B in the direction they are facing. Such audio queues can be customized to play for different events and/or triggers. In this way, the set of interactions 616A-616F can enable a user who is disabled to richly interact with the three-dimensional environment of a space 602A.

Turning now to FIG. 7, aspects of a routine 700 for translating a three-dimensional environment to an accessibility environment to enable interoperability between a three-dimensional experience and accessibility tools is shown and described. With reference to FIG. 7, the routine 700 begins at operation 702 where the system extracts component groups from a three-dimensional environment. Each component group includes components having a shared attribute. For example, the shared attribute is a component type (e.g., UI elements, user renderings, furniture). In another example, the shared attribute is location (e.g., left side of the room, right side of the room). In still another example, the shared attribute is a geometrical boundary (e.g., components within a certain area of a room) or other virtual constraint.

Next, at operation 704, the system constructs a flow hierarchy for the component groups.

Then, at operation 706, the flow hierarchy is output in an accessibility environment (e.g., a two-dimensional menu, an auditory environment).

At operation 708, the system receives a first user input via the accessibility environment indicating a selection of one of the component groups.

Next, at operation 710, in response to the first user input, the system shifts a focus to the components comprising the selected component group.

Subsequently, at operation 712, the system receives a second user input in response to the shifted focus indicating a selection of a component from the component group.

Finally, at operation 714, the system invokes functionality within the three-dimensional environment associated with the selected component.

Turning now to FIG. 8, aspects of a routine 800 for utilizing an accessibility environment to create an object for use in a three-dimensional environment are described. With reference to FIG. 8 the routine 800 begins at operation 802 where a system receives a first user input at a main menu indicating a selection of a category of functionality within the three-dimensional environment.

Next, at operation 804, the system extracts a plurality of components associated with the selected category of functionality.

Then, at operation 806, the extracted components are grouped based on a shared attribute to generate component groups where each component group comprises a respective plurality of components.

Proceeding to operation 808, the system outputs a component group sub-menu comprising the component groups.

Next, at operation 810, the system receives a second user input indicating a selection of one of the component groups from the sub-menu.

Then, at operation 812, in response to the second user input, the system outputs a component selector to shift a focus to the plurality of components within the selected component group.

At operation 814, the system receives a third user input via the component selector indicating a selection of a component.

Finally, at operation 816, in response to the third user input, the system applies the selected component to the object. In addition, operations 810-816 can be repeated until the object (e.g., a user avatar) is fully customized to the user's liking.

For ease of understanding, the processes discussed in this disclosure are delineated as separate operations represented as independent blocks. However, these separately delineated operations should not be construed as necessarily order dependent in their performance. The order in which the process is described is not intended to be construed as a limitation, and any number of the described process blocks may be combined in any order to implement the process or an alternate process. Moreover, it is also possible that one or more of the provided operations is modified or omitted.

The particular implementation of the technologies disclosed herein is a matter of choice dependent on the performance and other requirements of a computing device. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These states, operations, structural devices, acts, and modules can be implemented in hardware, software, firmware, in special-purpose digital logic, and any combination thereof. It should be appreciated that more or fewer operations can be performed than shown in the figures and described herein. These operations can also be performed in a different order than those described herein.

It also should be understood that the illustrated methods can end at any time and need not be performed in their entireties. Some or all operations of the methods, and/or substantially equivalent operations, can be performed by execution of computer-readable instructions included on a computer-storage media, as defined below. The term “computer-readable instructions,” and variants thereof, as used in the description and claims, is used expansively herein to include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like.

Thus, it should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof.

For example, the operations of the routines 700 and 800 can be implemented, at least in part, by modules running the features disclosed herein can be a dynamically linked library (DLL), a statically linked library, functionality produced by an application programing interface (API), a compiled program, an interpreted program, a script, or any other executable set of instructions. Data can be stored in a data structure in one or more memory components. Data can be retrieved from the data structure by addressing links or references to the data structure.

Although the illustration may refer to the components of the figures, it should be appreciated that the operations of the routines 700 and 800 may be also implemented in other ways. In addition, one or more of the operations of the routines 700 and 800 may alternatively or additionally be implemented, at least in part, by a chipset working alone or in conjunction with other software modules. In the example described below, one or more modules of a computing system can receive and/or process the data disclosed herein. Any service, circuit, or application suitable for providing the techniques disclosed herein can be used in operations described herein.

FIG. 9 shows additional details of an example computer architecture 900 for a device, such as a computer or a server configured as part of the cloud-based platform or system 100, capable of executing computer instructions (e.g., a module or a program component described herein). The computer architecture 900 illustrated in FIG. 9 includes processing system 902, a system memory 904, including a random-access memory 906 (RAM) and a read-only memory (ROM) 908, and a system bus 910 that couples the memory 904 to the processing system 902. The processing system 902 comprises processing unit(s). In various examples, the processing unit(s) of the processing system 902 are distributed. Stated another way, one processing unit of the processing system 902 may be located in a first location (e.g., a rack within a datacenter) while another processing unit of the processing system 902 is located in a second location separate from the first location.

Processing unit(s), such as processing unit(s) of processing system 902, can represent, for example, a CPU-type processing unit, a GPU-type processing unit, a field-programmable gate array (FPGA), another class of digital signal processor (DSP), or other hardware logic components that may, in some instances, be driven by a CPU. For example, illustrative types of hardware logic components that can be used include Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Products (ASSPs), System-on-a-Chip Systems (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

A basic input/output system containing the basic routines that help to transfer information between elements within the computer architecture 900, such as during startup, is stored in the ROM 908. The computer architecture 900 further includes a mass storage device 912 for storing an operating system 914, application(s) 916, modules 919, and other data described herein.

The mass storage device 912 is connected to processing system 902 through a mass storage controller connected to the bus 910. The mass storage device 912 and its associated computer-readable media provide non-volatile storage for the computer architecture 900. Although the description of computer-readable media contained herein refers to a mass storage device, the computer-readable media can be any available computer-readable storage media or communication media that can be accessed by the computer architecture 900.

Computer-readable media includes computer-readable storage media and/or communication media. Computer-readable storage media includes one or more of volatile memory, nonvolatile memory, and/or other persistent and/or auxiliary computer storage media, removable and non-removable computer storage media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Thus, computer storage media includes tangible and/or physical forms of media included in a device and/or hardware component that is part of a device or external to a device, including RAM, static RAM (SRAM), dynamic RAM (DRAM), phase change memory (PCM), ROM, erasable programmable ROM (EPROM), electrically EPROM (EEPROM), flash memory, compact disc read-only memory (CD-ROM), digital versatile disks (DVDs), optical cards or other optical storage media, magnetic cassettes, magnetic tape, magnetic disk storage, magnetic cards or other magnetic storage devices or media, solid-state memory devices, storage arrays, network attached storage, storage area networks, hosted computer storage or any other storage memory, storage device, and/or storage medium that can be used to store and maintain information for access by a computing device.

In contrast to computer-readable storage media, communication media can embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. As defined herein, computer storage media does not include communication media. That is, computer-readable storage media does not include communications media consisting solely of a modulated data signal, a carrier wave, or a propagated signal, per se.

According to various configurations, the computer architecture 900 may operate in a networked environment using logical connections to remote computers through the network 920. The computer architecture 900 may connect to the network 920 through a network interface unit 922 connected to the bus 910. The computer architecture 900 also may include an input/output controller 924 for receiving and processing input from a number of other devices, including a keyboard, mouse, touch, or electronic stylus or pen. Similarly, the input/output controller 924 may provide output to a display screen, a printer, or other type of output device.

The software components described herein may, when loaded into the processing system 902 and executed, transform the processing system 902 and the overall computer architecture 900 from a general-purpose computing system into a special-purpose computing system customized to facilitate the functionality presented herein. The processing system 902 may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, the processing system 902 may operate as a finite-state machine, in response to executable instructions contained within the software modules disclosed herein. These computer-executable instructions may transform the processing system