WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Web/ native app testing

for

From: Dean.Vasile@outlook.com
Date: Jun 11, 2024 4:48AM

Absolutely, Megha! Here's a breakdown of resources and tips for mobile app accessibility testing with a screen reader:
Key Resources:
* WCAG 2.1 Success Criteria: The Web Content Accessibility Guidelines are your foundation. Focus on the criteria relevant to mobile and touch interactions.
* Mobile specific examples: [invalid URL removed]
* Mobile Testing Guides:
* WebAIM: Offers specific guidance on testing mobile web content.
* Deque University: Provides comprehensive training on mobile accessibility.
* AccessibilityOz: Has articles dedicated to mobile testing.
* Platform-Specific Guidelines:
* iOS: Apple's Human Interface Guidelines include accessibility sections.
* Android: Google's Material Design guidelines have accessibility considerations.
Testing Checklist (Not Exhaustive):
* Navigation:
* Can you easily navigate the app using only gestures (swipes, taps)?
* Do screen readers announce headings, links, buttons, and other interactive elements clearly?
* Can you access all content without needing a mouse or trackpad?
* Interactive Elements:
* Do buttons and links have clear labels and are they easy to activate?
* Do form fields have labels and instructions that are read by the screen reader?
* Are dropdowns, modals, and other interactive elements accessible and announced correctly?
* Do you hear distinct feedback when interacting with elements (e.g., sounds or announcements)?
* Content:
* Is all text content readable by a screen reader?
* Are images and other non-text content accompanied by alternative text descriptions?
* Are videos captioned and audio content transcribed?
* Dynamic Content:
* Are changes to content announced to screen reader users (e.g., new notifications)?
* Can you control the rate at which content updates are announced?
* Gestures:
* Can you perform all actions without complex gestures that might be difficult for users with motor impairments?
Specific Components:
* Dropdowns: Screen readers should announce the currently selected option and provide ways to navigate through and select other options.
* Modals: The screen reader should announce that a modal has appeared and allow you to navigate its content.
* Tablist/Tabpanel: Screen readers should clearly indicate the active tab and allow you to switch between tabs.
* Links/Buttons: The screen reader should announce the role (link or button) along with the label or text content.
* Form Elements: Each form element should be clearly labeled and instructions should be provided.
Tips:
* Use multiple screen readers: Test with both TalkBack (Android) and VoiceOver (iOS) as they might behave differently.
* Explore different navigation modes: Try navigating by touch, gestures, and keyboard (if applicable) to ensure flexibility.
* Get feedback from other users: Ask other screen reader users to test the app and provide feedback.
Let me know if you have more specific questions!

Dean Vasile


617-799-1162
Dean Vasile


617-799-1162

> On Jun 11, 2024, at 1:45 AM, megha patangi < <EMAIL REMOVED> > wrote:
>
> Hello all,
> I am new into web/ native mobile app testing. I am a native screen reader
> user of android device, but still do not have best knowledge of best
> practices to test web/ native applications.
> Everything which we test on web browser may not be applicable for native or
> web applications, some components are not supported and also screen reader
> read out may differ.
>
> Is there any document or checklist available on what could be tested on
> applications on mobile devices, how to test and what is the
> expectations. Specially with respect to components, how to navigate with
> talk back/ voice over on and what is the right output to expect?
> For example: few which I struggle are drop downs, modals, tablist and tab
> panel, link/ button whether SR will read element role or not, various form
> elements, and likewise.
>
> Regards,
> Megha
> > > >