- From: Ash Ta <duc.ta.740@gmail.com>
- Date: Fri, 15 Jan 2021 15:23:28 -0800
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: w3c-wai-ig@w3.org
- Message-ID: <CACsk6ExSQsbLCUHpcQBr4MekquPzcU3f0Q2d-vU69y9RR_UJoA@mail.gmail.com>
Hi Patrick, I cannot access from the back end code. Thus, no idea what it looks like. You are correct. The hint is the additional description. I don’t know why it have that strange behavior. If i change to aria-live polite, it only fix the first two fields. Not sure why. Best On Fri, Jan 15, 2021 at 3:13 PM Patrick H. Lauke <redux@splintered.co.uk> wrote: > On 15/01/2021 22:26, Ash Ta wrote: > > > 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? > > Without seeing the code, or being able to check it in action, this is > difficult to debug/make an assessment. It sounds like the "hint" > (assuming it's like an additional description or tooltip that shows up > when a form field gets focus?) is "hanging around" somehow and not being > removed fast enough or getting blanked? I would try and run this while > keeping an eye on the actual DOM / the element with aria-live, to verify > when/if its contents get changed appropriately when a form field > receives or loses focus. > > P > -- > Patrick H. Lauke > > https://www.splintered.co.uk/ | https://github.com/patrickhlauke > https://flickr.com/photos/redux/ | https://www.deviantart.com/redux > twitter: @patrick_h_lauke | skype: patrick_h_lauke > >
Received on Friday, 15 January 2021 23:23:52 UTC