Nickname:
Title:
State: RAISED OPEN PENDINGREVIEW CLOSED POSTPONED
Product: None AccNam AAM 1.2 ARIA 1.0 ARIA 1.0 Authoring Practices ARIA 1.0 Implementation Guide ARIA 1.0 Primer ARIA 1.0 Test Plan ARIA 1.1 ARIA 1.1 Authoring Practices ARIA 1.1 Core Mapping Specification ARIA 1.1 Name Computation ARIA 1.1 Test Plan ARIA 1.2 ARIA 1.2 Core AAM specification ARIA 2.0 ARIA 2.0 Authoring Practices ARIA 2.0 Core AAM ARIA 2.0 Name Calculation ARIA HTML 5 Implementation Guide CSS AAM Digital Publishing AAM Digital Publishing Roles Module Miscellaneous SVG AAM Accessibility Mapping spec. WCAG 2 Techniques for ARIA
Raised By: Sina Bahram Aditya Bajaj Benjamin Beaudry Curt Bellew Zoë Bijl Shari Butler ANDREA CARDONA Dominic Cooney Michael Cooper James Craig Joanmarie Diggs Isaac Durazo Howard Edwards James Edwards Frank Elavsky Mayuri Faldu Steve Faulkner Reinaldo Ferraz Alexander Flenniken Bryan Garaventa Rashmi Garimella Matt Garrish Jaunita George Ariella Gilmore Michael Goddard Glen Gordon Shirisha Gubba Jon Gunderson Markku Hakkinen Sarah Higley Hans Hillen Isabel Holdsworth Stanley Hon Patrick Hung Matthew King Greta Krafsig Peter Krautzberger JaEun Jemma Ku Christopher Lane Charles LaPierre Gez Lemon Aaron Leventhal Laurence Lewis biao liu Brian Liu Xu David MacDonald Sazzad Mahamud Mark McCarthy Erika Miguel Daniel Montalvo Sheila Moussavi James Nurthen Scott O'Hara Adam Page Michael Pennisi Roberto Perez Janina Sajka Trisha Salas Stefan Schnabel Harris Schneiderman Boaz Sender Cynthia Shelly Tzviya Siegman Avneesh Singh Neil Soiffer Francis Storr Melanie Sumner Alexander Surkov James Teh Seth Thompson Jan Williams Benjamin Young Valerie Young Helen Zhou 骅 杨 Joseph Scheuhammer
Description: Do we need an AAPI event for aria-errormessage to indicate that the error message is now visible or relevant, or vice versa has gone away (when, presumably, the user has filled the form control with valid information)?
Add notes (no markup allowed, URIs get automatically hyperlinked):
No related emails.
Isn't the presence—or absence—of aria-errormessage enough?
The question is: how does the AT know when the error message text is relevant? The spec currently says that aria-errormessage is used in conjunction with aria-invalid; hence, the signal that the error message is pertinent is when aria-invalid is set to true. Setting aria-invalid to true will cause an AAPI event for everyone but UIA [1]. That may be sufficient, although something needs to be done in the case of UIA. Also, the error message will be shown when it's relevant. That will also cause events in the AAPI [2]. That may also be sufficient. Then again, it might be very useful to have a specific "error-message-asserted" event that targets error messages only. Dunno. [1] http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#event-aria-invalid [2] http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_events_visibility
Latest from James Teh: "If you really do want errormessage to be treated as an entirely separate thing, then I have to change my position on this: we need a new relation and new events. If it's really such a new and separate thing, we don't have to worry about existing AT not getting the benefit." [1] [1] https://lists.w3.org/Archives/Public/public-aria/2016Feb/0419.html
WONTFIX There are already numerous events, tied to live regions, that are adequate (some would say are actually spam). Joseph withdraws the issue, also. Closing.