In watching the accessibility stories, I was mainly struck by how much accessibility concerns were really about engaging multiple senses in case a user is unable to engage one or the other. This came to mind when I watched the videos on text-to-speech and video subtitles because both involved engaging with visuals (text) and sound (voiceover). The idea of having both instead of just one or the other includes a wider amount of users without drastically affecting the delivery of the content.
Programming a website to allow for text-to-speech bots to read it would be a technical feature. A more conceptual design feature would be general layout of the website, such as where navigation bars are placed and whether that placement changes depending on the viewing device.
To be honest, I hadn’t really considered labels for text boxes as accessibility features. Because they’re ingrained in most websites so people know what they’re supposed to type where, I just thought of them as basic web design principles.
My portfolio website is already in good shape according to the accessibility checker. The only issues came from some of my alt text for images, or lack thereof in some cases. There are not a lot of images on my website anyway, so this should be a quick fix.