Mobile Tech Accessibilities

“No one has ever requested captions or ALT text” I recently pointed out to an organisation that none of their social media content was accessible to me as a blind person, or to anyone who cannot access spoken language. The response I received was: “No one has ever requested ALT text or captions for our posts.” That sentence alone reveals just how much is still wrong with how accessibility is understood and practiced. First, disabled people do not request access every single time it is missing. We simply cannot. Inaccessibility is everywhere. Were we to contact every organisation, brand, university, conference, or charity about their inaccessible communications, we would quite literally not have the time or energy to do anything else. This is what research increasingly refers to as disability work: the invisible, unpaid labour disabled people perform every day just to exist in systems that were not designed for us. Flagging barriers, explaining basic access needs, advocating for changes, and then often being told those changes are too difficult, too expensive, or too time-consuming. This work takes time, cognitive effort, and emotional energy, and it is rarely acknowledged. Second, accessibility and reasonable adjustments are an anticipatory duty under the UK Equality Act 2010. That means it is not the responsibility of disabled people to notify organisations that they are inaccessible. It is the responsibility of organisations to know this already, to anticipate diverse access needs, and to design accordingly. If you operate in the EU or engage EU audiences, web accessibility regulations make this obligation even clearer. Access is not a favour. It is not an act of kindness. It is not a “nice to have”. It is a legal and ethical responsibility. Third, the argument that an organisation is “too small” or that creating ALT text and captions is “very time consuming” simply does not hold. With the technology currently available, including generative AI tools, creating ALT text takes seconds. Automated captions may not be perfect, but imperfect access is always preferable to none at all. Claiming a lack of budget or capacity shifts the burden onto disabled audiences, who did not create the barriers in the first place. And yes, accessibility benefits far more people than those it is usually associated with. Captions support Deaf and hard of hearing people, but also neurodivergent users and people whose first language is not English. Descriptive content improves clarity and engagement for everyone. Finally, designing with inclusion in mind from the outset is not only the right thing to do, it is also cheaper and more effective than retrofitting access later. It is how innovation happens. Inclusive design consistently leads to better user experiences for all. So if your organisation’s response to inaccessibility is “no one has asked”, it may be time to ask yourselves a different question: why should disabled people have to keep asking at all?

Do you use emojis instead of bullet points? Do you post a photo but forget to describe it? Maybe you love creating images where there is text over a photo... If you're doing any of these things, your communication is not as accessible as you might think. And as today is International Day of People with a Disability, it's a great time to reflect on our own accessible communication practices. The good news is that there are plenty of resources out there to help, like the brilliant Kelly Thibodeau, CUA, CPACC, and Matisse Hamel-Nelis, ADS, CPACC and Lisa Riemers' brand-new, amazingly helpful book, 'Accessible Communication: Create impact, avoid missteps, and build trust.' While you're getting your hands on a copy, here's five of my top tips to get you on the right track, especially if you're communicating through digital channels like social media. 1. Avoid emojis and emoticons. If a person uses a screen reader, these are very annoying! Also, they don't convey the same meaning for everyone. Use them sparingly, and at the end of a sentence if at all. 2. Include alt text and descriptions of your images. It's great for screen readers, great for SEO, and also just helpful for people to better understand the message the image is conveying. 3. Use colours with strong contrast. People with poor vision or visual processing can struggle to decipher text in different colours. Black on white is always a winner. There are great tools and guidelines out there to help assess your colour use. 4. Use short sentences and clear, common words. It's not just for accessibility ... it's just better for everyone! 5. Always include captions and transcripts for video and audio. People consume information in different ways and contexts anyway, and some people need a transcript to give them more time to process the messages. What else would you add to the list? [Image description: pale green tile with black text. The headline reads: Top tips for accessible communication, and lists the five points in this post. The logo for Cuttlefish, Mel's business, is on the right-hand side in black, all-caps text.]

My design passed accessibility checks with 7:1 contrast, while a user measured 3.37:1 on Linkedin. Both of us were right at the end, do you know how? I recently had a very interesting discussion under one of my posts and it turned into a great reminder of how complex accessibility can be in the real world. For the post, I created a graphic and checked that the color contrast of every text element is safely above the 4.5:1 minimum recommended by WCAG. Then a follower commented that some of the text was hard to read on the phone and he shared a screenshot from a contrast checker showing 3.37:1 for one of the colors. That raised an interesting question: how can a design that passes accessibility checks suddenly fail a user? There are several things happening between the moment we design something and the moment someone sees it: 1️⃣ Platform compression When we upload images to social platforms, they are usually compressed automatically to reduce file size. Compression can slightly change colors and blur the edges between text and background. If the contrast was already close to the limit, this can lower the effective contrast. 2️⃣ Image resizing The graphic I designed was quite large, but platforms often resize images for different screens, especially on mobile. When the image becomes smaller: • text strokes become thinner • edges get softened by scaling • readability decreases 3️⃣ Thin fonts + antialiasing Even with sufficient contrast ratios, thin fonts can reduce perceived contrast. When text is scaled or compressed, the browser blends text pixels with the background (antialiasing). That means the visible color becomes a mixture of text and background. Contrast tools inside design software measure pure colors, while the final rendered image contains blended pixels. 4️⃣ Screens and real-world conditions People view content on: • phones in bright daylight • different screen technologies • different brightness levels • sometimes without glasses All of this affects how readable something feels. 5️⃣ Measuring the uploaded image Another important detail: the contrast was checked on a screenshot of the uploaded image, not on the original design. That means the tool measured pixels that were already affected by: • compression • scaling • antialiasing So the measured 3.37:1 might actually be correct for the rendered version of the image. Accessibility does not only happen during design, it also depends on how the design is exported, processed by platforms, and displayed on real devices. That’s why it's helpful to: ✔ aim for contrast higher than the minimum ✔ avoid very thin fonts in images ✔ check the exported file, not only the design tool ✔ test how it looks after uploading to the platform Have you ever experienced something similar where a design technically passed accessibility checks but still caused issues for users? #WebAccessibility #Accessibility #InclusiveDesign #UXDesign #UXAccessibility #WCAG #DesignForAll

Most of us use our mobile devices a lot. You might be using a smartphone right now to read this post. We surveyed Fable community members and found many are on their mobile devices for more than 4 hours a day (41%). Another 23% spend 2 to 4 hours per day on mobile devices. With that much mobile usage, accessibility of native mobile apps is just as important as web accessibility. However, many app developers find mobile accessibility more challenging. There’s less guidance on how to build inclusive iOS and Android apps. Rather than look to standards for guidance, we can focus on avoiding the most common barriers assistive technology users encounter on smartphones and other mobile devices. Based on our community survey, those top barriers are: * Unlabelled buttons or links  * Small buttons or links  * Gestures required to interact  * Parts of the screen blocked * No error messages * Not able to resize text * Not able to pinch and zoom These aren’t hard things to fix. Label things. Design bigger touch targets. Use buttons or custom actions in addition to gestures. Be careful using sticky content. Include error messages in forms. Choose scalable or dynamic type so users can adjust text size. Don’t disable pinch to zoom. You can read the full mobile insights article here: https://lnkd.in/g3mGErmf My favorite resources for mobile accessibility are appt.org and magentaa11y.com. Apple and Android have solid documentation too: https://lnkd.in/gbfwBVFD https://lnkd.in/g9XH3yXf

What if the tool you're building is making the web less accessible - not because of how it works, but because of what it lets people create? Most web developers have heard of WCAG (Web Content Accessibility Guidelines). It's the go-to standard for making websites accessible. But WCAG isn't the only accessibility guideline out there. And if you're building anything that lets users create or publish content online, there's another one you should know about: ATAG. ATAG stands for Authoring Tool Accessibility Guidelines. And it applies to more tools than you might think. If you're building a CMS, a blog platform, a social media tool, a website builder, an email editor, a comment system, a forum, or really anything that lets people create and post content, then you're building an authoring tool. That also includes plugins, extensions, and add-ons for platforms like WordPress, Drupal, Shopify, Webflow, etc, or at least the ones that involve content creation. If your plugin gives users a way to input and publish content (think form builders, page builders, review systems, or portfolio tools), ATAG applies to you too. ATAG has two parts, and both matter: • Part A is about making the tool itself accessible. Can someone using a screen reader or keyboard actually use your editor? Can they format text, upload images, and publish without barriers? • Part B is about helping users produce accessible content. Does your tool prompt for alt text when someone uploads an image? Does it flag missing headings or low contrast? Does it make it easy to do the right thing? That second part is where it gets really interesting. Because even if your tool is technically accessible to use, if it doesn't guide users toward creating accessible output, you're potentially multiplying barriers across the web. Think about how many blog posts, product pages, newsletters, and social updates get published every day through tools like these. If the tool doesn't support accessible content creation, that's a lot of inaccessible content going out into the world. WCAG tells us how to make our own sites accessible. ATAG asks us to think bigger - to make sure the things we build help other people create accessibly too. If this is new to you, that's ok. It's not talked about nearly enough. You can find the full guidelines at w3.org/TR/ATAG20, and it's worth a read if you're working on anything in this space. #Accessibility #WCAG #a11y #webdevelopment [Image description: Comparison graphic showing two accessibility guidelines side by side. On the left, WCAG (Web Content Accessibility Guidelines) with the tagline 'Make your site or app accessible.' On the right, ATAG (Authoring Tool Accessibility Guidelines) with the tagline 'Help your users create accessibly.' Each side has an illustration of a developer, working on a website, and pointing at a website as though to guide someone.]

Content creation, but make it accessible! #accessibility We all want to make content visually pleasing, but who are we making it visually pleasing for? I’ve been working as a content creator for more than 3 years now; however, besides captioning, I haven’t really explored accessibility. When we talk about accessibility, we often think about making buildings or websites accessible. But what about the content we put out on social media? In today's digital world, where everyone is present on social platforms, ensuring inclusive content is important (though not all platforms may be accessible). Here are some suggestions to make the content we put out on platforms like Instagram, TikTok, and YouTube more accessible: 1️⃣✅ Colours: Ensure high contrast for readability and consider colour blindness simulations to test your designs, like the following: https://lnkd.in/gWngedNb https://lnkd.in/gaZfgjma 2️⃣✅ Fonts: Choose sans serif fonts. This improves readability, benefiting users with visual impairments or learning disabilities. 3️⃣✅ Visuals: Avoid triggering or overwhelming visuals. This ensures a positive user experience, especially for those with sensory sensitivities. 4️⃣✅ Language: Ensure content is understandable to speakers of various languages. Recently, I came across Adobe’s Dub Dub Dub project, which I think would be a great tool for users experiencing language barriers: https://lnkd.in/g9sz-8aw 5️⃣✅ Captions: Always provide captions or transcripts. This makes audio content accessible to users who are deaf or hard of hearing. 6️⃣✅ Graphics: Use graphics instead of text in images and provide alt text for screen readers (Instagram and LinkedIn have an alt text option). This ensures accessibility for users with visual impairments. 7️⃣✅ GIFs: Avoid using GIFs in videos for accessibility. They are incompatible with screen readers and may be challenging for users with learning disabilities to understand. 8️⃣✅ Emojis: Use emojis instead of text-based emoticons (incompatible with screen readers). This makes communication easier for users with learning disabilities. Do you have any more suggestions to add? Let me know in the comments! ⬇ A special thank you to my professor, Nancy La Monica, for her invaluable guidance in the universal design course, empowering me to create more accessible content. #contentcreation #accessiblecontentstrategy #disabilityadvocate #disabilitystudies #influencers #promotions #brandmarketing #adobedubdubdubproject #linkedincreators Seneca Polytechnic Seneca Business LinkedIn Guide to Creating ... 👋👩💼Hi there, I'm Krishma, and this is my professional diary where I reflect and write about #business, #marketing, #research, #accessibility, #sustainability, #studentlife, and more! 

I wrote a bug for this WCAG criterion for the first time, so I thought I'd share!   2.5.1 Pointer Gestures is one of the few WCAG criteria that is primarily targeted toward mobile (and tablet) devices. It says that, if a component uses a path-based gesture to operate it, there has to be an alternative non-path-based way of operating that component. What??   A path-based gesture involves an interaction where not just the endpoints matter, but how the users moves between these two points. Swiping through a carousel is a path-based gesture: your finger starts at the right, and then you have to make a (mostly) straight line to the left to move the carousel. A maze game would be another example: where exactly you move your cursor or finger between the start to end points matters.   Not everyone can perform a path-based gesture well, if at all! For example, people with hand tremors, arthritis or who use a head pointer would find the precision required for these movements - on desktop or mobile - difficult.   The bug we raised was for an image gallery, where the previous/next buttons only displayed on hover. But there's no hover state on mobile, so users could only swipe to view the gallery. That meant only a path-based gesture option was available.   The solution? Make the pagination buttons permanently visible. Users who want to swipe still can, but those who can't or would prefer not to, have a single-pointer option available.   Accessibility improvements are often as simple as this. And they have a huge impact on many users' ability to navigate, operate and understand digital content. What accessibility win have you accomplished recently? Don't forget to book your slot for free accessibility advice for Aleph Accessibility's birthday next week: https://lnkd.in/gVHNbXDt #webAccessibility #UX #code

The W3C’s new draft guidance on applying WCAG 2.2 to mobile apps, WCAG2Mobile, is a big step forward for mobile accessibility. This isn’t a new standard. It’s a clarifying resource to help developers and accessibility professionals interpret WCAG success criteria in the mobile context, where factors such as native gestures, hybrid apps, and diverse assistive technology support create real challenges. The draft offers: - Mobile-specific terminology to align accessibility language with mobile development - Criterion-by-criterion guidance tailored for mobile apps - Platform-specific insights to account for differences across iOS, Android, and web For teams building mobile experiences, this guidance makes accessibility more achievable — not more complex. It’s early days. The draft is open for feedback, and the accessibility community’s input will shape its future. If mobile accessibility is part of your roadmap, this is a must-read: https://lnkd.in/eJmXYNin #WebAccessibility #WCAG #W3C

Today is Global Accessibility Awareness Day (GAAD) Let’s talk about what accessibility really means and how you can take steps today to create more inclusive digital spaces. Accessibility isn't just a tech issue; it's a human issue. It’s about making sure disabled people can fully participate in online life, work, learning, and connection. Here are 6 simple things you can start doing right now: 1. Add alt text to every image you post 2. Use meaningful link text (not “click here” describe where it goes) 3. Check color contrast to ensure readability 4. Make content keyboard navigable; not just clickable 5. Use plain language for clarity 6. Caption your videos, always These small changes aren’t hard, but they make a massive difference. And remember: Accessibility without inclusion is performative. If you care about accessibility, hire disabled people. Bring us in as designers, developers, testers, consultants, creatives, and leaders. You don’t need to be an expert to start. You just need to care enough to take action. Image Description: A graphic with a notepad-style checklist on a purple background titled “Accessibility Things to Do.” It lists seven accessibility actions: Add meaningful alt text to your images, Add image descriptions of images on posts, Use descriptive link text (not “click here”), Check color contrast to ensure readability, Make content keyboard navigable, Use plain language for clarity, and Always, caption your videos. Decorative sparkles appear in the corners, and a website placeholder is shown at the bottom. #GAAD #Accessibility #InclusiveDesign #A11y #DigitalInclusion #ADA #WCAG #DisabilityJustice #NothingAboutUsWithoutUs #HireDisabledPeople #AccessibilityMatters