Since development of unity access has gone so well, I have been able to have most of the basic features built. This means that I was able to begin testing it to see if it would be viable to use in the long run.
I did this by building a basic first person seen.
Building The Scene
I started with a blank unity seen and created a capsule, using the game objects menu in the menu bar.
I then used the accessible hierarchy to find the capsule.
I then renamed it to player.
Next, I added the components to the player object that will be needed for the game.
I then used the same process to add a ground and 2 walls.
overall, I found the new plugin to be much easier than using unity's editor or writing the code to create each object. However, there is still room for improvement.
what to work on next
Now that I have the basic features in place I need to work on a way for the unity access plugin to be integrated into the editor asset system. At the moment I have to move and rename assets in file explorer. This could cause reference errors if I forget to move a .meta file with the asset it is attached to.
I also want to build a material system. The alternative would be to write the code for the objects materials. However, a material system would give me added convenience when adding shaders or effects.
{% card %}
If you want to follow along with the development of Unity Access or check out the code, you can find the repository over on GitHub!
{% endcard %}
join the conversation
what problems have you faced when developing plugins for unity?
Have you done anything around accessibility?