- From: Taliesin Smith <talilief@gmail.com>
- Date: Sat, 16 Jan 2021 13:50:44 -0330
- To: Ash Ta <duc.ta.740@gmail.com>
- Cc: WAI IG <w3c-wai-ig@w3.org>
- Message-Id: <E654AC7B-FD74-4E84-BF7F-1529CAC08D87@gmail.com>
Hi again Doc Ta, With developer tools in your browser, you can check the code. You can simply “View Page Source”, or inspect what is happening on the element with a web inspector tool. The tools vary among browsers, but they are generally bunched under a Develop or Tools menu. Of course, it might not tell the entire story, but it could help with trouble shooting. I don’t do implementation anymore, so I can’t recommend a favourite (sorry). You can also use an HTML validation tool, or have the developer use such a tool to make sure there are no syntax errors in the code. I would recommend running the relevant URL (or code) through the W3C’s markup validation service. It will point you to any errors in the code. https://validator.w3.org/ <https://validator.w3.org/> Just as a note, I have found in my work with ARIA Live and the alert settings that polite and assertive are not implemented consistently across AT and Browsers. Things have improved a lot, and are far better today than 5 years ago. Many things can go wonky, though, when using ARIA live and screen readers. You need to know what is under the hood, and to know how it is implemented. If that is not possible, and you don’t think the behavior is an ideal accessible user interface, you should report it as a bug regardless of any success criteria, and give to someone you can look at the code. All the best, Taliesin Smith talilief@gmail.com ~.~.~ Also reachable at: Taliesin.Smith@colorado.edu Inclusive Design Researcher PhET Interactive Simulations https://phet.colorado.edu/en/accessibility Physics Department University of Colorado, Boulder > On Jan 16, 2021, at 1:19 PM, Ash Ta <duc.ta.740@gmail.com> wrote: > > Hi, > > I check the front end code via browser, i see there is aria live alerts too. That is kinda strange to me. Bt if it is needed. That is what it is. But the main problem is why it is announced twice. Once at the current form. The other at the other form. Scratch my head for a night already. > > > > Best, > Duc Ta > > On Sat, Jan 16, 2021 at 8:05 AM <talilief@gmail.com <mailto:talilief@gmail.com>> wrote: > Hi Ash Ta, > Are you sure it is ARIA Live alerts that is being used for hints? > > Depending on the situation, for example, if this is just a simple form with form controls and help text, many people would choose to use “aria-describedby” to provide automatic help text. > > Of course, I am not fully aware of your design requirements so I can’t say what your site needs, but aria-describedby is way simpler from an implementation perspective than ARIA Live alerts. > > Best of luck, > Taliesin > > > > Sent from my iPhone > > > On Jan 15, 2021, at 19:02, Ash Ta <duc.ta.740@gmail.com <mailto:duc.ta.740@gmail.com>> wrote: > > > > Hi, > > > > I checked my company website. They use aria-live assertive. When i navigate through all the forms via tab key, the hint in the previous form is announced at the current form before the current form hint is announced. I change it to polite. The first two are fixed in announcing the hint. However, the rest still have the same abnormal behavior. Is it voice over issue? Or is it aria-live issue? Or is it due to the nature of javascript thus it changes back to the old coding? > > > > > > Best
Received on Saturday, 16 January 2021 17:21:00 UTC