Re: CFC - Update SC text Purpose of Controls

-1 - I cannot live with this as presented today.

I have to agree with Steve, without specific definitions of which controls,
this SC language has no real scope - which was a significant reason for
splitting this out from the original "Support Personalization" proposed SC
in the first place - scoping the requirement to a fixed list of page
controls, as opposed to applying Personalization(-like semantics to all
major blocks of content on the page, which is the current AAA Contextual
Information proposed SC).

Additionally, because of that lack of scope, it leaves the intended
controls undefined, and leaves content authors without "the list" of
controls they need to be marking up: a recipe for disaster from my
perspective.

I'd like to propose yet another draft:

"In content implemented using markup languages, the purpose of <ins>
*specific*</ins> *user interface components* that serve a conventional
purpose can be programmatically determined."

...and then link to the final defined
​ *normative*​
list of controls
<https://drive.google.com/file/d/0B8dsTwtY5GvmMGplTUY4UmZzX3M/view?usp=sharing>
​.

JF​

On Tue, Nov 21, 2017 at 12:41 PM, Repsher, Stephen J <
stephen.j.repsher@boeing.com> wrote:

> 0?
>
> I’m fine with the language change, but until we resolve the conventional
> purposes and a finalized SC that links to or defines them somehow, I cannot
> give consensus one way or the other.  In other words, there’s no value in
> this change by itself until other parts of the document are changed.
>
>
>
> Steve
>
>
>
> *From:* Joshue O Connor [mailto:josh@interaccess.ie]
> *Sent:* Tuesday, November 21, 2017 12:57 PM
> *To:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* CFC - Update SC text Purpose of Controls
>
>
>
> Call For Consensus — ends Friday November 24th at 1:00 PM Boston time.
>
> The Working Group discussed an update to the Purpose of Controls SC on the
> call today [1].
>
> The current SC text is:
>
> "In content implemented using markup languages, the conventional name of
> conventional form fields, conventional buttons or controls, or conventional
> links can be programmatically determined."
>
>
> This is to be changed to:
>
> " In content implemented using markup languages, the purpose of user
> interface components that serve a conventional purpose can be
> programmatically determined."
>
> If you have concerns about this proposed consensus position that have not
> been discussed already and feel that those concerns result in you “not
> being able to live with” this decision, please let the group know before
> the CfC deadline.
>
> [1] https://www.w3.org/2017/11/21-ag-minutes.html
>
> --
> Joshue O Connor
> Director *| InterAccess.ie *
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion