Skip to content
- After watching the keyboard compatibility, speech recognition, and text customization videos I found the slogan (“Essential for some, useful for all” ) at the end of all of them to be very compelling. When I think of accessibility, I think of chronic disabilities as opposed to temporary ones or people who simply prefer the more accessible format for other reasons. This distinction broadens the user base of accessible technologies a lot in my mind.
- Technical feature: change any decorative images to “background image” in the CSS code. Conceptual feature: videos should include narration so users would understand what is happening if only listening to the audio. New feature: don’t identify elements by color – I’m thinking of data graphs where some variable is denoted by color and how these could be made more accessible.
- On my portfolio website, the text on the home page does not have enough contrast with the background image itself. I’ll have to play around with different colors because I would still like to keep the image on my site.
- After this training, accessibility seems hard to implement at times because a lot of the elements for it actually aren’t visible on web pages. For example, needing certain headings on each page isn’t something you can automatically see because you’re able to change the formatting (font and size) of text to make it look like a title even if it’s H3. In cases like this, it’s very helpful to have the WAVE checker and I will be using that more often for my personal site and my project site.