Edit comment LC-2682 for Accessibility Guidelines Working Group

Comment LC-2682: Comment Shortname:; Commenter: Duff Johnson <djohnson@commonlook.com>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Comment:
SC 4.1.2 - The Guidance (and the SC itself) doesn't (appear to) account for cases where a given Role isn't exposed through a user interface component. An example would be pre filled forms in which no controls are present but the page contents nonetheless render as a form with pre-filled (or blank, as the case may be) fields. In PDF this is accomplished via the PrintField attribute applied to page content.; Related issues: (space separated ids); WG Notes: Previous proposed resolution: it is not clear what your question is -- or what your suggested edit would be. Thank you for the information on how this case is handled in PDF. We suggest that you submit a technique on this to the WCAG working group for inclusion with their PDF techniques.; Proposed Resolution: The situation described appears to the Task Force to contain UI components in the non-web software world. Static text *is* a UI component (typically with role "static text"); certainly editable text fields - even if pre-filled-in - are UI components. They should have roles. Assuming pre-filled means that the field is pre-populated AND not changeable, the state of the field would be read-only.; (Please make sure the resolution is adapted for public consumption)