Showing posts from April, 2021

2.4.2 Page titled

This is possibly the most obvious guideline but one that sometimes gets overlooked. I'm going to stretch it a little to cover more than just webpages. The actual guideline says: Webpages have titles that describe the topic or purpose. However, titles are useful for more than just webpages, so we'll do a quick run through of how this applies to documents that you might share online. Webpages Let's start with webpages. When coding in html, you have two main blocks of code:  Head - contains information about the page and links to things like the stylesheet and any javascript Body - the actual content that will be displayed on the page. In the head, you should include a title tag. This displays the title of the page on the tab in the Internet browser. It works like this: <head>     <title>Portfolio</title> </head> And this looks like this: The key thing is that this title needs to be short and to describe what the page contains. Mine probably needs chang

Alt text

I have already covered this guideline (back at the end of December) but in the last few weeks, it has cropped up in some of my work. I have been really encouraged, over the last year, to see the commitment my main client has towards meeting WCAG in all their content. They have invested in training for their staff, to ensure that any new content is accessible. It has been fantastic to see the efforts that individuals are making too. Though, naturally, not everyone gets it right all the time (including me). One of the common areas where I have seen mistakes recently, is in alt text. Some of the things I have seen are: Missing alt text (though this is now rare) Automatically generated alt text that is incorrect or inadequate Images incorrectly marked as decorative Images that are not inline with the text. However, the one thing that I get asked most about, is what to write. People find it very difficult to write alt text that is descriptive enough and gets the intended information across.

2.4.1 Bypass blocks

I thought this one would be easier to show than write about, so I made a 10 minute video. Hopefully, it also gives you an idea of how Dragon works, as well as what this guideline is about and how to achieve it.

2.3 Seizures and physical reactions

Like my last post, I'm going to cover the wider section and gloss over the subsections within it. This guideline says: Do not design content in a way that is known to cause seizures or physical reactions. I would like to hope that in 2021, people are aware that flashing lights can cause seizures for people with certain conditions. From personal experience of photosensitivity, they can also trigger migraines. Who knows what else?  I would question why you would use flashing, given that this is known to be problematic but like the safety note on suppositories that tells you not to take them orally, you know someone is trying it. PowerPoint I have to confess that I'm not the greatest fan of PowerPoint. I was a primary school teacher back in the day when it was all new and exciting. Y6 children (initially) were taught how to use PowerPoint and then gave endless presentations to their class, the school, the staff, different classes, etc. They made all the rookie errors, because we (