Tech using role log

[mbgower]

new technique for 4.1.3 Status Messages
https://rawgit.com/w3c/wcag/tech-using-role-log/techniques/aria/aria-log-role.html

Links go to working examples which have a separate pull request #436

[DavidMacDonald]

• It appears the first example once the "send" button is sent gives "undefined" if it is hit more than once.
• The default value for aria-relevant is "additions text" so it doesn't need to be added to the second example. Perhaps a description of the default behaviour would work there.

When the aria-relevant attribute is not provided, the default value, additions text, indicates that text modifications and node additions are relevant, but that node removals are irrelevant.

https://www.w3.org/TR/wai-aria-1.1/#aria-relevant

[mraccess77]

Some have even suggested that we should avoid using aria-relevant altogether.

https://medium.com/dev-channel/why-authors-should-avoid-aria-relevant-5d3164fab1e3

[mbgower]

re: aria-relevant

I can take this out for now. I do think there is a case to be made for using it when a 'busy' message disappears (i.e., a user with vision sees the busy message go away and starts working, but the blind user is never notified of the removal of 'busy' so just waits for an update that never is announced), so I may tackle it when I get to that technique/use case -- although I agree the AT support is spotty right now.

[mbgower]

It appears the first example once the "send" button is sent gives "undefined" if it is hit more than once.

Disabled Send button to make it one-time in #436

[alastc]

Using role=log to improve AT support

Should the main heading talk about "improve AT support"?

How about: "Using role=log to identify sequential information updates"

Also, I might be misunderstanding aria-atomic but wouldn't 'false' mean that it reads the whole thing at once? That seems to be the opposite of what is desirable here.

Also, the procedure seems self-fulfilling, where a log is marked up as a log. Could it be something like:

On a page that contains sequentially updating information:

1. Check that the container of the information is given a role of log.

[mbgower]

@alastc in regard to your question about aria-atomic, if it is set to false (the default for log) then it will only read the changes, not the entire contents. So your understanding seems to be opposite to the implementation. The following is from aria 1.1 spec:

If none of the ancestors have explicitly set aria-atomic, the default is that aria-atomic is false, and assistive technologies will only present the changed node to the user.
If aria-atomic is explicitly set to false, assistive technologies will stop searching up the ancestor chain and present only the changed node to the user.
If aria-atomic is explicitly set to true, assistive technologies will present the entire contents of the element, including the author-defined live region label if one exists.

Made your suggested changes to the title and test procedure wording.

[alastc]

Thanks Mike, I haven't used atomic in anger yet.

I just assumed that 'atomic' meant peice by peice, therefore 'true' would mean per-change, and false would mean the whole lot. I shall update my mental model ;-)