Re: [webauthn] cognitive-accessibility consideration

thx @wseltzer, so the definition of "[formally addressed](https://www.w3.org/2017/Process-20170301/#formal-address)" appears to cover our nominal working process where we have at least examined all open issues (i.e., "triaged" them), and assigned them to a milestone (CR, PR, REC).  

So, it would seem to me that we _can_ assign the  [subtype:accessibility-cons] issues to, say, the [PR  #milestone](https://github.com/w3c/webauthn/issues?q=is%3Aopen+is%3Aissue+milestone%3APR) such that we have time to give said issues proper attention, and enter transition-to-CR earlier, yes?

@JohnRochfordUMMS: [you said](https://github.com/w3c/webauthn/issues/733#issuecomment-358310145) "once we start working together".  From our nominal perspective, your having submitted this issue _does_ mean "we are working together".  If the present state does not meet your definition of "working together", might you please elaborate what your conception of "working together" entails? thanks.



-- 
GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/733#issuecomment-358717410 using your GitHub account

Received on Thursday, 18 January 2018 17:19:22 UTC