W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2018

RE: Clarification of "functionality"

From: Jonathan Avila <jon.avila@levelaccess.com>
Date: Fri, 13 Apr 2018 17:52:22 +0000
To: WCAG <w3c-wai-gl@w3.org>
Message-ID: <BN6PR03MB251307E69AF981DDD3368EECF1B30@BN6PR03MB2513.namprd03.prod.outlook.com>
It’s my general understanding the when you are looking at functionality you are determining whether there is equivalence via an alternative approach.   From what I understand the determination of functionality isn’t so much about the same steps but the outcomes (with 1 exception).  The exception and why the term “processes” may have been put in the definition is in some situations the actions are required to complete an activity and in that case all of the actions needed to perform the activity have to be available in a series.

If there isn’t a necessary set of steps needed for an activity then the location and mechanisms of the functional can be different.  For example, on a mobile site the menu items are hidden under a hamburger menu but are still available.


Jonathan Avila
Chief Accessibility Officer
Level Access
703.637.8957 office

Visit us online:
Website<http://www.levelaccess.com/> | Twitter<https://twitter.com/LevelAccessA11y> | Facebook<https://www.facebook.com/LevelAccessA11y/> | LinkedIn<https://www.linkedin.com/company/level-access> | Blog<http://www.levelaccess.com/blog/>

Looking to boost your accessibility knowledge? Check out our free webinars!<https://www.levelaccess.com/compliance-resources/webinars/>

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

From: Greg Lowney <gcl-0039@access-research.org>
Sent: Friday, April 13, 2018 2:33 PM
To: WCAG <w3c-wai-gl@w3.org>
Subject: Clarification of "functionality"

I'd like clarification on the meaning of "functionality" as used in WCAG. The two questions are, when the user interacts with a form:

  1.  does moving keyboard focus to a control count as functionality?
  2.  does changing the state of a check box or radio button count as functionality?

As background, the Glossary includes:

processes<https://www.w3.org/TR/WCAG21/#dfn-processes> and outcomes achievable through user action

series of user actions where each action is required in order to complete an activity

Received on Friday, 13 April 2018 17:53:02 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:26 UTC