adding items to functionality capabilities

[UsableNet-WCAG]

hi, reviewing the capabilities under functionality and cross referencing the last 5 projects we worked on, I found a number of capabilities that are needed for modern day website accessibility.

Need to add to "Client Side Interaction" these key capabilities:

• ensure keyboard access to interactive elements
• manage focus through interactive processes
• handle live regions - this helps use handle dynamic pages (like single page applications)

And add a new subset of

Custom components (these are starting t be used heavily for rapid feature deployment)

• correct semantic behavior
• apply or adjust aria elements when needed
• replace component if needed with accessible version

[lwolberg]

Discussed in the Telecon. Updated:

Jason to add the following to a branch, to suggest these additions:

add to "Client Side Interaction":

• ensure keyboard access to interactive elements - AOK
• manage focus through interactive processes - this refers to managing the focus order as an individual interacts with the page.
• handle dynamic pages (like single page applications) - focus on live regions on behalf of screen reader users

In Functionality, Create a new H2 for "Custom components". Under that, add

• correct semantic behavior - AOK
• apply or adjust ARIA elements when needed
• replace component when possible with an accessible version

add to "Management":

• use native semantic elements when possible, avoid custom components when you can