WebAIM - Web Accessibility In Mind

E-mail List Archives

Multiple questions

for

From: megha patangi
Date: Jun 10, 2024 11:37PM

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