Re: Technique F9

Just for clarity, I said, 'what happens if tabbing away initiates a change of context' given in the  case of comboboxes tabbing away also sets the value

Thanks

Sarah

Sent from Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Ms J <ms.jflz.woop@gmail.com>
Sent: Thursday, February 22, 2024 11:02:35 AM
To: w3c-wai-ig@w3.org <w3c-wai-ig@w3.org>
Subject: Re: Technique F9

Hi Patrick

Not by default but in my examples it does because a modal dialog is unexpectedly triggered when I change the value.

So, slightly different examples, I have two components. One is a <select> and when I press 'down' a dialog is triggered. This prevents me reading the options. Changing the value (by selecting an option) triggers a modal dialog so I can't read the options without being interrupted. This fails 'on input'

But I also have a read only combobox. This time, pressing down does not trigger the dialog and I can read the options. This is because it works differently from a <select> - a <select> the value changes when I press down. A combobox, the value isn't set until I press tab. When I press tab (and set the value) I then trigger a dialog. So I don't have the conventional on input problem of being unable to read the options - it's more aligned with the AAA change on request fail.

The only additional difference I can see from the equivalent AAA fail, for example, with a <select> that behaved similarly (aka didn't trigger a dialog on input, but did if I tabbed away) I could set the value before initiating the change of context. However, with the combobox, I can't really set the value without having to press tab or enter or space. So setting the value comes at the same time as the change of context... not sure how much difference that makes...

Thanks

Sarah

Sent from Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Ms J <ms.jflz.woop@gmail.com>
Sent: Wednesday, February 21, 2024 5:11:09 PM
To: w3c-wai-ig@w3.org <w3c-wai-ig@w3.org>
Subject: Re: Technique F9

Sorry, I'm doing the annoying thing of double emailing

So if you have two controls and for both tabbing away initiates a change of context

If this is a <select> it fails 3.2.5
But if this use a select only combobox it fails 3.2.2? Because the value is changed at the same time as you tab away?

Thanks

Sarah

Sent from Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Ms J <ms.jflz.woop@gmail.com>
Sent: Wednesday, February 21, 2024 5:02:40 PM
To: w3c-wai-ig@w3.org <w3c-wai-ig@w3.org>
Subject: Technique F9

Hello again

Technique F9: changing the context when a user removes focus from a form element. This fails 3.2.5 change on request AAA

However, what happens for comboboxes like this one where the value is only set when you press tab, enter or space, because then you are initiating a change of context 'on input' surely? So 3.2.2 on input? https://www.w3.org/WAI/ARIA/apg/patterns/combobox/examples/combobox-select-only/

Thanks

Sarah

Sent from Outlook for iOS<https://aka.ms/o0ukef>