Skip to Main Content

Accessibility Adventures: October 2020

In August, I posted about how I’ve recently discovered and have been falling in love with the world of digital accessibility. Here’s what I’ve been up to since then.

A refreshable braille display connected to a laptop computer.
Photo by Elizabeth Woolner on Unsplash


In August, I posted about how I’ve recently discovered and have been falling in love with the world of digital accessibility: “Accessibility Adventures: August 2020.” Here’s what I’ve been up to since then.

Science Fiction & Accessibility

I enjoyed this short post on science fiction and accessibility from Sheri Byrne-Haber. As someone who is into both of those, the title caught my eye, and apparently I’m not the only one. Sheri Byrne-Haber anecdotally notes that there seem to be many people who love both science fiction and accessibility, and she suggests that’s probably because of a common denominator: both science fiction and accessibility are “about building a future that does not yet exist.” This resonated with me. I do have other reasons I care about both of them, but this is definitely a shared theme that I return to quite often.

Accessibility Audits

I enjoyed reading “What to look for in an accessibility audit” by Glenda Sims on the Deque blog. It’s a highly detailed post about different types of accessibility audits and how they are conducted. I hadn’t come across someone talking about accessibility audits in this level of detail before, so I found it really interesting.

Accessible Certification

I enjoyed reading “Diversity, Equity and Inclusion: Including Disabled People in Digital Certification, Credentialing and Licensure” by Samantha Evans in Credentialing Insights. The post examines how disability justice and accessibility relate to the world of credentialing, certification, and licensure. At the end of the post, Samantha writes:

International Association of Accessibility Professionals (IAAP) is creating a coalition of credentialing organizations, certification groups, higher education, advocacy groups, psychometric exam/test delivery industry partners and accessibility professionals this fall. The hope in bringing these audiences together is to establish agreed upon terms, standards, best practices and resources that can advance accessibility and inclusion in these shared professions and industry.

That was exciting news to me! Accessibility and inclusion in the credentialing/certification/licensure space is important, and I’m glad to see that IAAP is working with the Institute for Credentialing Excellence and other groups to make this space more inclusive.

Assistive Technology Videos

I really enjoyed this post from Axess Lab: “Videos of people with disabilities using tech.” The post collects videos of people with disabilities using eye trackers, Xbox adaptive controllers, screen readers, and switch controls to play games, shop, edit videos, and write code. It’s a wonderful collection of videos, and watching them made me think about not only how cool assistive technology is, but also how important accessibility is. Assistive technology can be a great help, but if the underlying software isn’t accessibility written — for example, can you only use the software if you have a mouse, good vision, and fine motor control? — people using assistive technologies still won’t be able to access or use it.

Accessible & Inclusive Gaming

I enjoyed this Bloomberg article by Renata Geraldo about the growing market for accessibility in the gaming industry. Video games are a huge industry, one that often has not been (and isn’t) accessible to gamers with disabilities. There’s still a long way to go, but it’s cool to read about the progress that’s happening.

I also recently came across Accessible Gaming Quarterly, a zine dedicated to accessibility and disability within the tabletop RPG space. I haven’t had the chance to read it yet, but it looks awesome. As an accessibility nerd who is also a D&D player, this looks right up my alley.

On the topic of tabletop games and inclusive gaming, here’s an excerpt from my last SFF Adventures blog post:

I have another D&D essay I recommend: “D&D will change to address racism, but someone has already done the work” by Charlie Hall on Polygon. This essay examines how race in D&D is problematic and bigoted and looks at alternatives to the current system. In particular, this essay looks at Ancestry & Culture: An Alternative to Race in 5e by Eugene Marshall, which offers a critical and progressive way to rework race in D&D. In short, it looks like Marshall splits the problematic concept of race into biological ancestry and cultural heritage. Ancestry & Culture seems like (1) a cool, non-problematic way to rework race in D&D, and (2) a work of critical race theory disguised an an RPG game. I want to read Ancestry & Culture, but I haven’t gotten around to it yet. In the meantime, I recommend any D&D fan or anyone striving to be anti-racist to check out the essay on Polygon.


I recently listened to Disability Visibility: First-Person Stories from the Twenty-First Century, a new nonfiction anthology edited by Alice Wong. It’s very good! It’s a bunch of great essays on disability from a bunch of different perspectives. I loved how intersectional most of these essays were. I definitely recommend.

I also just read two books from A Book Apart: HTML5 For Web Designers by Jeremy Keith and Rachel Andrew and CSS3 for Web Designers by Dan Cederholm. In “web time,” these are old books. They were originally published in 2010 and had updated second editions released in 2016 and 2015, respectively. The age showed. For example, CSS3 for Web Designers focused mostly on using CSS3 modules for minor progressive enhancements and basically didn’t even touch on Grid layout, which is currently supported for over 95% of users. Despite the age, however, I actually did find these books quite useful. They were short, well-written, and easily digestible. They taught me about history and context that I previously didn’t know much about, such as introducing me to the Web Hypertext Application Technology Working Group (WHATWG). And they also introduced me to techniques that I didn’t really understand before, such as vendor prefixing. While I have had formal schooling that introduced me to computer programming and networking, my web design knowledge is all mostly self-taught, and these books did a good job of filling in some of my knowledge gaps.

Compliant or Conformant?

In my short time that I’ve been in the world of accessibility, I’ve already come across two words quite often: compliance and conformance. These words are used when referring to laws (such as the Americans with Disabilities Act or Section 508 or the Rehabilitation Act) as well as standards (such as the Web Content Accessibility Guidelines). I began to wonder if the two words can be used interchangably, or if there are any significant differences between the two, so naturally I did a web search.

I came across this post from about compliance/conformance that clearly differentiates between the two, and according to that post, in short, you must comply with the law, and technologies should conform to standards. I also looked up the definitions of these two words, which — while somewhat overlapping — also support that distinction. So it’s just that easy, right?

Not really. In practice, it seems the two words are often used interchangably. While the Web Content Accessibility Guidelines (WCAG) themselves do follow this distinction and refer only to conformance with the standard (not compliance), the A11y Project instead refers to WCAG in terms of compliance, and they’re not the only ones.

This is partially confusing because the two words sound similar and have largely similar meanings, but it’s also confusing because in order to comply with accessibility laws, you should conform to WCAG. Although WCAG isn’t a law, WCAG effectively has the power of law behind it (at least in the United States), so in some ways it does make sense to talk about WCAG compliance, rather than WCAG conformance.

I will do my best to use those words precisely (compliant to the law, conformant to standards), but I also want to recognize that it seems in practice these two words are often used interchangably.

I’ve been working to upgrade my tech skills with I completed their Responsive Web Design certification, and I’m currently working on JavaScript with them. Thus far, I’ve been really satisfied with their program. The interface works well for me, the content is nicely chunkable, and the curriculum exposes you to a sizable breadth of info with a gentle on-ramp. The Responsive Web Design certification also includes a set of challenges on applied accessibility, which I was glad to see. And that’s to say nothing of the fact that FreeCodeCamp is a nonprofit with tons of free content. I’m trying to stay focused on JavaScript right now, but their courses on front-end libraries and Python keep grabbing my attention.

Classless CSS Stylesheets

Recently, I was exporting a bunch of markdown notes to HTML pages, and I wanted them to look prettier than the default styling that Firefox applies. Hence, I discovered the world of classless CSS stylesheets. It’s pretty much what it sounds like: CSS stylesheets that don’t use any (or use very few) classes, relying instead upon styling semantic HTML elements. Obviously, these will not be a good fit for a great many projects. However, for converting markdown documents to simple HTML pages, it’s a perfect fit. Assuming that you’re not doing weird things to your markdown, when you export markdown to HTML, you get plain old semantic HTML, complete with zero classes, which makes it trivial to add a classless stylesheet and see your document redesigned cohesively in under a minute. There are plenty of classless CSS stylesheets out there that you can use. Some of my favorites are new, water-dark, and sakura-earthly. I downloaded a host of stylesheets, tried them all out, and had quite a bit of fun looking at all the different ways my document could be styled.

What’s the connection to accessibility? Writing in semantic HTML (assuming you’re actually using the elements correctly) is great for accessibility. Semantic HTML is relatively straightforward for assistive technologies like screen readers to access, and it renders easily and quickly for everyone else as well. Classless stylesheets encourage you (force you?) to write in semantic HTML — that’s the whole point of them. I also think that classless stylesheets can be beneficial to folks learning HTML and CSS. Applying classless stylesheets to your HTML illustrates how semantics and styling are distinct, and hopefully that can encourage more folks to seek out the most appropriate elements, rather than rely on divs and spans.

However, classless stylesheets aren’t necessarily accessible. As I wrote earlier, writing in semantic HTML is great for accessibility — assuming that you’re actually using the elements correctly. If you use a certain HTML element to achieve a certain styling, but if your content doesn’t align with that element’s semantic purpose, that’s … not great. Assistive technologies, for example, might misinterpret your content and thereby misrepresent it to users. One classless stylesheet that I fear might enable folks to do this is MVP. For example, with MVP, if you nest an aside element within a section element, it’s formatted as a centered content card. Designers might be thereby be tempted to use an aside element for a page’s main content, rather than content that’s “only indirectly related to the document’s main content,” as the Mozilla Developer Network defines the aside element. To be clear, I like MVP’s design, and its website clearly states that the stylesheet is intended only for temporary, ad-hoc purposes. However, I did want to note this potential way for classless stylesheets to be misused and lead to less accessible designs.

Website Updates

I recently did my first website remediation! At work, my team has put up an ad-hoc website this year as we’ve responded to the pandemic, pivoted to online staff trainings, and put together an online distance learning program for our clients. I identified that the color contrast between some commonly-used text and the background was not WCAG level AA conformant. With my manager’s approval, I selected a darker shade that was conformant, and I updated the text color. Hurrah for my first accessibility website fix!

On that topic, I’ve learned a lot about website accessibility over the past few months, and I’ve realized that I need to make some accessibility updates to my personal website as well as Graph Paper. I haven’t had the time to make those fixes yet, but I did conduct an accessibility audit on Graph Paper and log nine issues on GitHub. That was fun! Fixing those issues will be my next accessibility project after I publish this post.