[TIME SENSITIVE] aria-errormessage may need additional normative language in the ARIA spec

Hey all.

I marked this thread as "TIME SENSITIVE" because I am hoping to reach
consensus at tomorrow's meeting regarding how to proceed. (It's already
in the agenda.)

I began implementing support for aria-errormessage in WebKitGtk, but was
unsure how user agents should handle aria-errormessage referencing a
valid, non-hidden element when that error message has not explicitly
been marked as pertinent by the author. As the subject indicates, I
believe that aria-errormessage may need additional normative language in
the ARIA spec. I have detailed those issues in github:
https://github.com/w3c/aria/issues/587, and included proposed language
which would satisfy my concerns and enable me to finish the
implementation I had started.

Addressing this issue to my satisfaction would require exiting and
re-entering CR, something we would need to do quickly if we have any
hope of being a REC by TPAC. But the need to exit and re-enter CR is
also present if we want to address the unintentionally
overly-restrictive language in aria-roledescription. Ditto if we want to
mark some potentially at-risk items as such. (Also on the agenda.)

See you all tomorrow, and in the meantime, thoughts on my proposed
changes to aria-errormessage are encouraged.

Thanks!
--joanie

Received on Wednesday, 14 June 2017 15:04:54 UTC