Hi Markus,
I like how you phrased your revelation on inclusive design, realizing that you should start creating something with the anticipation of needing to accommodate different needs instead of taking something that already exists and trying to make it accessible after the fact. What you are essentially doing is using the backwards design method we learned about in the last module to now think about creating things for accessibility, so that’s great!
I’m glad text-to-speech tools worked out for you and that you found them helpful. I cannot absorb information from just listening, and, as you mentioned, the robotic voice doesn’t help much either.
And yes, the wave accessibility tool was disappointing. We had a very similar experience.
To answer your question, there are many tools online that can check how your work might look to someone who is colourblind. Some of them can be helpful in different ways, such as checking the contrast of your text or how different colours will read. I use these mostly for design purposes.
When you say you will try to use generic and plain text, what do you mean exactly? If by that you mean limiting yourself and your writing to very simple sentence structures and less flowery language I think you would be doing a disservice to yourself and others. Making something accessible doesn’t mean dumbing it down. But if you meant like fonts then yes I agree haha.
Leave a Reply
You must be logged in to post a comment.