Are you over 18 and want to see adult content?
More Annotations
A complete backup of australiaawardsafrica.org
Are you over 18 and want to see adult content?
A complete backup of newmarketholidays.co.uk
Are you over 18 and want to see adult content?
A complete backup of lagonissiresort.gr
Are you over 18 and want to see adult content?
Favourite Annotations
Black History Studies – Educating the community to educate themseves
Are you over 18 and want to see adult content?
Start your Shopify Dropshipping Business Today | Best Guide to Dropshipping
Are you over 18 and want to see adult content?
Αρχική - Μαγειρικές Απολαύσεις
Are you over 18 and want to see adult content?
Christa Quilts – Make it yourself. Make it your own.
Are you over 18 and want to see adult content?
Vakantie boeken | Zon & wintersportvakanties | Sunweb
Are you over 18 and want to see adult content?
Plymouth, MA Hotel - Hotel 1620 Plymouth Harbor
Are you over 18 and want to see adult content?
AWE 情感工作室 – Attract Men You Want
Are you over 18 and want to see adult content?
Envato Studio - WordPress Customization to Logo Design and more
Are you over 18 and want to see adult content?
Text
MOBILE A11Y
Mobile A11y. Mobile A11y is a collection of blogs and resources about how we as mobile developers can improve accessibility on mobiledevices.
RESOURCES | MOBILE A11Y Resources. This is a personally curated list of resources I have used and think others may find helpful too. I’m always looking for new high quality mobile accessibility and inclusion resources to add here.BLOG | MOBILE A11Y
A11y Box Android. Apr 26, 2020 | 1 minutes. An open-source example of Android's Accessability API. Android. Mobile A11y Blog. Blog.Resources.
A11YUITESTS: AN XCUI TESTING LIBRARY FOR ACCESSIBILITY A11yUITests: An XCUI Testing library for accessibility. A11yUITests is an extension to XCTestCase that adds tests for common accessibility issues that can be run as part of an XCUITest suite. I’ve written a detailed discussion of the tests available if you’re interested in changing/implementing these tests yourself. Alternatively, follow thisquick start guide.
HOW DO I GET MY APP AN ACCESSIBILITY AUDIT? An accessibility audit is part of the process of making an accessible app. But if you include accessibility throughout the process there should be no nasty surprises at the end, and importantly, don’t stop there. Include people with disabilities in user testing, encouragefeedback,
ANDROID LIVE REGIONS A Live Region is an element of your interface that will automatically announce it’s content through TalkBack whenever that content changes. This means you can up update your score and your TalkBack users will know without having to navigate to the scoreboard. Take this really simple game I’ve made. The aim is to score 1,000 points. TEST YOUR APP'S ACCESSIBILITY WITH EVINCED In your iOS app, navigate to the screen you want to audit, and in the Evinced desktop app hit the “Scan” button. After a brief pause you’ll see a screenshot of your app appear in the debugger with accessibility violations highlighted and labeled. The list of scanresults provides a
SWIFTUI ACCESSIBILITY: DYNAMIC TYPE SwiftUI Accessibility: Dynamic Type. Like all accessibility features, Dynamic Type is about customisability. Many of your customers, and maybe even you, are using Dynamic Type without even considering it an accessibility feature. Dynamic type allows iOS users to set the text to a size that they find comfortable to read. SWIFTUI ACCESSIBILITY: SEMANTIC VIEWS SwiftUI Accessibility: Semantic Views. Semantic views are not new to SwiftUI, but changes in SwiftUI mean creating them is simple. Semantic views are not so much a language feature. They’re more a technique for manipulating the accessible user interface and improving the experience for assistive technology users.MOBILE A11Y
Many people don’t realise dark mode is an accessibility feature. It’s often just considered a nice to have, a cool extra feature that power users will love.MOBILE A11Y
Mobile A11y. Mobile A11y is a collection of blogs and resources about how we as mobile developers can improve accessibility on mobiledevices.
RESOURCES | MOBILE A11Y Resources. This is a personally curated list of resources I have used and think others may find helpful too. I’m always looking for new high quality mobile accessibility and inclusion resources to add here.BLOG | MOBILE A11Y
A11y Box Android. Apr 26, 2020 | 1 minutes. An open-source example of Android's Accessability API. Android. Mobile A11y Blog. Blog.Resources.
A11YUITESTS: AN XCUI TESTING LIBRARY FOR ACCESSIBILITY A11yUITests: An XCUI Testing library for accessibility. A11yUITests is an extension to XCTestCase that adds tests for common accessibility issues that can be run as part of an XCUITest suite. I’ve written a detailed discussion of the tests available if you’re interested in changing/implementing these tests yourself. Alternatively, follow thisquick start guide.
HOW DO I GET MY APP AN ACCESSIBILITY AUDIT? An accessibility audit is part of the process of making an accessible app. But if you include accessibility throughout the process there should be no nasty surprises at the end, and importantly, don’t stop there. Include people with disabilities in user testing, encouragefeedback,
ANDROID LIVE REGIONS A Live Region is an element of your interface that will automatically announce it’s content through TalkBack whenever that content changes. This means you can up update your score and your TalkBack users will know without having to navigate to the scoreboard. Take this really simple game I’ve made. The aim is to score 1,000 points. TEST YOUR APP'S ACCESSIBILITY WITH EVINCED In your iOS app, navigate to the screen you want to audit, and in the Evinced desktop app hit the “Scan” button. After a brief pause you’ll see a screenshot of your app appear in the debugger with accessibility violations highlighted and labeled. The list of scanresults provides a
SWIFTUI ACCESSIBILITY: DYNAMIC TYPE SwiftUI Accessibility: Dynamic Type. Like all accessibility features, Dynamic Type is about customisability. Many of your customers, and maybe even you, are using Dynamic Type without even considering it an accessibility feature. Dynamic type allows iOS users to set the text to a size that they find comfortable to read. SWIFTUI ACCESSIBILITY: SEMANTIC VIEWS SwiftUI Accessibility: Semantic Views. Semantic views are not new to SwiftUI, but changes in SwiftUI mean creating them is simple. Semantic views are not so much a language feature. They’re more a technique for manipulating the accessible user interface and improving the experience for assistive technology users.MOBILE A11Y
Many people don’t realise dark mode is an accessibility feature. It’s often just considered a nice to have, a cool extra feature that power users will love.ABOUT MOBILE A11Y
About Mobile A11y. Mobile A11y is a collection of blogs and resources about how we as mobile developers can improve accessibility on mobile devices. From time to time the blog might also touch on related topics such as digital inclusion, and other topics around ethics in technology. The site is aimed at mobile developers and is written by a GUIDES | MOBILE A11Y SwiftUI. Jan 1, 0001 | 1 minutes. SwiftUI is Apple's new technology for building user interfaces on Apple platforms. Apple have made some very important accessibility choices with SwiftUI that mean accessibility is included by default. QUICK WINS | MOBILE A11Y Accessibility can seem daunting. It’s a huge subject and, much like any area of software development, no one can know everything and everyone is always a learner. QUICK WIN - START UI TESTING Quick Win - Start UI Testing. I’ll admit, adding UI testing to an app that currently doesn’t have it included is probably stretching the definition of quick win, but the aim here isn’t 100% coverage - QUICK WIN - SUPPORT LANDSCAPE Quick Win - Support Landscape. If you have a regulatory requirement to provide accessibility in your app (spoiler, you do) the chances are it will say you have a requirement to reach WCAG AA.While this is likely meaningless to anyone other an accessibility professionals, in short it means you are providing the minimum level of accessibility features required to make your app usable by the XCUITESTS FOR ACCESSIBILITY This test is valid for any accessible element, whether that’s a control, image, or text. I chose to check the accessibility label had a minimum of 2 characters, as 1 is most likely meaningless. Checking if the string is empty might work better for your app. XCTAssert (element.label.count > 2) ANDROID LIVE REGIONS A Live Region is an element of your interface that will automatically announce it’s content through TalkBack whenever that content changes. This means you can up update your score and your TalkBack users will know without having to navigate to the scoreboard. Take this really simple game I’ve made. The aim is to score 1,000 points. SWIFTUI ACCESSIBILITY SwiftUI Accessibility - Named Controls. One big accessibility improvement in SwiftUI comes in the form of named controls. Nearly all controls and some non-interactive views can take a Text view as part of their view builder.The purpose of this is to tie the meaning to thecontrol.
ACCESSIBILITY REVIEW: HUH? Accessibility Review: Huh? - International languages. The Accessibility Review series uses real world apps to provide examples of common accessibility issues and provide tips on how to fix them. Each of the developers has kindly volunteered their app to be tested. Huh? is a dictionary and thesaurus app from Peter Yaacoub.Enter a word into the search bar then choose a dictionary service. WRITING GREAT IOS ACCESSIBILITY LABELS Writing Great iOS Accessibility Labels. A good accessibility label lets your customer know exactly what a control does in as few words as possible, without having to rely on implied context.MOBILE A11Y
Mobile A11y. Mobile A11y is a collection of blogs and resources about how we as mobile developers can improve accessibility on mobiledevices.
RESOURCES | MOBILE A11Y Resources. This is a personally curated list of resources I have used and think others may find helpful too. I’m always looking for new high quality mobile accessibility and inclusion resources to add here.BLOG | MOBILE A11Y
A11y Box Android. Apr 26, 2020 | 1 minutes. An open-source example of Android's Accessability API. Android. Mobile A11y Blog. Blog.Resources.
QUICK WIN - SUPPORT LANDSCAPE Quick Win - Support Landscape. If you have a regulatory requirement to provide accessibility in your app (spoiler, you do) the chances are it will say you have a requirement to reach WCAG AA.While this is likely meaningless to anyone other an accessibility professionals, in short it means you are providing the minimum level of accessibility features required to make your app usable by the A11YUITESTS: AN XCUI TESTING LIBRARY FOR ACCESSIBILITY A11yUITests: An XCUI Testing library for accessibility. A11yUITests is an extension to XCTestCase that adds tests for common accessibility issues that can be run as part of an XCUITest suite. I’ve written a detailed discussion of the tests available if you’re interested in changing/implementing these tests yourself. Alternatively, follow thisquick start guide.
HOW DO I GET MY APP AN ACCESSIBILITY AUDIT? An accessibility audit is part of the process of making an accessible app. But if you include accessibility throughout the process there should be no nasty surprises at the end, and importantly, don’t stop there. Include people with disabilities in user testing, encouragefeedback,
TEST YOUR APP'S ACCESSIBILITY WITH EVINCED In your iOS app, navigate to the screen you want to audit, and in the Evinced desktop app hit the “Scan” button. After a brief pause you’ll see a screenshot of your app appear in the debugger with accessibility violations highlighted and labeled. The list of scanresults provides a
SWIFTUI ACCESSIBILITY: DYNAMIC TYPE SwiftUI Accessibility: Dynamic Type. Like all accessibility features, Dynamic Type is about customisability. Many of your customers, and maybe even you, are using Dynamic Type without even considering it an accessibility feature. Dynamic type allows iOS users to set the text to a size that they find comfortable to read. SWIFTUI ACCESSIBILITY: SEMANTIC VIEWS SwiftUI Accessibility: Semantic Views. Semantic views are not new to SwiftUI, but changes in SwiftUI mean creating them is simple. Semantic views are not so much a language feature. They’re more a technique for manipulating the accessible user interface and improving the experience for assistive technology users.MOBILE A11Y
Many people don’t realise dark mode is an accessibility feature. It’s often just considered a nice to have, a cool extra feature that power users will love.MOBILE A11Y
Mobile A11y. Mobile A11y is a collection of blogs and resources about how we as mobile developers can improve accessibility on mobiledevices.
RESOURCES | MOBILE A11Y Resources. This is a personally curated list of resources I have used and think others may find helpful too. I’m always looking for new high quality mobile accessibility and inclusion resources to add here.BLOG | MOBILE A11Y
A11y Box Android. Apr 26, 2020 | 1 minutes. An open-source example of Android's Accessability API. Android. Mobile A11y Blog. Blog.Resources.
QUICK WIN - SUPPORT LANDSCAPE Quick Win - Support Landscape. If you have a regulatory requirement to provide accessibility in your app (spoiler, you do) the chances are it will say you have a requirement to reach WCAG AA.While this is likely meaningless to anyone other an accessibility professionals, in short it means you are providing the minimum level of accessibility features required to make your app usable by the A11YUITESTS: AN XCUI TESTING LIBRARY FOR ACCESSIBILITY A11yUITests: An XCUI Testing library for accessibility. A11yUITests is an extension to XCTestCase that adds tests for common accessibility issues that can be run as part of an XCUITest suite. I’ve written a detailed discussion of the tests available if you’re interested in changing/implementing these tests yourself. Alternatively, follow thisquick start guide.
HOW DO I GET MY APP AN ACCESSIBILITY AUDIT? An accessibility audit is part of the process of making an accessible app. But if you include accessibility throughout the process there should be no nasty surprises at the end, and importantly, don’t stop there. Include people with disabilities in user testing, encouragefeedback,
TEST YOUR APP'S ACCESSIBILITY WITH EVINCED In your iOS app, navigate to the screen you want to audit, and in the Evinced desktop app hit the “Scan” button. After a brief pause you’ll see a screenshot of your app appear in the debugger with accessibility violations highlighted and labeled. The list of scanresults provides a
SWIFTUI ACCESSIBILITY: DYNAMIC TYPE SwiftUI Accessibility: Dynamic Type. Like all accessibility features, Dynamic Type is about customisability. Many of your customers, and maybe even you, are using Dynamic Type without even considering it an accessibility feature. Dynamic type allows iOS users to set the text to a size that they find comfortable to read. SWIFTUI ACCESSIBILITY: SEMANTIC VIEWS SwiftUI Accessibility: Semantic Views. Semantic views are not new to SwiftUI, but changes in SwiftUI mean creating them is simple. Semantic views are not so much a language feature. They’re more a technique for manipulating the accessible user interface and improving the experience for assistive technology users.MOBILE A11Y
Many people don’t realise dark mode is an accessibility feature. It’s often just considered a nice to have, a cool extra feature that power users will love.ABOUT MOBILE A11Y
About Mobile A11y. Mobile A11y is a collection of blogs and resources about how we as mobile developers can improve accessibility on mobile devices. From time to time the blog might also touch on related topics such as digital inclusion, and other topics around ethics in technology. The site is aimed at mobile developers and is written by a GUIDES | MOBILE A11Y SwiftUI. Jan 1, 0001 | 1 minutes. SwiftUI is Apple's new technology for building user interfaces on Apple platforms. Apple have made some very important accessibility choices with SwiftUI that mean accessibility is included by default. QUICK WIN - SUPPORT LANDSCAPE Quick Win - Support Landscape. If you have a regulatory requirement to provide accessibility in your app (spoiler, you do) the chances are it will say you have a requirement to reach WCAG AA.While this is likely meaningless to anyone other an accessibility professionals, in short it means you are providing the minimum level of accessibility features required to make your app usable by the SWIFTUI ACCESSIBILITY SwiftUI Accessibility - Named Controls. One big accessibility improvement in SwiftUI comes in the form of named controls. Nearly all controls and some non-interactive views can take a Text view as part of their view builder.The purpose of this is to tie the meaning to thecontrol.
SWIFTUI | MOBILE A11Y SwiftUI. SwiftUI is Apple’s new technology for building user interfaces on Apple platforms. Apple have made some very important accessibility choices with SwiftUI that mean accessibility is included by default. Our job as developers is to improve an accessible experience, not to create one. SWIFTUI ACCESSIBILITY: ATTRIBUTES An element’s Accessibility Label is the first string read by VoiceOver when landing on an accessible element. It’s also the string used to activate a control in Voice Control. You should think of this as the name of the element. Set an accessibility label on your SwiftUI element using the modifier .accessibility (label: Text("Send")).
ANDROID LIVE REGIONS A Live Region is an element of your interface that will automatically announce it’s content through TalkBack whenever that content changes. This means you can up update your score and your TalkBack users will know without having to navigate to the scoreboard. Take this really simple game I’ve made. The aim is to score 1,000 points. SWIFTUI ACCESSIBILITY Thanks for reading. This story is part of a series on SwiftUI Accessibility. Check out my other guides in this series: SwiftUI Accessibility SwiftUI Accessibility: Named Controls SwiftUI Accessibility: Images SwiftUI Accessibility: Dynamic Type SwiftUI Accessibility: Accessible User Interface SwiftUI Accessibility: Sort Priority SwiftUI Accessibility: Attributes SwiftUI Accessibility:Traits
SWIFTUI ACCESSIBILITY: USER SETTINGS SwiftUI Accessibility: User Settings. SwiftUI allows us to read environmental values that might affect how we want to present our UI. Things like size classes and locale for example. We also get the ability to read some of the user’s chosen accessibility settingsallowing us to
ACCESSIBILITY REVIEW: HUH? Accessibility Review: Huh? - International languages. The Accessibility Review series uses real world apps to provide examples of common accessibility issues and provide tips on how to fix them. Each of the developers has kindly volunteered their app to be tested. Huh? is a dictionary and thesaurus app from Peter Yaacoub.Enter a word into the search bar then choose a dictionary service. skip to content W3C SVG A blog about making mobile more accessible for all. Edited by RobWhitaker
dark theme:
MAIN NAVIGATION
Menu
* Home
* Blog
* Guides
* Quick Wins
* Resources
* Tags
* About
* RSS
ANDROID LIVE REGIONS Live Regions are one of my favourite accessibility features on Android. They’re a super simple solution to a common accessibility problem that people with visual impairments can stumble across. Say you have a game app, really any type of game. Your user interacts with the play area, and as they do, their score increases or decreases depending on your customer’s actions. In this example, the score display is separate to the element your customer is interacting with. For a blind or partially sighted user, how will they know their interaction has had a consequence against their score? In steps Live Regions. A Live Region is an element of your interface that will automatically announce it’s content through TalkBack whenever that content changes. This means you can up update your score and your TalkBack users will know without having to navigate to thescoreboard.
Take this really simple game I’ve made. The aim is to score 1,000 points. Handily there’s a button that will award you 1,000 points. To activate this button, a TalkBack user must navigate to the button, activate it, then navigate to the score area to know if the scoreupdated.
If we make the score TextView element a Live Region, there’s no need for this extra swipe. Once we update the score, TalkBack will read itright away.
So how do we take advantage of this advanced technique? It must take a ton of coding to achieve this, right? Well, ready?…
android:accessibilityLiveRegion="polite" /> Or if you’re setting it dynamically in Kotlin: score.accessibilityLiveRegion = View.ACCESSIBILITY_LIVE_REGION_POLITE That’s it. Android and TalkBack do the rest for you. USE LIVE REGIONS WISELY Live Regions are a powerful tool, but it’s essential to know when and where to use them. Using them unnecessarily will add noise to your interface and make it confusing. More than one per screen seems unnecessary to me, and most screens shouldn’t have any at all. Any area that updates a lot, such as a timer, really shouldn’t be marked as a Live Region.
BE POLITE
You’ll notice in the example code above, they include the word polite. As a rule, this is the option you’ll use. This means TalkBack will wait to complete any current utterances before speaking the new Live Region value. The alternative is assertive. Assertive will interrupt any current utterances. Use this only if absolutely necessary as interrupting content can be confusing and frustrating. Live Regions are a potent tool when used in the right situations, and all it needs from you is one line of code. Consider where you can take your app’s accessibility to the next level with this technique. Thanks for reading!
Did you find this resource valuable? Please consider supporting Mobile A11y by sending a tip or sharing this blog. Developing Inclusive Mobile Apps: Building Accessible Apps for iOS and Android is available now from Apress and Amazon
.
Copyright © 2021 - Rob Whitaker Twitter: @MobileA11y . Email: a11y@mobilea11y.com. Made with Hugo . Themed by Cupper .
…
android:accessibilityLiveRegion="polite" /> Or if you’re setting it dynamically in Kotlin: score.accessibilityLiveRegion = View.ACCESSIBILITY_LIVE_REGION_POLITE That’s it. Android and TalkBack do the rest for you. USE LIVE REGIONS WISELY Live Regions are a powerful tool, but it’s essential to know when and where to use them. Using them unnecessarily will add noise to your interface and make it confusing. More than one per screen seems unnecessary to me, and most screens shouldn’t have any at all. Any area that updates a lot, such as a timer, really shouldn’t be markedas a Live Region.
BE POLITE
You’ll notice in the example code above, they include the word polite. As a rule, this is the option you’ll use. This means TalkBack will wait to complete any current utterances before speaking the new Live Region value. The alternative is assertive. Assertive will interrupt any current utterances. Use this only if absolutely necessary as interrupting content can be confusing and frustrating. Live Regions are a potent tool when used in the right situations, and all it needs from you is one line of code. Consider where you can take your app’s accessibility to the next level with this technique.Thanks for reading!
Did you find this resource valuable? Please consider supporting Mobile A11y by sending a tip or sharing this blog. Developing Inclusive Mobile Apps: Building Accessible Apps for iOS and Android is available now from Apressand Amazon
.
Copyright © 2021 - Rob Whitaker Twitter: @MobileA11y . Email: a11y@mobilea11y.com. Made with Hugo . Themed by Cupper.
Details
Copyright © 2024 ArchiveBay.com. All rights reserved. Terms of Use | Privacy Policy | DMCA | 2021 | Feedback | Advertising | RSS 2.0