Re: SCR37 replacement

Hi Wilco,

If I understand your perspective, is it that: The opening of the model does not impact the focus order, so it is orthogonal to the SC?

I think others (including me) have a slightly wider interpretation. The SC doesn’t say the tab-order, it’s about the focus order.

If you open a dialogue, the best way to preserve meaning and operability is to do what the new technique says (i.e. move the focus to the dialog).

It can apply when you use a button which moves the focus, not just tab order. In that way dynamic interfaces can be covered.

As a sufficient technique it isn’t the *only* way to do it, you could use content-ordering rather than focus management, but this is *a* way to meet it.

Kind regards,

-Alastair



From: Wilco Fiers <wilco.fiers@deque.com>
Date: Friday, 10 November 2023 at 15:11

Hey Alastair,
I'm happy with this as an advisory technique. I think as a sufficient technique this is confusing. The part of SC37 that made it directly relevant to SC 2.4.3 was test 3 "Check that, once opened, the dialog is next in the tab order.". In the rewrite, that part was replaced with a test that is no longer about the order in which elements are in sequential focus navigation. "When the dialog is opened, check that focus is placed inside it.". I support that change. That is a better way to do this, but it removed the only thing in SC37 that was about the order in which elements appear when a user navigates the page with tab focus.


On Tue, Nov 7, 2023 at 2:20 PM Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
Hi everyone,

Last week we had a discussion about replacing SCR37, a technique to create a custom dialog:
https://www.w3.org/WAI/WCAG22/Techniques/client-side-script/SCR37.html


It is referenced from 2.4.3 Focus Order, as a sufficient technique under “Changing a Web page dynamically”.

The current technique is old and does not follow modern best practices (e.g. it is asking that dialogs be ‘next’ in the tab order, rather than focus is moved). It is also possible to achieve the same thing with HTML, so the proposal was to change it to an HTML technique:
https://github.com/w3c/wcag/pull/3024/<https://github.com/w3c/wcag/pull/3024/files>

A couple of people wanted to understand the context better, and/or thought it was going beyond the requirements of the SC.

NB: Sufficient techniques can go beyond what is required by an SC. They are one way of fulfilling the SC, there can be others.

The preview of the technique is here:
https://raw.githack.com/w3c/wcag/re-write-scr37-as-html-technique/techniques/html/H-creating-dialogs-with-the-html-dialog-element.html


Does anyone have move specific things that we could change to clear objections?

Kind regards,

-Alastair

--

@alastc / www.nomensa.com<http://www.nomensa.com/>




--
Wilco Fiers
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator ACT Task Force
[cid:BCBD7D4B-677E-4B95-AE3F-60005DBD9EE4]