[Agenda] WAI Curricula Task Force Teleconference Meeting Tuesday November 24

Hello all:

 

Below some items we could go through in our meeting today.

---

Tuesday November 24 we are going to have another WAI Curricula Task Force 

teleconference.

 

Topic: WAI Curricula Task Force Weekly Meeting

Time: November 24, 2020 5:00 PM CET (Central Europe Time)

 

Participation Info:

https://www.w3.org/2017/08/01-eowg-info.html

 

IRC:

http://irc.w3.org?channels=#wai-curricula

 

Port 6665.

Channel #wai-curricula

 

Agenda:

 

We will be discussing work in progress for module 7, rich applications, 

https://deploy-preview-273--wai-curricula.netlify.app/curricula/developer-modules/rich-applications/

 

Agenda+ Coverage of Dom Management techniques for accessible rich applications

 

Currently we have a topic called "Document Object Management" about DOM management techniques related to accessibility, such as
showing or removing nodes based on what is currently visible on screen.

 

What other mechanisms (if any) apart from use of aria-hidden and DOM removal of nodes that are not relevant to the context of the
current application views should we include in this topic?

 

Agenda+ Standard versus non-standard keyboard shortcuts

 

In topic "Keyboard and Focus Management" we currently use the term "non-standard keyboard shortcuts" to refer to specific keyboard
shortcuts for rich applications such as web-based email clients. For example, moving back and forth through the list of emails is
achieved by pressing j or k, which is not a standard web keyboard shortcut. Is this concept clear enough? How could we make the
difference between expected keystrokes on the web such as the tab key or the arrow keys and specific keystrokes in a
per-application basis?

--

 

Daniel Montalvo

 

Accessibility Education and Training Specialist

W3C/WAI