
Hubs works towards the Mozilla mission of keeping the internet open and accessible to all by providing an ecosystem for communities, organizers, educators, artists, and developers to easily build and deploy innovative web content in a social, open manner.
The Mozilla Hubs team highly values the accessibility community’s voice in helping to make Mozilla Hubs a more usable and accessible product. Dan Fernie-Harper from Mozilla Hubs Design and People Experiences team will present an update on the past, present, and future of accessibility in Mozilla Hubs, speaking about the user experience design process.
Dan Fernie-Harper is a Design Content Creator on the Hubs Design and People Experiences team. He has a passion for inclusive emerging and immersive technologies complimenting his love of audio-visual production, traditional and digital illustration, and 3D animation and modeling.
Here are the presentation slides with requested links.
Check out the following highlights from this presentation:
- What is Mozilla Hubs?
- A look at Mozilla Hubs design team approach
- An exploration of Mozilla Hubs’ past
- Where Mozilla Hubs is today
- What’s the future of Mozilla Hubs?
- Q&A: How long does it take to implement an accessible Mozilla Hubs feature?
Transcript: The Past, Present and Future of Accessibility in Mozilla Hubs - Dan Fernie-Harper
DAN FERNIE-HARPER: Hi, everyone. My name is Dan Fernie-Harper. It's a pleasure to be here. I'm extremely grateful to the A11yVR team for inviting me today.
I live in Auckland, New Zealand and I came to the organization with a background in traditional and digital illustration along with some years of audio/video and virtual reality production experience but I was relatively in the dark about accessible design. I'm still a no advice and me learning along the way but I feel very passionately about how we can make Hubs accessible to everyone who wants to use it. I consider myself incredibly lucky to be able to work with the individuals who create and tirelessly maintain this desktop platform.
So I'm here today to talk about our design process, the past, present, and future of accessibility Hubs and how Mozilla and the community can make Hubs a more user-presently product for all. So I wanted to start by giving a quick introduction to Hubs, our Hubs is a platform that allows people to connect safely on any device. To those watching the stream or recording, this virtual meetup is taking place on Hubs. The environment we're in was built by A11yVR team and the scene meeting -everyone has chosen an avatar, and here we can bring in and share images and video files and create and interact with 3D models but these features only scratch the surface of the tools.
Further than that it's a social experience engineer. To tailor their virtual space to their needs. What drives Hubs? I believe Hubs to be a powerful platform for a collaboration just on its own merits but there's a value-driven force behind it that allows Hubs to be a safer, and more inclusive tool and that force is Mozilla.
The Hubs philosophy draws heavily on the ten principles of the organization to guide our efforts. I won't run through all of these now but the Mozilla manifesto can be found online and I'll drop the link to the Hubs in the meetup chat. And Hubs is just another way how Mozilla is showing its ideas are contributing to make the Internet a better place for all. The Hubs design team.
So as the Hubs design team we are constantly evaluating the functionality, usability of the Hubs product. What does the product do? The usefulness of product features, maintainability and reliability, for example. Usability is a characteristic of the interaction between the user and the product, can I make the product do what I want it to do?
And user experience. So user experience considers the wider relationship between the product and the user in order to investigate the individual's personal experience of using it: how the person felt about the experience, what it meant to them, whether it was important to them and whether it set comfortably with their other values and goals. That is to say we put people as the driving force behind decision-making. Recommendations and designs that put users at the forefront of product development.
We are a hard-working by identifying gaps in opportunities in the product allowing us to bring out audiences wants, and needs into the design. So thank you for listening to my brief introduction about Hubs, our philosophy and description of our process. Providing an equitable experience sits high on the list of what the Hubs team wants to achieve with this product but it's still a work in progress and a fairly new product and platform but we feel we have a roadmap that we believe in and look forward to continuing to develop Hubs into a product that is setting a standard in accessible design.
I'd like to speak now to the ways Hubs and Mozilla have incorporated accessible design into the product. Historically, in the present and what we hope to achieve in the future. So in a way, accessibility has been baked into Hubs from the very beginning. Hubs is open-sourced and invites contributors to help improve the product.
This means that there's more opportunity for accessible design and feature implementation and ultimately to build a more inclusive product. If people find a bug, something that's not accessible or a feature request we invite them to review existing tickets to see if it's already in the pipeline or create an issue on our GitHub repo and our product team will address and prioritize it. We also have a board to facilitate feedback and conversation within the community.
Being powered by the web, it can be accessed from the browser or any device. As long as you have an Internet connection, you can create or join a room with only a few clicks. At the default level it is completely free and there is no need to create an account. This would seem like an easy enough task however, the steps to this process can act as a barrier to people with disabilities.
And Hubs also leverages existing browser functionality like compatible devices and keyboards when used on a desktop or laptop. This year in January, we implemented a new user-interface design scheme. This redesign includes a highly-requested feature of a persistent chat sidebar along with a more streamlined interface for mobile and desktop to align with industry standards. The work on improving this experience is still ongoing and that brings me to the present.
We feel we have a good grounding --bbut we realized we couldn't do it alone. There was a real feeling of excitement - we've featured concepts and designs so the community can help us deliver a product that people want and our plan is to do the same thing here. The cool-looking sci-fi avatar that I'm using was recently created by a Hubs community member @imaginer to show when the avatar is speaking. It expands indicating the source of the sound.
Future Hubs. So I can't say exactly what features, changes, and additions we'll be implementing but I know we have loads of suggestions from internal work and from our community and that extensive exploration is being done to improve the work overall. Some of the work that I can speak about such things like the color palette that is more accessible, more options and themes including an alternate dark mode, high-contrast mode and a simplified light mode alongside a great deal of progress for users in audio and video and this slide here shows an example of a concept for a dark-mode user interface.
Accessibility when using Hubs with a VR headset is an important area for us moving forward. Sickness is a great deal and the design team are exploring ways to implement features that mitigate the effects. Hand tracking is another interesting avenue to go down. We believe that this can not only improve more human expression and interaction but possibly help make sign language in virtual spaces available.
There's a prototype available through We beXR, the We beXR emulator that includes support for hand tracking and leverages Google MediaPipe. I hope one day soon we can integrate such tools as text-to-speech captioning in Hubs. This is an often-requested feature and I and a lot of users would like to have this feature without workarounds with third-party providers. Google's speech-to-text functionality is strong and this year there are plans to publish a toolkit to help people, users, and organizations use deep speech to invent their own voice-based solutions.
I believe it's only a matter of time until Hubs and its contributors find a way to incorporate it. As I come to the end of this presentation, I have to say there are a range of accessibility needs and requests that I haven't touched on today and we're working hard to solve them. Control and navigation improvements, focus layers between 2D and 3D and visual cues for audio zones. The list goes on.
I would also like to reiterate that Mozilla has a long history of valuing its communities and we wholeheartedly agree that they build a better product. So reach out to us on our Discord server and our GitHub for discussions and feature requests. Thank you to everyone who has joined in the conversation along the way so far. A huge thank you to Thomas Logan and the A11yVR team for continuing to hold events such as this and many, many thanks to everyone that came along today.
The future is accessible. Happy Global Accessibility Awareness Day!
THOMAS LOGAN: Thank you very much, Dan and that's an excellent presentation. So now we'll be taking questions either from you all on the YouTube stream or here in this space. For those of you in this space it's fine to chat your question or come off of mute and ask the question. I'll just get started, Dan, with a question for the sign language example that you were talking about and you mentioned that emulator extension.
Do you have a link for where that is or how we can find out more? DAN FERNIE-HARPER:I don't happen to have that on hand. I will have to post one up in the chat. Let me just have a quick look for it.
THOMAS LOGAN: Sure and we can post that into the notes of the meeting, afterwards too, as well, afterwards but it would be definitely interesting to check that out.
DAN FERNIE-HARPER: For sure. Thanks, Thomas.
THOMAS LOGAN: On average how long does it take hubs an accessibility feature, i.e. for research, design, developmentt testing, and user testing? DAN FERNIE-HARPER:That's a greay question. It really depends on the lift that all of the teams -- deasign, engineering and research teams have to take.
Simple stuff like UI stuff is a lot quicker to implement, but say something like captioning is a huge engineering lift, so we're always looking for ways to partner with our community and bring contributors on board to help speed up that process. I really couldn't give you an average feature request timeline.
THOMAS LOGAN: I think that is a difficult one. I know that in the events that we've held here. -when you all added the support to have the keyboard support for the reactions, that was something great for our event. So something like when you can press the one, two, three, four, or five for the reactions and I'm sure that was something that would take longer than changing, say, the color support in the UI but, um -we have another question here, Dan.
Is there a VPAT, voluntary product accessibility template available for Hubs?
THOMAS LOGAN: We remember the -when you all added the support to have the keyboard support for the reactions, that was something great for our event. So something like when you can press the one, two, three, four, or five for the reactions and I'm sure that was something that would take longer than changing, say, the color support in the UI but, um -we have another question here, Dan. Is there a VPAT, voluntary product accessibility template, available for Hubs?
DAN FERNIE-HARPER: Um, there isn't. I've seen this question and I quickly googled it because I had no idea what it was. And this is -this just highlights how connecting with our community can help implement new standards that will improve accessibility. So I'm going to bring this to the team and see what something like this could look like for Hubs.
So thank you to the -for the question on that.
THOMAS LOGAN: Um, I had another question, too, for your avatar that you mentioned -being able to have that kind of contrast for the audio display so that it's really clear that your avatar is speaking. Is that a link, too, that can be shared of the avatar and where the person is able to explain how they built it? It's really interesting.
DAN FERNIE-HARPER: Um, yeah, so I reached out to this Hubs user and asked if I could use the avatar for this presentation today. On our Discord channel, I think it was in the design channel... he posted it up just in the last couple of weeks. It is publicly available.
You can actually go and click on the link there and it will update your avatar. And from there, there's workarounds to be able to save it and to actually be able to get that model into Blendr and reverse engineer it so to speak but the design team is also looking into ways we can show off when someone's speaking so, yeah, really grateful. Someone from the community is already thinking about it and putting it into motion!
THOMAS LOGAN: Excellent! I know that, um, Matt here, I know that Matt's been working on something like interactive functionality in, like, WebXR in Hubs and like quiz functionality in Hubs or something like that. Are those sort of interactive features inside of Hubs are also something you're looking at for accessibility as well?
DAN FERNIE-HARPER: There is exploration into that, I can't speak too much as to what that looks like. But definitely there is progress being made on that front.
THOMAS LOGAN: Great, thanks! If you could wave a magic wand, what would the top three implementations to Hubs be and what is stopping it currently?
DAN FERNIE-HARPER: Um, first off, I would say captioning. To be able to have speech-to-text captions either 3D or 2D or a combination of both. That would be my number one choice. And what is stopping the implementation currently?
We need to do more research. It's a pretty big engineering lift, as well. It's really -time is really our biggest barrier at the moment. What else?
What other additions...? I like the idea of having objects in Hubs have interaction, sort of, qualities able to be sort of coded into them. Able to have sort of a door that is closed and able to interact with the actual door handle and open the door -that sort of thing. What would my third one be?
Yeah, this is a great question. I would love to see the capacity, like, room capacity increased and for there to be huge events with, like, 1,000 people. Yeah, in the room in the space interacting. What is stopping implementation?
It's quite a heavy load for the service. So I think time as we develop techniques for, like, how far away you need to be from someone before you start being able to start hearing them and interacting with them. Things like that could drop the load -the server load. Um, yeah, I have lists.
They would be my three top choices at the moment. Thank you for the great question.
THOMAS LOGAN: And those are great responses. We definitely have had that experience, you know, here in the event with the room capacity before. So that definitely does sound like a good thing but understandable that it's a challenging item to solve with, you know, every new person and avatar increases the load potentially. We have another question.
Here from Eric Balm. What's the best way to get involved with Hubs and provide feedback?
DAN FERNIE-HARPER: So that would be our GitHub repo and discussion board on there or our Discord server. We have a range of channels covering many different sort of areas. I would say get in there and communicate with the people using it and look out for our feedback forms on the accessibility and design channels there. Uh, we also have a community meetup every Friday and Saturday where I am, New Zealand.
So you can find that on our Discord channel, as well.
THOMAS LOGAN: And I can definitely echo that. Yeah, if you're interested in getting involved, that's been a huge reason for us doing accessibility virtual reality that we have loved hosting our events in Mozilla Hubs. The team is really responsive and does, you know, live the principle of being open and communicating with the community so we've -we've used those channels and had great success being able to communicate with the people, building, and creating this software and so I think, yeah, if you use those, you'll have a great experience and... you know, we're definitely excited to keep seeing what changes with Mozilla Hubs in the future and I'll just wrap up our event today with saying, you know, that we do believe all of these virtual-reality experiences, you know, they need to be accessible and there's lots of research, lots of opportunities
to improve and we're very happy, right, with what the Mozilla Hubs team is doing. And as I said at the start of the meetup, your input and feedback coming to our events every month, that is also something that we plan to continue sharing with the Hubs people. So if you don't join the Discord or GitHub, we'll be doing that and we'll also help take your thoughts and feedback to the team.