- From: David MacDonald <david100@sympatico.ca>
- Date: Tue, 30 May 2017 17:21:54 -0400
- To: Detlev Fischer <detlev.fischer@testkreis.de>
- Cc: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CAAdDpDb2XfhyErBw=1SMTJ_DrX_qgdCmTZR+EBJhf-j3UayHFw@mail.gmail.com>
> What this new content is missing is a corresponding role and is covered by SC 4.1.2 even now. 4.1.2 covers interactive components. This is wider, covering all content, and simpler at the same time. Requiring a summary message like the examples in the Understanding. The Understanding can also explain those things above the current requirements of 4.1.2 > Exception #1 to proposed SC suggests the new content could be associated with the trigger element. This SC would be triggered even when an error message is placed next to a failed field and is associated say via aria-describedby and focus is placed on the field when the form is presented with errors... because the error message is not associated with the submit button. That is a programmatic association and is sufficient > I am assuming this form has no global message above the form like 3 errors present / form submission failed. The primary technique would be for an announcement that there are "x errors on the page" > A global message needs role=alert or aria-live=assertive. Yes that would be a technique, however I would not recommend "assertive" unless a house is burning down. better to use polite as per the aria spec > Change in count of cart or remaining characters in a text area is updated in an element that needs role=status with aria-live=polite. Yes Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd GitHub <https://github.com/DavidMacDonald> www.Can-Adapt.com <http://www.can-adapt.com/> * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html> On Tue, May 30, 2017 at 5:10 PM, David MacDonald <david100@sympatico.ca> wrote: > > ?? Do we have techniques for doing this? > > Yes, in all major technologies. > > >> For example in a game or simulation - there will continual changes of > content. There is no exception for this — so is there a technique that > should be used in these situations to indicate that there are continuously > changing content? > > We can place a note on the Draft: "The working group is seeking input to > account for situations where there is frequent, or constant updating." > > >> Or is this ONLY supposed to apply to content that changes in response > to a user action. > > It applies to all changes to the content currently. It could be narrowed > for user initiated changes but the general feeling is that it should > include all changes to content that are part of the primary purpose of the > page. > > >> If you DON’T mean changes due to user action — then for dynamic content > (constantly changing) content is a simple notice someplace that says that > the page has continually changing content sufficient? or would the page > need to stream a constant flow of notifications through some mechanism that > is supported by AT? > > We could provide something like that. However, I would like to hear what > the public has to say. There was an exception for over 5 notifications a > minute, but it was dropped. Your language might be better. We want to > ensure however there is not an exemption for things like chat widgets, > where a ping that a comment was posted is key to having a fluent > conversation. This is the usual behavipur anyway of chat programs. > > > Cheers, > David MacDonald > > > > *Can**Adapt* *Solutions Inc.* > > Tel: 613.235.4902 <(613)%20235-4902> > > LinkedIn > <http://www.linkedin.com/in/davidmacdonald100> > > twitter.com/davidmacd > > GitHub <https://github.com/DavidMacDonald> > > www.Can-Adapt.com <http://www.can-adapt.com/> > > > > * Adapting the web to all users* > * Including those with disabilities* > > If you are not the intended recipient, please review our privacy policy > <http://www.davidmacd.com/disclaimer.html> > > On Tue, May 30, 2017 at 4:39 PM, Detlev Fischer < > detlev.fischer@testkreis.de> wrote: > >> +1 >> >> >
Received on Tuesday, 30 May 2017 21:22:30 UTC