WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WebAIM-Forum Digest, Vol 231, Issue 5

for

From: megha patangi
Date: Jun 11, 2024 11:34PM

Thank you Dean for the responses. This helps a lot

On Tue, Jun 11, 2024 at 11:30 PM < <EMAIL REMOVED> >
wrote:

> Send WebAIM-Forum mailing list submissions to
> <EMAIL REMOVED>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://list.webaim.org/cgi-bin/mailman/listinfo/webaim-forum
> or, via email, send a message with subject or body 'help' to
> <EMAIL REMOVED>
>
> You can reach the person managing the list at
> <EMAIL REMOVED>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
> Today's Topics:
>
> 1. Re: [EXTERNAL] - Video Accessibility (David Engebretson Jr.)
> 2. Multiple questions (megha patangi)
> 3. Web/ native app testing (megha patangi)
> 4. Re: Multiple questions ( <EMAIL REMOVED> )
> 5. Re: Web/ native app testing ( <EMAIL REMOVED> )
> 6. Re: [External Email] Re: Video Accessibility
> (Webmaster Duval Schools)
> 7. Document format for alternative for time-based media (Steve Green)
>
>
>
> ---------- Forwarded message ----------
> From: "David Engebretson Jr." < <EMAIL REMOVED> >
> To: "'WebAIM Discussion List'" < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Mon, 10 Jun 2024 14:48:37 -0700
> Subject: Re: [WebAIM] [EXTERNAL] - Video Accessibility
> And AblePlayer does have an interactive transcript which can be useful
> from a multi-modal UI/UX perspective.
>
> Cheers,
> David
>
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Hayman, Douglass
> Sent: Monday, June 10, 2024 10:19 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] [EXTERNAL] - Video Accessibility
>
> For several years there has been a contest between the Oz player and
> AblePlayer. Oz has had limited resources to keep up to date from what I've
> heard.
>
> Here is the AblePlayer example page
>
> https://ableplayer.github.io/ableplayer/demos/
>
> Try out some of the demos to see the number of player controls and
> capabilities.
>
> One can change speed, turn audio description on/off, see transcript, see
> breakout window with sign language interpreter and more.
>
> Doug Hayman
> IT Accessibility Coordinator
> Information Technology
> Olympic College
> <EMAIL REMOVED>
> (360) 475-7632
>
>
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Radhika Soni
> Sent: Monday, June 10, 2024 7:56 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: [EXTERNAL] - [WebAIM] Video Accessibility
>
> CAUTION: This email came from a non-OC system or external source. Beware
> of phishing and social engineering!
>
>
> Hi All,
>
> I hope you're having a great Monday! I have a quick question about video
> accessibility. I wanted to check if you have any recommendations for making
> only videos accessible. According to WCAG AA guidelines, we need to provide
> audio descriptions or transcripts for videos only. However, I haven't seen
> many websites doing this for embedded videos on their homepages. Do you
> have any inspiration or visual designs for the best way to display many
> controls on an embedded video?
> Thanks in advance for your help!
>
> Regards,
> Radhika
> > > at http://webaim.org/discussion/archives
> > > > at http://webaim.org/discussion/archives
> >
>
>
>
>
> ---------- Forwarded message ----------
> From: megha patangi < <EMAIL REMOVED> >
> To: webaim-forum < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Tue, 11 Jun 2024 11:07:35 +0530
> Subject: [WebAIM] Multiple questions
> Hello Web Aim Team,
>
> I have following different questions, in very different scenarios:
>
> 1. We have used input box in one of our very complex widget for better
> focus management. this is just in code but not available for anyone to use,
> neither visible on screen. since this is interactive element we cannot use
> aria-hidden on it.
> so what could be the best way to hide it so that it does not effect user
> adversely and also is no longer flagged in automated test?
>
> 2. Secondly, I have a use case where on a single UI there may happen to
> witness multiple dynamic changes in parallel, like timer is running,
> notifications are coming, articles are getting updated and many more. if we
> give them all aria-live even with right value of assertive/ polite as per
> their priority, but still there is too much to listen and definitely only
> the one assertive will get heard, others will suppress. on top of it,
> screen is becoming too noisy.
> is there any idea/ suggestion/ technique with which such scenario can be
> handled better?
>
> 3. Finally, if we have a very visual based component say for example google
> maps and they are not end to end accessible then what should be our
> approach for it. I have a similar component which has lot to consume
> visually. it is like a huge organization chart with various nodes and to
> perceive right information whole chart needs to be looked together to get
> the relationship between two nodes.
> Even we make these keyboard accessible, but for a screen reader they might
> be able to navigate but too difficult to perceive same amount of
> relationship information.
> Any suggestions on what best can be done here? Any maximum acceptable
> approach which is useful as well as passes WCAG?
>
> Regards,
> Megha
>
>
>
>
> ---------- Forwarded message ----------
> From: megha patangi < <EMAIL REMOVED> >
> To: webaim-forum < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Tue, 11 Jun 2024 11:15:00 +0530
> Subject: [WebAIM] Web/ native app testing
> 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
>
>
>
>
> ---------- Forwarded message ----------
> From: " <EMAIL REMOVED> " < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Tue, 11 Jun 2024 10:42:11 +0000
> Subject: Re: [WebAIM] Multiple questions
> Dear Mega,
> * Hidden Input Box:
> * Use display:none or visibility:hidden in CSS to hide the input box.
> * These styles prevent the input box from affecting layout or screen
> readers.
> * Automated tests may still flag it, but this can be addressed by adding
> an attribute like data-test="ignore".
> * Multiple Dynamic Updates:
> * Use aria-live="polite" for most updates, reserving aria-live="assertive"
> for critical alerts.
> * Prioritize updates and only announce the most important ones.
> * Consider a notification center where users can review less urgent
> updates.
> * Complex Visual Components:
> * Provide a text summary of the key information conveyed by the visual
> component.
> * If possible, offer alternative formats (e.g., tabular data) for better
> accessibility.
> * Consider a simplified version of the component for screen reader users.
> * Acknowledge limitations in accessibility and provide clear instructions
> for users who may need assistance.
>
> Dean Vasile
>
>
> 617-799-1162
> Dean Vasile
>
>
> 617-799-1162
>
> > On Jun 11, 2024, at 1:37 AM, megha patangi < <EMAIL REMOVED> >
> wrote:
> >
> > Hello Web Aim Team,
> >
> > I have following different questions, in very different scenarios:
> >
> > 1. We have used input box in one of our very complex widget for better
> > focus management. this is just in code but not available for anyone to
> use,
> > neither visible on screen. since this is interactive element we cannot
> use
> > aria-hidden on it.
> > so what could be the best way to hide it so that it does not effect user
> > adversely and also is no longer flagged in automated test?
> >
> > 2. Secondly, I have a use case where on a single UI there may happen to
> > witness multiple dynamic changes in parallel, like timer is running,
> > notifications are coming, articles are getting updated and many more. if
> we
> > give them all aria-live even with right value of assertive/ polite as per
> > their priority, but still there is too much to listen and definitely only
> > the one assertive will get heard, others will suppress. on top of it,
> > screen is becoming too noisy.
> > is there any idea/ suggestion/ technique with which such scenario can be
> > handled better?
> >
> > 3. Finally, if we have a very visual based component say for example
> google
> > maps and they are not end to end accessible then what should be our
> > approach for it. I have a similar component which has lot to consume
> > visually. it is like a huge organization chart with various nodes and to
> > perceive right information whole chart needs to be looked together to get
> > the relationship between two nodes.
> > Even we make these keyboard accessible, but for a screen reader they
> might
> > be able to navigate but too difficult to perceive same amount of
> > relationship information.
> > Any suggestions on what best can be done here? Any maximum acceptable
> > approach which is useful as well as passes WCAG?
> >
> > Regards,
> > Megha
> > > > > > > > >
>
>
> ---------- Forwarded message ----------
> From: " <EMAIL REMOVED> " < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Tue, 11 Jun 2024 10:48:51 +0000
> Subject: Re: [WebAIM] Web/ native app testing
> 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
> > > > > > > > >
>
>
> ---------- Forwarded message ----------
> From: Webmaster Duval Schools < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Tue, 11 Jun 2024 12:28:31 +0000
> Subject: Re: [WebAIM] [External Email] Re: Video Accessibility
> Dax,
>
> Quick question, all video need to have that audio descriptions to be ADA
> compliant?
>
> From: WebAIM-Forum < <EMAIL REMOVED> > on behalf of
> Dax Castro < <EMAIL REMOVED> >
> Reply-To: WebAIM Discussion List < <EMAIL REMOVED> >
> Date: Monday, June 10, 2024 at 12:57 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: [External Email] Re: [WebAIM] Video Accessibility
>
> This message was sent from outside the district. Please do not click links
> or open attachments unless you recognize the source of this email and know
> the content is safe.
> This message was sent from outside the district. Please do not click links
> or open attachments unless you recognize the source of this email and know
> the content is safe.
>
> This is a good example of audio descriptions.
> https://vimeo.com/820638084/f9d28374f4<
> https://vimeo.com/820638084/f9d28374f4>
>
> OZ Player has accessible controls.
> https://www.accessibilityoz.com/ozplayer/<
> https://www.accessibilityoz.com/ozplayer>
>
>
> Thanks!
>
> Dax Castro, ADS
> Certified Digital Accessibility Trainer
> Accessibility Advocate | IAAP
> www.accessibilityUnraveled.com<;http://www.accessibilityUnraveled.com>;
>
> Chax Chat
> Accessibility Podcast
>
> 916.856.9347
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Radhika Soni
> Sent: Monday, June 10, 2024 7:56 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: [WebAIM] Video Accessibility
>
> Hi All,
>
> I hope you're having a great Monday! I have a quick question about video
> accessibility. I wanted to check if you have any recommendations for making
> only videos accessible. According to WCAG AA guidelines, we need to provide
> audio descriptions or transcripts for videos only. However, I haven't seen
> many websites doing this for embedded videos on their homepages. Do you
> have any inspiration or visual designs for the best way to display many
> controls on an embedded video?
> Thanks in advance for your help!
>
> Regards,
> Radhika
> > > http://list.webaim.org>; List archives at
> http://webaim.org/discussion/archives<;
> http://webaim.org/discussion/archives>;
> > > > http://list.webaim.org/>;
> > http://webaim.org/discussion/archives>;
> >
> >
> This communication may contain privileged and confidential information
> intended only for the addressee(s) named above. If you are not the intended
> recipient, you are hereby notified that any review, dissemination,
> distribution or duplication of this communication is strictly prohibited.
> If you are not the intended recipient, please notify the sender by reply
> email and destroy all copies of the original message. Under Florida law,
> e-mail addresses are public records. If you do not want your e-mail address
> released in response to a public records request, do not send electronic
> mail to this entity. Instead, contact this office by phone or in writing.
> Florida has broad public records laws and virtually all written
> communications are public records unless specifically deemed confidential
> pursuant to state or federal law.
>
>
>
> ---------- Forwarded message ----------
> From: Steve Green < <EMAIL REMOVED> >
> To: " <EMAIL REMOVED> " < <EMAIL REMOVED> >
> Cc:
> Bcc:
> Date: Tue, 11 Jun 2024 15:41:16 +0000
> Subject: [WebAIM] Document format for alternative for time-based media
> The definition of "alternative for time-based media" states that this is a
> "document including correctly sequenced text descriptions of time-based
> visual and auditory information and providing a means for achieving the
> outcomes of any time-based interaction". What document formats are
> acceptable? HTML and text, of course, but what about RTF, Word and PDF, as
> long as they are WCAG conformant? As far as I can tell, they are all
> acceptable.
>
> Please note that the question is strictly regarding WCAG conformance, not
> best practice or user experience.
>
> https://www.w3.org/TR/WCAG21/#dfn-alternative-for-time-based-media
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
> > > > >