Category Archives: Accessibility

Accessibility, Story telling

The current way of my blogging – Part 1

During the years, I slowly changed my way of blogging. I can just write about is, but I also want to add some thoughts about it. Welcome to my first State of the Blogging.

The first step was to put the whole blog post in a mind map on a mobile phone. I liked the auto complete typing. Then I copied all the text into a Word document.

Brewing blog posts

In the past I used the mind map intensively for blogging. I edited the first rough version with MindManager on my Android phone and then extracted the information with FreeMind on my PC.  Nowadays I use an iPhone and I could not find the right software, so I started blogging in Word right away. Like now.

The basic idea is still the same. I put little pieces of the blog post in a Word document. Then I expand the pieces to readable paragraphs. This is based on the Fieldstone method of Jerry Weinberg.

Most tech related blog posts can be quite boring with abundance of dry facts and tips. So, I tend to add jokes in the blog post. If I need to retrieve some information from a blog post, then it is easier for me to consume.

Nowadays, I put a rough overview of a blog post or serie of blog posts with similar theme into one Word document. In case of several blog posts, I split the overview in different parts. Yes, you are currently reading the first part.

Making it accessible

In the past I tried to make my blog posts better readable for other people. I added extra headings, so I had to add extra code for CSS or Cascading Style Sheets. I used the following code:

blockquote {
	color: black;
	padding-left: 5%;
	font-weight: 400;
}

h1 {
font-size: 20px;
line-height: 1.5;
}

h2 {
font-size: 18px;
line-height: 1.25;
}

h3 {
font-size: 16px;
line-height: 1.1;
}
Then I limited the size of the paragraphs. My thumb of rule is maximal 3 lines in Word, which leads to a reasonable paragraph in WordPress.

During editing, I tried to simplify the language, so a beginning engineer can understand my blog posts. Example: the previous version of the last sentence contained “to reduce the level of my language to a level of a beginning engineer”.

In one blog post I added a warning for people, who uses screen readers to read the text aloud. Most of the time it is tiring to listen to every period and comma in a sentence. So, a lot of people set the level of the screen reader to skip these characters. But this this is not handy, if source code is shown.

Bonus tip: I also used warnings for readers to avoid situation, which trigger things like anxiety.

Just checking

English is not my native language, so I try to use proper words. On the web I regularly asked for the meaning of a word. If I find a reference to urban language, then I need to change the text.

Fact checking on the web is also included in my blogging. Especially, if laws are involved. Luckily, they are published on the web. They are great link fodder.

Use the Source, Luke.

To be sure, I added a disclaimer, that I am not a legal expert.

Word offers spelling and grammar checks. I prefer to use English UK. There are a lot of people who like to speak Oxford English, but use American words or phrases. Yes, I am one of them.

Using open standards

A Word document cannot be copied and pasted on the Web. I prefer HTML, the language used to make web pages. Then I store the Word document with the option ”Web page (filtered).”.

To be continued.

Accessibility, Assistive technology

How to convince a tech outsider with a car

How to convince a tech outsider with a car

Sharing a concern

A few years ago, I talked with a man about accessible programs. People with disabilities have problems with certain programs. If someone  has a problem with sight, then a screen reader is important to understand the program. If this program has not been set up in the proper way, then the user does not hear what is going on.

I said that it was difficult to change the code. In return I got a weary glance. He was probably thinking about replacing some lines of text by other lines.

The man did not know anything about software engineering. It was time to use an example which was understandable for him.

Throwing in a car

So, I asked him: “Name a car brand.”
He answered with: “Porsche.”
That man had an expensive taste. How could I beat that?

I remembered another car brand:
“I have a Lamborghini.”
He exhaled.

Then I mentioned a task:
“Replace the engine of the Porsche with the engine of the Lamborghini.”
He tried to imagine how to accomplish this task. With a worried face he gave up:
“It is not possible.”

Then I said:
“Making existing code accessible is like replacing an engine of a Porche with an engine of a Lamborghini.”

Owing an explanation

The first step is to build the engine in the car. Of course, nuts and bolts might be reused. But are the holes in the engine on the same place as the holes in the chassis.

Keep your engine on board.

Keep your engine on board.

The next step is to connect the moving parts of the engine to the rest of the car. An example is the axis to turn the wheels.

The main purpose is turning the wheels instead of making impressive sounds.

It is also important to realise that changing an engine can have impact on other parts of the car. A project member once told me, that people forgot to improve the brakes after upgrading the engine.

Keep a good grip,

Excusing for the scale

While blogging, I described an extreme case of replacing. There are programs or web sites which can be made accessible in a simpler way under the right conditions.

Accessibility, Assistive technology

Test idea number 1 – Use the screen reader – part 2

At the Club of Ministry of Testing, Rosie Sherry asked to share test ideas in five words or less. My first test idea was: use the screen reader. In the previous blog post some aspects of testing with a screen reader have been highlighted. There is more stuff to think about. Or to be read.

A more holistic approach

Getting good quality also implies involving developers, product owners, and managers from the start. A lot of people tend to determine the quality of an app or web site for a screen reader in the final phases of the development of a product. This order of activities is not as expected.

If some laws require to make web sites or apps accessible for screen readers, then the selection of the UI elements should be strict. A law has some priority. Fortunately.

Whether the UI elements came through the initial test, they should be monitored. Even, if they are not updated by your own developers. Even removing UI elements can have some consequences for the operation of the app or web site.

There are other test activities than reviewing use stories and using the screen reader at the end. This means, that extra developer activities must be added. This is the reason I call this a holistic approach. As a tester, I tend to, look at the tools and the processes to make the software. That can be outside the tester comfort zone.

According to me, a life cycle approach should be used for each UI element. This cycle contains the following phases: Create, Read, Update, and Delete.

How to test Create a UI element suited for a screen reader

Use standard UI elements, which are automatically recognised by screen readers.

Use a library of accessible UI elements.

Extend existing code of UI elements. Inheritance is a way to make stable code. It is like adding some extra features to an existing UI element. A combo box based on code of another combo box might also
change.

Avoid making UI elements from scratch. For web sites the HTML tag Aria looks very compelling, but it takes some consideration. Suppose I like have a blue car. Inheritance would lead to buying a car and painting it blue. Aria would be like building a car from scratchans using blue paint. 

Use standard development practices. This year Sonos released an inaccessible app for iOS. The standard iOS elements are accessible, so the developers had taken some strange steps to use own elements
and instead.

Use good tools. This also applies for systems which can be adjusted to your company or organisation. I heard about a system which was accessible for job seekers, but not for the people inside the company.

Make a big app or web site with all custom-made GUI elements for evaluation. This is also needed for 3rd party softwire like cookie banner, chat bots, and web shop functionality.

To be extended.