Reflect on your developing understanding of web accessibility in a blog post on your portfolio site, covering the questions above: something you learned from experience videos, one identified technical feature, one identified conceptual feature, one feature you hadn’t considered before, what errors your portfolio site included (if any) and how you fixed them or are still figuring out how to fix them.
Experience videos: One thing I learnt from these videos is the importance of notifications and feedback from websites. Error messages are almost always unclear and frustrating to everyone, and even more so to people unfamiliar with technology. I hadn’t considered how important it was before to make websites responsive.
Technical feature: Non-text content items.Most of these could be addressed using some software.
Conceptual feature: Audio description requiring a ‘radio-style’ narration would require a conceptual change in the recording of the content itself.
One I hadn’t considered before: Audio playing as soon as you open a page. This is something that is somewhat normalized with apps like TikTok, Reels,etc. that play videos as soon as you play them, but I see how it is a major accessibility concern.
I used the WAVE AIM accessibility checker and it mostly came up with very low contrast errors. There were also a few redundant link errors. I fixed most of the low contrast errors by changing the font color or the background image. I plan to fix the issue with the links when I restructure my website in the next week or so.
0 Comments