- From: Bruce Bailey <Bailey@Access-Board.gov>
- Date: Wed, 17 Apr 2019 12:53:40 +0000
- To: Michael Gower <michael.gower@ca.ibm.com>
- CC: WCAG <w3c-wai-gl@w3.org>
Replies in-line... > Bruce, I reviewed for A and AA, and had a few requests/questions. Thanks! > Can you please add a comment to the document explaining why On Input is listed "no" for Invisible while On Focus is "yes". Done. I characterized On Input as not invisible because it frequently requires adding an explicit submit button (which otherwise might not have been in the original design). > Given 4.1.2 exists for custom components as per the SC's note, I do not think it is reasonable to use the rationale that standard HTML components already meet this SC to mark it "easy". It is theoretically easy to add aria, but can involve effort. So I'm not sure whether or not it should be marked easy, but I'm not comfortable with the reason given. Okay. I changed to not easy, and expanded the note. > Can you please add a note explaining why Contrast (minimum) is marked as not essential while Non-text Contrast is marked essential? Done. I also added notes to 1.4.11 and 1.4.12 > I suspect it is to do with a user's ability to transform text through an AT, but it would be good to note that. Yes, that was my thinking. > I would say that Status Messages needs some adjusting. I would say it is easy and also invisible. The text already exists in the UI; the SC merely requires it be programmatically flagged to AT, so it does not alter the UI at all (and therefore invisible). The fix is easy to implement - just add a role or aria-live attribute. Thanks for that input, I agree, and I changed it in the table. > Thanks for the work! Thank you for your review!
Received on Wednesday, 17 April 2019 12:54:06 UTC