Identify Common Purpose - resolving issues

OK, we have 12 issues raised on 1.3.4 (Identify Common Purpose). We need to be able to resolve these quickly, and it will be very difficult. The brief summaries of the issues are below.

In general, the concerns are:

  1.  No implementations. We have an indication that one is coming, but I’m not sure if it is English-only or not.
  2.  Making the list – how it was determined, whether we add more, remove some, reference externally, or what
  3.  Security concerns/conflicts. Suggests moving to AAA due to lack of implementations and required support if 2.1 takes ISO path. Problem in Japan. (major) Proposes sentence structure change (minor) Presently there are no add-ons or AT supporting the SC, change to AAA (major) Concerned about the dilemma of a fixed list of purposes vs. an untestable (moving target) maintained list. (major) Suggests waiting for browsers/UA to possibly pick up data and then it will be time to ask developers to support it. (major) Suggests a reference to the HTML autofill list, or at least clarifying in understanding that the list will become out of date with the source. Thinks should be for HTML only also. (major) Concerned that the purposes need to be uniquely identifiable and referenceable. (seems solved) Wants more and better understanding content. Raises potential security risks. (major) “compose” / “new” question related to a specific metadata item in the list. similar to 635 (seems solved) comment that raises possible concerns and conflicts with security requirements for sites (major – solved?) List of purposes needs more terms (minor/major)



Andrew Kirkpatrick
Group Product Manager, Accessibility

Received on Wednesday, 10 January 2018 02:10:21 UTC