Joining a CD Team the experience report

Today is my last day at Songkick. It has been amazing. Unfortunately I am in no position to move closer to the office, which means commuting! Commuting has taken its toll on me and I decided to call it a day and cried a lot.

When asked during recent interviews what my dream job would be, I did honestly say, my current role at Songkick. It obviously had its challenges but I don’t think a role has pushed me and enlightened me as much. Thanks for giving me the opportunity to experience it.

With joining Songkick came the experience of joining a CD team. Amy did a great talk about the survival guide of joining a CD team at Testbash Brighton this year.

But what was my actual experience?

I cam from a scrum team. We had bi-weekly releases and a comprehensive suite of selenium tests that ran through the browser. By comprehensive I mean, we had 64 hours of selenium tests that when run in parallel took 4 hours. So if one test failed because it found a bug, is flakey, you name it, you lose another 4 hours.

This meant there was a 3-5 day code freeze before the release date as well. We also used a typical scrum board with columns including a testing column. Some were even so granular that there was a “Ready for test” and “In test” column.

scrum-task-board-template-powerpoint

Any bugs that were raised during the sprint ended up in the to do column and needed to be fixed and regression tested before the sprint could be closed off.

Typical problems I had at this job were:

  • Testers become the “bottleneck”
  • Convincing team to help test rather than start new work
  • Defining acceptance criteria
  • Everything had an acceptance test
  • No unit tests

 

When joining CD teams it is worth understanding what the CD stands for. At songkick we have both products working in Continuous Delivery and Continuous Deployment.

At the very basic level both have an automated test and release pipeline but the Continuous Delivery approach still has a manual step to deploy to production, whereas Continuous Deployment would deploy the code straight to production.

This environment came with many learnings for me.

Ready for test:

Being used to the “Ready for test” column it was quite a shock to join Songkick and its continuous delivery and deployment approaches. Don’t get me wrong I joined because of these approaches as well. In conference talks this often appears to be a mystical world of software development where you test your code on production and developers have relatively good dev environment set ups that they can test well themselves.

But when do I test? Also where do I test?

There was something like a complete loss of control. In certain work environments (not Songkick at all) when a bug is found in production, the test team gets blamed. “Why wasn’t this tested?” is a common phrase. If you have worked in such an environment and then go to continuous delivery you can initially feel panicky because things move so fast and you may not be, or are very unlikely to be doing the testing.

What helped was understanding what is actually going on when new features are being developed. A thing that helped was that testing is happening everywhere all the time.

So discovering that everywhere testing is happening and can happen is invaluable. So you (not you personally but the team) can and probably is testing all the time everywhere. This starts with Kick off conversations. Here you get the chance to test the idea, the problem and the ideas around implementation. It is also a good place to state how you would test the feature.

A great tip from Amy was that in previous roles she learned that telling people what you will do for testing the new feature meant it would already get done by the person developing it and hence there will be less bugs.

So overall these kick off conversations become the most valuable part of testing for a tester at Songkick. They help inform what is just enough testing for this particular release.

Forget about “Ready for test” columns. Everything is continuously being tested and not necessarily by you. Think about how you can integrate your tester mind-set to be heard.

 

Ultimate shift left:

Get in on the planning discussions, requirements, stories, kick offs, whatever you call them, just invite yourself to the meeting and ask questions such as:

  • What is the problem?
  • Who is having the problem?
  • Why are we fixing it now?
  • How will we test it?
  • What is the risk of shipping bugs?
  • Do we need to consider non functional testing such as performance or security?

 

Team and trust:

Build good relationships in your team, because you will be on holiday for a week and there will have been 50 small releases to catch up on that were not tested by a tester.

For me this was about letting go and trusting your team members. Remember no one wants to write bad code and ship broken features.

Like I mention above I felt lost in the beginning, where do I fit in? Who is testing all of this?

A lot of that was about letting go of control issues. Discuss things you care about in a team setting, such as quality features and processes so you all feel comfortable. We did a great session on what quality and quality features means to us and how we define “just enough” testing. This can vary across products and teams but is so valuable to talk about.

 

Mindset change:

Testing becomes more of a proactive role, where you do the testing early on by pairing with developers, or going through unit tests, or liaise with the business to make sure you have the right acceptance tests in place.

Some of this mindset change may be to embrace more of a coaching mindset and sharing experiences and testing knowledge with team members.

At least at Songkick you are an expert in your field and can leverage this to help the team get better at testing in general.

 

Forget a “release date”. Communication is key:

If something is ready to go it will be released. Establish good communication with teams affected by changes. Release log emails, cross functional team updates in slack or regular catch ups.

This was an awesome change for me, to see how much the team is communicating with other departments to let them know about changes.

 

Test in production

g1361999261125710696.jpg

Get to know your production data really well, as a lot of testing will be done in the live environment. This has great advantages as the code is being tested where it is being used with real data but it can be daunting, as you could be affecting real reporting. Liaise with the relevant departments to help sort this and avoid any confusion.

I was always worried I would notify people about fake events. Liaising with the relevant teams and setting up data in a way to not disturb real fans was fun and scary at the same time and we actually found a bug that we could then fix asap.

Joining Songkick was one of the best things I did and I am super sad to be leaving today, but I am also excited about sharing what I learned and bringing this to a whole new role on the near future.

Have you had any experiences joining CD teams? Any learnings to share?

 

Thoughts: Accessibility testing for the web

screen-shot-2016-10-23-at-21-58-16

 

Myself and Emma recently organised an intro into accessibility testing with the awesome people at Test Partners.

They are really up for doing talks or tutorials with companies and are super friendly and knowledgeable. Do reach out to them if you have any questions on how to get started.

Why is accessibility important?

Up to 20% of the UK population has a disability but moreover research shows that 57% of the UK population benefit from accessibility features:

    • 20 million people over 50 in the UK – diminishing eye sight
    • 6 million + people with dyslexia in the UK
    • 1.5 million people with arthritis in the hand or wrist – use keyboard shortcuts over a mouse
    • Anyone can have a temporary accessibility need – like breaking an arm or hand

 

I have been aware of accessibility testing and really enjoyed the talk by Michael Larsen on the subject at the end of last year but did not look into it anymore.

This is a shame really because the internet is meant to be for everyone and therefore be inclusive but many websites are not.

Do we as testers do enough or even know enough about accessibility testing to point these things out? Are we knowledgeable enough to have these conversations on why we are excluding certain members of the population on using your website or services?

Have you ever had these conversations?

One place I worked at, I had just hired a new tester who came from an external testing services provider. He knew quite a bit about accessibility and started to raise bugs against our website for the images missing alt text for example.

On the one hand the things he was raising were just good practice to have really. But why did we not raise this before?

I never knew what to look for. I was more focused on functionality for able bodied users, maybe because I could easily be that sort of user.

The positive effect the other tester had, was that the designers and front end developers became more interested in how to make the website more accessible and started to reform from within. They started to design good patterns in accordance with the Web Content Accessibility Guidelines (WCAG) 2.0. I think this is the hard thing when it comes to accessibility, you can raise bugs and therefore awareness against accessibility features missing or keyboard navigation not working but if the designers and front end developers and maybe more importantly, the product team are not considering accessibility from the start then it is really hard to add it back in.

Why do we not learn about these things when we start our testing career? Was I just blind to it? The ISTQB certainly did not tell me about it.

If you are on the dojo there is a great resource to get you started. Maybe there will be a 30 day testing challenge for accessibility testing soon as well. I would love that.

One thing that Steve and Paul from the Test Partners showed us was this tool. You can add the bookmarklets to your browser bookmarks toolbar and then click on them to get visual feedback on how your website is built.

This helps with understanding the semantics of your page. How it is built and structured. For example headings are usually large and lists usually have bullet points. However, the semantic structure also need to be conveyed programmatically by means of tags in the source code. And these bookmarklets highlight where something has been tagged as a list or image for example.

This is a good starting point I feel, to understand what flaws your page may have for screen readers. Screen readers use the tags in your source code to tell the user what the item on the page is and does.

I would love to pair with some users of accessibility related tools at some point. On a similar note this podcast on a blind architect was incredible to find out how blind people actually use screen readers. TL;DR at a way faster setting than you think.

Have you ever paired with a blind user? Or someone who cannot use a mouse? Or maybe someone who uses a magnifyer?

 

 

Thoughts: Pair Testing…sort of

Pair Testing

At the beginning of the year, I attended TestBash in Brighton and there was a talk that just stuck with me with practical application.

This was the talk by Katrina Clokie on Pair Testing. She even outlined how she trailed it in her job.

I recently got a buddy at work and we were talking about sharing knowledge. I really wanted to try pair testing, so we did a version of it.

Step 1 – finding the right task

The team did some work on a tool that I wasn’t too familiar with and as part of our development process we created a testing mind map.

During coding the developer will use this mind map to test his code and depending on risk and sadly often time, the tester will also do some testing using the mind map.

In my pair testing example, the developer had done some testing and so had I, noting down some questions before involving my buddy. I then walked him through what we had tested so far and how the application was working.

Step 2 – What happened

Just due to different experience and knowledge he asked some other valuable questions which aided my testing to go a bit deeper and got us thinking of other testing types such as performance and database behaviour.

For me this was an invaluable experience, as I learned to think about other testing types and techniques and scenarios and I think for my buddy it was also a great experience as he got to see bits of the company’s product catalogue he wouldn’t necessarily get to see on a day to day basis.

I want to try and make this a more regular thing, and also try it before I test something and let the other tester drive.

The other side of this is, that we have a weekly test team meeting and I will try to show features or functionality that the other members may not necessarily see but may have to pick up, when I go on holiday. During this session we can also ask valuable questions of the new feature or product. Which is easier than listening to a monologue when handing something over. I think!

As testers I feel we generally want to know about the company’s products and about all the things they can do for customers and ourselves, so that is also why I envision this knowledge share to be good.

Do you do regular pair testing sessions? How do you structure them? Do you do knowledge sharing sessions with other team members?

Thoughts: Encouraging change when you are the only tester

Sometimes things come from small conversation snippets.

Some of you may know that I did a testinginthepub episode not too long ago. In there I talk a lot about what is awesome in my job now, like being valued as a team member, being invited to kick off meetings (these help us talk about what we are building and why)  teams ask me for mind mapping the testing areas.

However this was not always the case. It is important to remember that anyone can encourage change. I was not here before the changes so I will base my advice on what I did in my previous role as the first and only tester.

I did a talk on this last year at Tiny Testbash as well. The recording is available through the dojo subscription.

 

Encouraging change when you are the only tester.

In my previous job, I was introduced into a company which had a successful product that was starting to make them money but they had no testing department. When I questioned how they test their product I got the following answers:

“We don’t have any testers. Our product owners and stakeholders do the manual testing and we have a vast suite of front end automation tests.”

Nevertheless they decided to hire me, and subsequently a team of tester. How this came about and some learning along the way is what I would like to share below.

 

The problem:

So I mentioned that the company had a successful product, they had people testing it and a vast suite of automation tests. So what was the problem? The company was 6 years old at this point, had moved to their version of agile software development and the need for a fast feedback loop from the product owners and stakeholders was becoming apparent.

However these individuals generally already had a full time job and could not attend stand-ups, reviews, planning meetings, let alone test the product. More often than not the stakeholders were shown a feature at the review, and then they would find out that it may not have been what they asked for.

So the problems they were having were:

  1. Slow or no feedback from stakeholders
  2. No dedicated feature testing of new or existing features
  3. Front end automation tests that back to back would take over 60 hours, and run in parallel would run for 4 hours. (these were also fragile)
  4. No trust in the selenium tests – the tests are being fixed rather than the code.
  5. No unit tests
  6. Some business logic tests but they relied on experts being available to check them
  7. No stakeholder involvement in meetings
  8. No-one is thinking like the user

 

How did I approach this list?

Slow or no feedback from stakeholders:

Well this wasn’t so easy, but I tried to do a couple of things.

First of all it became clear very quickly that the business side of the company and the development side of the company actually did not know what each other did. To be able to be a representative of the user I had to understand who our users are and what they do.

Engage with the whole company:

So my first point of call was to spend time with the business, but not the managers, the actual people who use the systems from an admin POV and understand the user pains.

This would help manifold. I could understand where their frustrations may come from, and in turn the users’ frustrations and also see how the system is actually being used. In some places it wasn’t being used like the development team thought but there were workarounds in place to go around bugs. Now we didn’t even know those bugs existed.

This in turn led me to propose we talk and communicate with each other more. We set up specific projects for the internal bugs to be raised and had a dedicated team working on those, improving and maintaining the current systems rather than purely focusing on getting new features out. Which had 2 spokespeople from the business who ran teams of account managers or accountants so both sides of the system were represented. These then owned a backlog and could priorities their bug fixes and discuss them as well as progress in weekly meetings.

The important thing here was to engage with everyone across the business. Try to find out what everyone’s job role is, what do they love about their job, what isn’t going too well and why.

I did get pushbacks though when I asked the teams to forward issues to their managers which would then be logged in the dedicated project. I heard things such as “it has always been like that. I tried to tell someone before.”

We as a development team even offered to automate some data inputs but people are always wary when it comes to change.

Changes:

Once we started with the engagement I tried to create regular sessions on what testing is, what development is etc.

So we learned from the business but now we needed to see if they are willing to understand what we do. We set up fun little coding dojos over lunchtimes, where we used a language called Processing and tried to illustrate how the numbers and letters create systems ( or code).

Furthermore we set up a brown bag lunch on agile testing. When I first joined I was asked if I would be writing the unit tests. This got me thinking and I tried to collaborate instead. I am no coder or automation tester but I can pair on writing those tests and give feedback.

This way I tried to illustrate what I do and I decided to make my commitments public to the team. This came about because I was constantly being asked if I would write the automation tests, such as unit and selenium tests for the devs, which wasn’t the case. I stumbled upon the Tester’s commitments from James Bach around that time and wrote my own version, covering how I provide a service, etc.

http://www.satisfice.com/blog/archives/652

Alongside this I made suggestions what the business/stakeholders could focus on for their UAT, held a brown bag lunch about how a manual tester fits into an agile team working on bi-weekly sprints, and did some pairing with developers to understand how they work.

Consequences of change:

As much as this driving of change and engagement with the business had a positive effect – we were now on the road to better unit test coverage, understanding of testing, it also ended up backfiring a little bit, where I was starting to be seen as a quality gatekeeper, with there being a reliance on manual regression testing before a release, so testing became a bottleneck, especially as the team of developers grew and more streams of work were happening. More streams of work also meant context switching a lot from regression testing bug fixes, to new features, to new architecture.

Note to self: Do not let anyone call you QA, gatekeeper, etc when you first start somewhere and if that is not your role.

The effect of this was the thinking that we need a tester per product team to embed into each agile team, as well as dedicated product owners. A stakeholder or business person with a full time job was not going to cut it anymore if we wanted to get back up to speed and be focused.

So we wanted to work towards integrated a tester into each team, to be able to test small iterations of work frequently, and aim for full time product owners so we can reduce the feedback loop and having to spend time chasing stakeholders.

Hiring and building a team:

I was mainly involved with the hiring of the testers.

We have discussed the problem briefly and why hiring was a solution. We were trying to find tester who can integrate into the various teams and be the testing professional. As the product teams were quite different it was important to keep this in mind and not just hire 3 of the same type of tester.

For the hiring process I had a good idea of what I wanted, a good fit, an experienced self starter and not an automation tester but someone who would be a front end tester, with complimentary skills to myself. As I was keen for the devs to own the automation tests.

For the actual process we did phone interviews, and face to face interviews which included a live action testing problem. Just to see how someone would test and tackle a tasks and if they ask questions or not. How proactive are they? There are some very succinct and good resources on the ins and outs of hiring testers, I am mainly thinking of the ones by Rob Lambert if you want to have a further read and get some more ideas.

Once we had a team (I counted 2 testers as a team, but we grew to 4 in total within my first year), I wanted the team to be engaged and constantly learning about testing.

Time boxed Sprints give you the great advantage to try new techniques and experiment with testing techniques and I didn’t want anyone to feel boxed in, while having some consistency. Also each tester was working on a different product which would need different testing activities and tools anyway based on their context.

This meant we had bi-weekly knowledge sharing sessions, new features, testing techniques you name it.

I also set up monthly one to ones and tried to share a blog a week or whenever I saw a good one with the team. Furthermore we added testing related books to the library which had the nice side effect that developers would see the titles of the books and have a chat with you, so you could sell them more on the subject.

There was an especially a good session with jerry weinberg’s Perfect software- where a dev walked past and challenged me that perfect software doesn’t exist. Of course the full title is “perfect software and other illusions about software testing”.

Also being an organiser of the brighton tester meet up, I encouraged the team to attend events or even speak at them. One thing I learned from this was that not everyone wants to engage as much as I maybe do. At least not on the surface. And this is OK. Just keep doing your thing and don’t get downhearted. It can seem frustrating, like you are not getting through but I would just persevere.

We did manage to have developers attend the tester meet up and even speak about testing as well.

So what does my story tell you?

The main thing I did  was to communicate.

Find like minded people in your organisation and start sharing ideas, product knowledge, skills and experience and collaborate with them.

Start creating a library of resources and learning. This could be a physical library of books, or a wiki page with suggested reading/watching or regular events that you host inside and/or outside of the company.

Pair

Seek out people in different roles within your organisation and learn about their work. Try to understand what works for them and what does not.

But don’t forget people in the same role as you. Start pairing with other people in the same role in an effort to learn more about what they do, but also to help to build relationships.

Start socialising your improvement ideas with anyone who will listen. In my experience, planting the seed of an idea can make discussions about change easier later down the line. Get feedback on the ideas. Talk to people about how the future could be different. Listen to others.

I was passionate about what I do and tried to be positive in the light of change and when driving it.

Start gathering interesting trends about the work you’re doing – and then socialise these with the rest of the business.

Agile Testing: Frustrations can make us creative

  

creative space design of a restaurant

I love the fact that I have worked at a few different companies and hence have gotten to know so many awesome people.

It also has the great benefit that I still get to take part in different conversations around Agile Software Development practices and especially when the focus is on testing.

The other day I was forwarded a little article by Mountain Goat Software which focused around the fact that in an agile team, at the end of the sprint everyone tests. And some developers may not like manual testing so they will do automation testing or pair with testers to find efficiencies.

“At the end of the sprint, everyone tests.”

I am wondering a few things around this line of text. Why does everyone only test at the end of the sprint?

I know there have been many discussions that “testing” means manual testing being done by a human. But I do think that developers are often using Test Driven Design to write code and hopefully are also running the code they write to test that it does what they intended and maybe also how it does not (depending on experience, mind set, time pressures and learned habits).
Nevertheless the above quote is important for agile teams. I have experienced that as testers you can easily become a bottleneck because the developers think their part is done. Ideally they will have written the code and written automation tests as well. Now the manual testers get to test the new feature works and hasn’t broken anything.

But this leads to the problem that the developers are sitting there twirling their thumbs or starting more work, adding it to the bottleneck until the pipeline completely collapses.

So I like the fact that there was an emphasis put out that everyone should test as the team is responsible for shipping the work altogether.

I do hope though that testers and developers in a team get to test early as well, or maybe even designers or product managers, to make sure that the feedback loops is as fast as possible. The statement has the danger to be interpreted as such that testing should only happen at the end of the iteration. (I don’t think that is actually what they are saying.)

The excerpt I read actually states that the better the agile team the later the testing can occur. This seems wrong to me, but maybe I am taking it out of context and it is referring to the time needed for the whole team to be testers.

 

“Establishing a mindset of we’re all testers at the end, does not mean that programmers need to execute manual test scripts, which is something they’ll probably hate.”

 

The article went out to say that developers may dislike using manual test scripts for testing and hence maybe could focus on other things such as automation scripts.

I actually thing that it will be really beneficial for developers to do manual testing, not necessarily follow test scripts but explore the features they wrote instead.

By all means make sure your code is well tested using automation tools but you will not know if you have written the right code if you do not manually test it. You will only know that the code is written in the right way.

 

Frustrations can make us creative

I recently watched a video that Chris recommended on How frustrations can make us creative and it highlighted how doing something you maybe don’t like can actually result in you finding ways to make it better a lot easier than doing stuff you enjoy all the time. So developers definitely can really gain from doing some manual testing. And not just developers but hopefully the whole team.

A sort of related example of this is, that at Songkick we try and learn about what each department does and were encouraged to help the support teams. This has actually led to improvements being made to the admin systems when developers used it to help solve support cases. It is OK here to JFDI, when an improvement can really help someone.

A small example was that someone added extra information to be pulled in on one screen, so that you do not need 2 tabs open anymore to find all the information you need to close a support case. This was a huge time saving for everyone and was only achieved because a developer used the tools he created for the support team.

So I encourage everyone to test, collaborate and try something that frustrates you and see if you can make it less frustrating to do.

 

 

Don’t get stuck, try something different

 

view when trying a new running route I saw a double rainbow!


If you don’t know by now, 5 months ago (5 months!!!) I joined Songkick.

One of the many things that appealed, apart from working with Amy of course, was to experience another way to develop software, namely Continuous Delivery.

So this post is a bit about, not getting stuck in your job, routine, thought processes, try something different when you can or if what you are doing doesn’t feel right!

How did I get into this topic?

Songkick has had quite a few new hires in the tech team over the past few months and as part of the on-boarding there is a an intro into how we test at Songkick.

For 2016 Amy has been mixing this up by making the session super interactive and it really works.

As part of this we spoke about exploratory testing over test plans and how your emotions can drive your journey through the system when you are hunting for information and bugs.

All this “huh!?”, “oh!”, “OH!?”, “ah”, and “erm” moments can drive your test journey through the application as a tester and developer.

On the flipp-side to this is boredom. Boredom is another emotional state to avoid. Question why you are bored. Have you exhausted your testing journeys, do you need to mix it up by using different devices?

Boredom and feeling a little stuck was what drove me to try something different.

First a quick back story.

As part of a merger in early 2015 Songkick is doing some re-aligning of technologies. To keep it as vague as possible. I have been part of one of those teams working towards one platform. This has been super exciting and provided a great learning experience as I could learn about both companies technological history.

But this means we have some (or a lot of) manual regression testing we do as a team. This is generally unusual for projects there but a way of providing confidence for the team and whole business.

Now where am I going with this?

My boredom (don’t tell my team, I keep telling them that all testing is fun) came from the fact that I was regression testing something that we did have confidence in, over and over again on different devices and browsers, but it is quite a risky project so we rather test twice and in person alongside automation.

In the retrospective I was surprised how concerned everyone was that the testing was left to one person while the rest of the team tries to finish off other tasks before the release date. 

One of our team members had the great idea to block out some time and get everyone to test for an hour together.

Go with the energy.

Straight away I jumped at this and expanded on the idea. We discussed that this 1 hour session will involve all team members and we will test on different devices and browsers.

I was however not keen on providing a list of testing tasks or test plans as I wanted everyone to feel free to explore, so I created some user scenarios for everyone to have and try. They were meant as inspiration of what to test and a way of visulaisin how the software may actually be used.

 This seemed to work well, although the volume of scenarios I supplied was frightening some initially, but by emphasising that these were ideas and did not have to be ticked off we got somewhere really quickly.

Make it as easy as possible.

One major thing with testing systems can be the test data. This can be time consuming to create and manage, putting people off spending time on testing. I took this away from the team and provided them with different test data options for the various scenarios. These were the same selection of test data meaning we had a mini performance test of several users, accessing the same data. Being in ticket sales though we generally deal with short and high spikes of data which we are testing using automation. 🙂

Entice them

This can be as simple as buying jaffa cakes or bringing in some home made cookies. Always works a treat!

 

Trying a new recipe!


Results?

We had a focused testing session and logged several issues. None of which will block our release, thank god, but some which would have taken ages to find for one person.

Also we logged improvements on usability, as our designers and usability experts took part and got to experience the app first hand in a repetitive situation.

Overall this was a success, we got many eyes and devices to be used at the same time and it was a great team experience!

So don’t get stuck but do try something new! You never know what you may achieve. 

Agile Testing Days: Making a web for everyone by Michael Larsen

Wow Agile testing days is in a class of its own. So relaxed fun and full of friends old and new! Everyone is a hugger so be prepared. 😛

This morning I listened to 2 sessions. One by Michael Larsen I want to mention now as it was about a topic close to my heart, accessibility.


In my places of work we have ignored this in the past and actually it goes hand in hand with good UX design and responsive design so why don’t we make that extra effort up front?

Here are my notes from Michael’s talk.

Why accessibility as a topic?

  • We should build products that are designed to allow as many people as possible to access information.
  • Allow people with disabilities have a similar experience as their normative counterparts.
  • Good design that helps all of us.

Why focus on accessibility?

  • In some countries it is the law. Why limit your user base.
  • It is the right thing to do
  • It is good business.

Can you put yourselves in peoples shoes? What about blindness? Deafness? How would that affect your app usage? Have you ever turned on the screen reader on your computer?

Michael highly recommends the following book for more information as well. A web for everyone.

Types of disabilities:

  • There are normative/primary disabilities: Deafness, blindess
  • But there are also secondary disabilities, that we all can related to. IE. phone call at a loud concert.

Products are not just designed for a small group of people. We can all go from normative to significantly disabled without notice. What then?

Principles of web accessibility:

  • avoid making assumptions about your users’ ability
  • you can only guarantee that someones tech can send texts thats it
  • users time belong to them not us – don’t take control of either without good reason
  • provide good text alternatives for non text content
  • use widely available technologies
  • use clear language to communicate your message
  • make your sites usable, searchable, navigable
  • design your content for semantic meaning and maintain separation between content and presentation
  • progressively enhance your basic content – allow content to degrade gracefully

Heuristic Be HUMBLE

  

Humanise – understand the emotional content

Unlearn – step away from your default, maybe with using duct tape to resritct movement or using gloves. Try to control your computer with your voice.

Model – use personas, consider pace and behaviour differences

Build – learn about the tools to test with and discover the barriers

Learn – what are the barriers how do users perceive understand and operate

Experiment – put yourself in literal situation, collaborate with designers and programmers and provide feedback

Different terminology

Design accessibility up front – be agile about it – but use a different term. Accessibility has baggage associated with it this tends to be around money and law suits which has a negative connotation.

Use inclusive design

I really enjoyed this session and can’t wait to explore the topic further and order the recommended book. 🙂 Also a tip from my last place. If you just start paying attention to simple things like using alt tags and nudge the team you can make a real impact without much effort to your user base!