Accessibility Considerations
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Wilbur, Marcia K.
Wilbur, Justina
Accessibility considerations for hardware, software and documentation are presented. The presenters are Marcia K Wilbur (developer) and her daughter, Justina Wilbur. Justina was diagnosed several years ago with mixed connective tissue disorder (MS, Lupus, Rheumatoid Arthritis) and has some insights on additional areas for accessibility considerations in software and documentation. Web considerations and recommendations for future tools will be discussed.
 Hi, and welcome to accessibility considerations. My name is Marcia Wilber, and today I'll be presenting this short lightning talk with my daughter Justina, or Tina. Just as a short intro, I am a developer, Debian. I also do some AIoT development. I like to tinker. I've been a part of this community for about 20 years now, and I'm very community focused. I'm a journalist, a copyright activist, and a chixor. So I'm excited to be able to present this information about accessibility today, and let's get started. I'm going to turn the time over to Tina for a little bit about web accessibility. Hi, my name is Justina Wilber. I go by Tina. I have mixed connective tissue disease, fibromyalgia, bilateral carpal tunnel, renaughts, and degenerative disc disease. We are going to talk about web accessibility considerations for web content. Links. The text needs to be consistent with descriptive text. Same text used for links that go to the same destination. The link title attribute, the purpose is to offer additional information about the link. Typically, these are less than 80 characters, rarely over 60 characters, but short of the link title, it's more recommended. Web forms. If you use web forms, remember to have a real label, instructions placed before the form, and clear fields. It is clear which field an error message is referring to. Clear errors in how to correct. Color and contrast. Text color versus background color. Make background colors lighter or font colors darker, so it's easier to see. There are a few tools to check against color contrast in websites. Just create or improve some free and open software for contrast auditing. Keyboard only access. I do this a lot because I have a hard time gripping a mouse and using a mouse. I tend to use the tab key to tab over, but sometimes it doesn't work on certain websites. We would like to be able to use the tab key alone, in a logical order. You can set the links up and buttons with the enter key to create the best end user experience possible. You can move inside interactive items with an arrow tab. There's a skip to content link. The first thing you tab onto the page. There's drop down menus and mouse overs to work with tabs or arrows. That is it. So I want to thank Tina for that information about web accessibility and move on to other considerations. We'll start with video. To include audio and closed caption. So moving on to IoT and hardware. One of the things I wanted to discuss was the IP address that is sometimes located on the module outside of the device or unit. Is there audio also? Is there an alternative way for someone to see that display or get that information from the display? Because that would be very useful. Also during setup, you know, if it's too physically demanding, that could be difficult for some users. So remember ease of use, less setup, more bring up. And to include clear instructions, both text and images. So just like a recap here, make sure there are audio and visual considerations, ease of use, and also color blind considerations such as the green LED, right? Remember to design for accessibility. Who is the customer? What is the situation? How can we include everyone? And then of course, now is a good time to focus on accessibility. Again, a recap. Is there visual only display? Or is there audio also? Is there both? Is the setup demanding? Is the software easy to use and accessible friendly? And are the instructions clear and accessible friendly? So to sum it up. And let's go back to the glamorous battle, oh and look at this. I have to guess what, as none of the autistic groups here reflect baked science. Art街, creating a scripting 100 million- paradoxical people made a mistake. This overused and so the ugly sources show what happens if they take them and ignore their fixed layer of information. Okay, accessibility, physical reactions and seizures. So there can be physical reactions due to video and animations as well as patterns. So if you're doing video and animation, avoid blinks, flashes, anything 3-30 Hz. Avoid patterns with light and dark contrast, stripes and bars, and some of the reactions are as discomfort all the way up to seizure. So keep these things into consideration. Then reduce the risk by avoiding firework like videos or high flash rates, strobe lights is another. Avoid black and white patterns and anything with sunlight coming through the blinds or trees. If you're working with virtual reality, then you know it really stimulates your senses. And the images flash quickly, your eyes more focused on the field of view, and it's a possibility there could be a seizure triggered. So there's more current information about that at the Epilepsy Society website if you want to go check that out. And again another recap, do you have flickers, flashes, patterns, videos, sunlight, are you using VR? Okay, so this next section is about writing for accessibility in graphics and mobile. So when you write for accessibility, keep an accessibility in mind, you want to be clear and concise. You want to avoid using location such as in the upper right hand corner at the bottom of the page because when you're using a screen reader, I don't really think there's, you know, that doesn't, it's not kind of relevant, doesn't make a lot of sense, right? You know what I'm saying? And then with colors, you know, something like click the blue button, but there's three buttons. So how do they know which one's blue, if they're color blind or not able to see? So you know, keep these things into consideration. If you're working on a hardware project and you notice there are only like different colored LEDs for visual cues like yellow for warning, green for go, you might want to mention it to the engineering team and you know, just something very FYI like, hey, by the way, you know, I noticed visual items and cues, are there going to be any audio or alternative ways for people to get that information? Okay, when writing for accessibility, remember to use, you know, clear instructions, simplified language, colors and visual location. Now you might say, well, how can I have details and simplified language? Just make it easy to read and, you know, avoid the colors and visual location. So infographics are interesting because they're images, right? And how does someone make that more accessible? Well, you can add audio like with the image. So maybe like collection or like container that has, you know, that information. But I like to use Steghide and include the transcript. So if you want to learn more about Steghide, it's really interesting. You can embed the file with the image and you can do it with audio as well. So it could be an ultimate way of including information. As far as mobile applications, well, if you're using mobile apps, you know, if you have some, you know, there are some accessibility settings built in for enlargement, contrast, zoom and magnification. And during my research, I discovered that Google has an accessibility app scanner. Now here's the question. Why does Google have one and we don't? This is an amazing idea, right? Like we could have one just for desktop apps too. It checks different items for accessibility, friendliness. Anyways, it checks type, you know, the types that checks is like recording snapshots and secure windows, dialogues, and it scans it, it submits the results and then even has an editor for contrast, stores the results, share the results. I mean, it would be, I don't think it would be that difficult to, you know, write a script and throw a little YAD front on it or something. And here's the conclusion. Okay. So basically with accessibility, you can really pave the path to positivity, right? A little closer to the heart. And these are just recommendations and guidance, not enforceable, not something that, you know, needs to be in compliance or anything. Just goodwill. And starting out as community, maybe like for me it was about 20 something years ago. Like many of our projects seem more people focused, right? Like how can we create a tool, utility, or app that makes it easier for people to do this or automate this, you know? And let's get back to that, right? And pave a path of positivity for the future. If you have any questions, if you need to reach out to myself, Martina, you can find us online. IRC, you know, all the regular channels. But if you really need some assistance with your project and you don't know where to start with accessibility, you just want to, you know, talk it out or chat it out for a little bit and see what we can do for you. We do have volunteers and we do have information on our website, ganuelinux.io. No charge, help the community, help society, help our applications improve. We're all about that. So, thanks. Have a great day. Thank you. Marsha, thank you very much for the talk. And thank you for joining us for the Q&A session today. Thank you. So we have already received several questions. The first item is from Sylvia and Sylvia asks, even while trying to keep best practices in mind, it is of course possible to miss the stuff. Do you have any tips on making it easy as possible for people to report accessibility-related issues for open source or free software projects? Is GitLab's issue tracker okay or is it not very accessible? What is your opinion on that? So I can give you my opinion on GitLab but maybe people don't like it. It's a Microsoft product. I don't use it. So, but I could look into it and see how accessible it is. Yeah, I don't really have that answer as far as GitHub and proprietary platforms are concerned, but they might have some information on GitHub about accessibility. Right. The next question is from Sebastian and Sebastian is asking, do you find that better accessibility has for a part the same focus as keyboard enthusiasts? For example, use the mouse as little as possible just to make it also work properly just with the keyboard. So being able to use the keyboard is very important for people not just who have visual issues but who also have limited mobility. I saw someone posted something from Mozilla about accessibility. I thought that's a great resource that you can look to. Yeah, I would say keyboard definitely helps everyone. Thank you, Marcia. Sebastian has asked one more question. I have not used open dyslexic, but we do have dyslexics in our family and I definitely want to look into that. And thank you for that. I don't know what happened to Praveen, but I'm going to say this. I'm looking at some of the questions. So yes, I did subtitles. No, I did not see where on FOSDOM we can import SRT or subtitle files. Let's see. As far as getting back to that limited mobility question, it's not just one hand usage. Some people have arthritis in both hands or even we know some quadriplegics. We had a member in my club whose father had Parkinson's. So there's a lot of different limited mobility issues. The talk ends in one minute.
 Hi, and welcome to accessibility considerations.  My name is Marcia Wilber, and today I'll be presenting this short lightning talk with my  daughter Justina, or Tina.  Just as a short intro, I am a developer, Debian.  I also do some AIoT development.  I like to tinker.  I've been a part of this community for about 20 years now, and I'm very community focused.  I'm a journalist, a copyright activist, and a chixor.  So I'm excited to be able to present this information about accessibility today, and  let's get started.  I'm going to turn the time over to Tina for a little bit about web accessibility.  Hi, my name is Justina Wilber.  I go by Tina.  I have mixed connective tissue disease, fibromyalgia, bilateral carpal tunnel, renaughts, and degenerative  disc disease.  We are going to talk about web accessibility considerations for web content.  Links.  The text needs to be consistent with descriptive text.  Same text used for links that go to the same destination.  The link title attribute, the purpose is to offer additional information about the link.  Typically, these are less than 80 characters, rarely over 60 characters, but short of the  link title, it's more recommended.  Web forms.  If you use web forms, remember to have a real label, instructions placed before the form,  and clear fields.  It is clear which field an error message is referring to.  Clear errors in how to correct.  Color and contrast.  Text color versus background color.  Make background colors lighter or font colors darker, so it's easier to see.  There are a few tools to check against color contrast in websites.  Just create or improve some free and open software for contrast auditing.  Keyboard only access.  I do this a lot because I have a hard time gripping a mouse and using a mouse.  I tend to use the tab key to tab over, but sometimes it doesn't work on certain websites.  We would like to be able to use the tab key alone, in a logical order.  You can set the links up and buttons with the enter key to create the best end user  experience possible.  You can move inside interactive items with an arrow tab.  There's a skip to content link.  The first thing you tab onto the page.  There's drop down menus and mouse overs to work with tabs or arrows.  That is it.  So I want to thank Tina for that information about web accessibility and move on to other  considerations.  We'll start with video.  To include audio and closed caption.  So moving on to IoT and hardware.  One of the things I wanted to discuss was the IP address that is sometimes located on the  module outside of the device or unit.  Is there audio also?  Is there an alternative way for someone to see that display or get that information from  the display?  Because that would be very useful.  Also during setup, you know, if it's too physically demanding, that could be difficult for some  users.  So remember ease of use, less setup, more bring up.  And to include clear instructions, both text and images.  So just like a recap here, make sure there are audio and visual considerations, ease  of use, and also color blind considerations such as the green LED, right?  Remember to design for accessibility.  Who is the customer?  What is the situation?  How can we include everyone?  And then of course, now is a good time to focus on accessibility.  Again, a recap.  Is there visual only display?  Or is there audio also?  Is there both?  Is the setup demanding?  Is the software easy to use and accessible friendly?  And are the instructions clear and accessible friendly?  So to sum it up.  And let's go back to the glamorous battle, oh and look at this.  I have to guess what, as none of the autistic groups here reflect baked science.  Art街, creating a scripting 100 million- paradoxical people made a mistake.  This overused and so the ugly sources show what happens if they take them and ignore  their fixed layer of information.  Okay, accessibility, physical reactions and seizures.  So there can be physical reactions due to video and animations as well as patterns.  So if you're doing video and animation, avoid blinks, flashes, anything 3-30 Hz.  Avoid patterns with light and dark contrast, stripes and bars, and some of the reactions  are as discomfort all the way up to seizure.  So keep these things into consideration.  Then reduce the risk by avoiding firework like videos or high flash rates, strobe lights  is another.  Avoid black and white patterns and anything with sunlight coming through the blinds or  trees.  If you're working with virtual reality, then you know it really stimulates your senses.  And the images flash quickly, your eyes more focused on the field of view, and it's a possibility  there could be a seizure triggered.  So there's more current information about that at the Epilepsy Society website if you  want to go check that out.  And again another recap, do you have flickers, flashes, patterns, videos, sunlight, are you  using VR?  Okay, so this next section is about writing for accessibility in graphics and mobile.  So when you write for accessibility, keep an accessibility in mind, you want to be  clear and concise.  You want to avoid using location such as in the upper right hand corner at the bottom  of the page because when you're using a screen reader, I don't really think there's, you  know, that doesn't, it's not kind of relevant, doesn't make a lot of sense, right?  You know what I'm saying?  And then with colors, you know, something like click the blue button, but there's three  buttons.  So how do they know which one's blue, if they're color blind or not able to see?  So you know, keep these things into consideration.  If you're working on a hardware project and you notice there are only like different colored  LEDs for visual cues like yellow for warning, green for go, you might want to mention it  to the engineering team and you know, just something very FYI like, hey, by the way,  you know, I noticed visual items and cues, are there going to be any audio or alternative  ways for people to get that information?  Okay, when writing for accessibility, remember to use, you know, clear instructions, simplified  language, colors and visual location.  Now you might say, well, how can I have details and simplified language?  Just make it easy to read and, you know, avoid the colors and visual location.  So infographics are interesting because they're images, right?  And how does someone make that more accessible?  Well, you can add audio like with the image.  So maybe like collection or like container that has, you know, that information.  But I like to use Steghide and include the transcript.  So if you want to learn more about Steghide, it's really interesting.  You can embed the file with the image and you can do it with audio as well.  So it could be an ultimate way of including information.  As far as mobile applications, well, if you're using mobile apps, you know, if you have some,  you know, there are some accessibility settings built in for enlargement, contrast, zoom and  magnification.  And during my research, I discovered that Google has an accessibility app scanner.  Now here's the question.  Why does Google have one and we don't?  This is an amazing idea, right?  Like we could have one just for desktop apps too.  It checks different items for accessibility, friendliness.  Anyways, it checks type, you know, the types that checks is like recording snapshots and  secure windows, dialogues, and it scans it, it submits the results and then even has an  editor for contrast, stores the results, share the results.  I mean, it would be, I don't think it would be that difficult to, you know, write a script  and throw a little YAD front on it or something.  And here's the conclusion.  Okay.  So basically with accessibility, you can really pave the path to positivity, right?  A little closer to the heart.  And these are just recommendations and guidance, not enforceable, not something that, you  know, needs to be in compliance or anything.  Just goodwill.  And starting out as community, maybe like for me it was about 20 something years ago.  Like many of our projects seem more people focused, right?  Like how can we create a tool, utility, or app that makes it easier for people to do  this or automate this, you know?  And let's get back to that, right?  And pave a path of positivity for the future.  If you have any questions, if you need to reach out to myself, Martina, you can find  us online.  IRC, you know, all the regular channels.  But if you really need some assistance with your project and you don't know where to start  with accessibility, you just want to, you know, talk it out or chat it out for a little  bit and see what we can do for you.  We do have volunteers and we do have information on our website, ganuelinux.io.  No charge, help the community, help society, help our applications improve.  We're all about that.  So, thanks.  Have a great day.  Thank you.  Marsha, thank you very much for the talk.  And thank you for joining us for the Q&A session today.  Thank you.  So we have already received several questions.  The first item is from Sylvia and Sylvia asks, even while trying to keep best practices in  mind, it is of course possible to miss the stuff.  Do you have any tips on making it easy as possible for people to report accessibility-related  issues for open source or free software projects?  Is GitLab's issue tracker okay or is it not very accessible?  What is your opinion on that?  So I can give you my opinion on GitLab but maybe people don't like it.  It's a Microsoft product.  I don't use it.  So, but I could look into it and see how accessible it is.  Yeah, I don't really have that answer as far as GitHub and proprietary platforms are concerned,  but they might have some information on GitHub about accessibility.  Right.  The next question is from Sebastian and Sebastian is asking, do you find that better accessibility  has for a part the same focus as keyboard enthusiasts?  For example, use the mouse as little as possible just to make it also work properly just with  the keyboard.  So being able to use the keyboard is very important for people not just who have visual  issues but who also have limited mobility.  I saw someone posted something from Mozilla about accessibility.  I thought that's a great resource that you can look to.  Yeah, I would say keyboard definitely helps everyone.  Thank you, Marcia.  Sebastian has asked one more question.  I have not used open dyslexic, but we do have dyslexics in our family and I definitely  want to look into that.  And thank you for that.  I don't know what happened to Praveen, but I'm going to say this.  I'm looking at some of the questions.  So yes, I did subtitles.  No, I did not see where on FOSDOM we can import SRT or subtitle files.  Let's see.  As far as getting back to that limited mobility question, it's not just one hand usage.  Some people have arthritis in both hands or even we know some quadriplegics.  We had a member in my club whose father had Parkinson's.  So there's a lot of different limited mobility issues.  The talk ends in one minute.
including_everyone_0_1391.png including_everyone_1392_1883.png including_everyone_1884_5087.png including_everyone_5088_9203.png including_everyone_9204_11375.png including_everyone_11376_11627.png including_everyone_11628_14543.png including_everyone_14544_15587.png including_everyone_15588_20075.png including_everyone_20076_26219.png including_everyone_26220_26639.png including_everyone_26640_28350.png