– DRAFT –
WCAG2ICT sub-group meeting on closed functionality

<maryjom> https://docs.google.com/spreadsheets/d/109GqdIBvvL1WRBryJOis7kS6pRGyeIYKpl63QuTIPnI/edit?usp=sharing

Go over spreadsheet on closed functionality analysis of WCAG SC

<maryjom> https://docs.google.com/spreadsheets/d/109GqdIBvvL1WRBryJOis7kS6pRGyeIYKpl63QuTIPnI/edit?usp=sharing

Generic comments that apply across many or all SC

Greg went through and tagged programmatically determinable SC

Closed products are closed to everything. Assistive technology cannot be installed on closed functionality products. That's the distinction we want to use as the EN is.

If AT is offered than the product is not closed

<maryjom> Poll: Should we have a note or text that says it is out of scope for our TF to come up with alternate requirements to cover different disabilities

<Sam> +1

<PhilDay> +1

+1

<maryjom> +1

1.1.1 Non-text Content

Slightly adjust "requires text or a text alternative" to add note on "programmatically determinable"

<maryjom> Modify existing guidance to: requires text or a text alternative in a programmatically determinable form

<PhilDay> +1

<Sam> +1

<maryjom> +1

+1

1.2.1 Audio-only and Video-only (Prerecorded)

If you have audio only, equivalent information should be provided. Nothing to add.

1.2.2 Captions (Prerecorded)

All audio SC stand as they are

1.2.3 Audio Description or Media Alternative (Prerecorded)

Transcript alone does not meet this, audio description needs to be synchronized. Leave as is.

1.2.4 Captions (Live)

Not a problem

1.2.5 Audio Description (Prerecorded)

1.3.1 Info and Relationships

All about programatic information

All fine with current

1.3.2 Meaningful Sequence

Statement maybe needed to say systems that cannot PD a meaningful sequence should be baked in

<PhilDay> For systems that do not support programmatically determinable such as closed systems, a correct reading sequence should be output

<PhilDay> For systems that do not support programmatically determinable , a correct reading sequence should be output

Work on wording

1.3.3 Sensory Characteristics

1.3.4 Orientation (New in WCAG 2.1) (24 May - stop)

<PhilDay> Content that is only used on hardware with a fixed display orientation OR that has no sensor to detect or change the orientation is covered under the essential exception and not required to provide support for orientation changes.

<PhilDay> (Copying from the main SC note)

<maryjom> Poll: Copy the statement regarding fixed display into the closed functionality section.

<PhilDay> +1

+1

<maryjom> +1

<Sam> =1

<Sam> +1

1.3.5 Identify Input Purpose (New in WCAG 2.1)

Autocomplete not relevant to most closed systems. Closed functionality is not going to remember your information.

Could comment on input field labels, additional labels may be helpful. But autocompletion could not be allowed.

Come pack to wording.

back*

1.4.1 Use of Color

Not a problem

1.4.2 Audio Control

Stopping here for next week