Edit comment LC-2962 for Accessibility Guidelines Working Group

Next: LC-2938

Comment LC-2962: Comment Shortname:; Commenter: Ted Drake <ted_drake@intuit.com>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
If the placeholder text is required to meet 4.5:1 contrast ratio, should the compliance be required by developers (modify with CSS) or should the burden rest with browser manufacturers?; Related issues: (space separated ids); WG Notes: I think Michaels response captured most of the issue reflected in the WG feedback from our meeting on 23rd Sept 2104, so I've added his suggested text to the response. https://www.w3.org/2002/09/wbs/35422/20140923/results; Resolution: Browser vendors do have some responsibility for how they render author generated content by default. UAAG helps to indicate to user agent vendors to them how to achieve this. The most relevant UAAG Guidelines and success criteria are likely to come under Guideline 1.8 (See 1.8.8 Customize Viewport Highlighting for example). [1] [2] However, it is ultimately the responsibility of the author claiming WCAG conformance to ensure that the success criteria have been met. When user agents conform to UAAG 2.0, many of the success criteria, such as this one, are met automatically and the author does not need to take specific action. When user agents do not meet this automatically, authors must take specific action in the content. This varies according to the accessibility support of the user agents expected to be used by the audience. [1] http://www.w3.org/TR/UAAG20/ [2] http://www.w3.org/TR/UAAG20/#sc_188; (Please make sure the resolution is adapted for public consumption)