Blog Post #6

Accessibility is an interesting topic to me because we frequently see websites (particularly older sites) made by professionals in certain fields (history, art, science) that are completely inaccessible due to poor coding choices. Oftentimes this is because of bright text on a garish background, dead links, autoplay audio (just why), and other aspects. It just goes to show that being an expert in one field doesn’t mean you are in all fields haha! I’m not a programmer but having my sites be accessible is important to me since I want others to stay and read my content. I decided to test the WAVE tool on my personal novel site and my class site. The class site didn’t bring forth many issues (mainly because it’s so simple, I think) but the WAVE tool did point out some issues on my novel website. My colors for my side bar are evidently too bright and this makes the menus less accessible. My art does tend to be colorful but I’ll need to find a better way to utilize it in my sidebar. I will be working on that this week! I also apparently linked my Instagram twice!

A bit of an aside, but I find it funny and kind of cute that the flashy, tacky internet graphics of the early 00s have actually become an aesthetic trend. I’ve been seeing people recreate the graphics of sites like Blingee and GeoCities as a kind of statement to their childhood!

[I, uh, have some work to do!]

In terms of data visualization, I quite liked the Charles Minard’s Napoleon’s March. It was well designed and easy to follow. Even for those who may not know much about this topic. Similarly, John’s blog mentioned the visualizations where you have an image that you can swipe showing before and after. I’ve always found these neat and have seen them fore things like the aftermath volcanic eruptions and tsunamis.

5 comments on Blog Post #6

  1. I agree with you that making your website accessible is key for those who may struggle with some kind of disability. I wonder, too, if making your website accessible could help you stand out more on, say, the job market. I can see my word press site as something that sticks with me for a considerable amount of time. Will accessibility help my website stand out more when I am looking for a job? Just a hypothetical idea in my mind.

  2. I had never considered accessibility as a function of user engagement. That line of reasoning actually makes sense when I think about it more: if the site is well-designed, readable, and easily navigable, it’s one fewer barrier separating visitors from any website’s real draw – the content. If any of those other features were more impediment than enabler, users would be more likely to just get their fix (or whatever it is that brought them to the site in the first place) and then leave instead of want to explore.

  3. I agree with your assessment of poor websites from the days-of-yore; definitely usually color choices and aggravating auto-play media. I always hate it when I click a tab and something starts playing, though of course it doesn’t harm me in a way it may someone with sensory issues.
    I think using your art on your site will work will with your current dark color scheme! Having that bright against a muted background could work well. As always, playing around with it is necessary anyway.


  4. Thank goodness that image gallery defaults have improved too, because those are an accessibility MESS. I remember all of the clever ways that artists came up with to show images in their web portfolios, which worked great…if you used the right browser, at the right resolution, and also, maybe don’t disable popups.


  5. I had only tried my class blog with WAVE when working on the technical activities this week. I just tried WAVE on my own artwork site and seeing a few things I need to tweak. It is really important that we think about these concepts of accessibility, especially when something like your website is how you are getting your work out there. I know what my next project will be.

    WAVE pointed out that I apparently forgot to link my instagram page on my site — oops!

Leave a Reply to Samantha Cancel reply

Your email address will not be published. Required fields are marked *