Consider semantics for accessible route

[rachaelbradley]

As web applications get more complex, guaranteeing every route through is fully accessible can be difficult. Occassionally the accessibility needs of one group may even conflit with the needs of another group and providing alternative routes may be the best alternative. In building design we have the concept of marking an accessible route. Is this something you have been considered within the web space? If not, would you discuss the possibility of a marker for an accessible route and indications of what functional needs are best supported within that route?

There are down sides to implementing an approach like this but I think it is worth discussing even if the end decision is not to pursue it.

[johnfoliot]

Personalization TF discussed. We are working on the following: https://w3c.github.io/personalization-semantics/tools/index.html#stepindicator-usage-example-explanation

We likely want more discussion

[lseeman]

we may want to design module 2 and module 3 together to meet this need
Module 2 - functional requirements and support for alterntve path
Module 3 -make it path not step

[rachaelbradley]

This suggestion may be broader than steps. A component may be the most accessible way through for several paths or it may be at a different step based on the task the user is trying to perform.

[becka11y]

Thanks for your comment. We agree that providing one or more accessible routes through a process is important. We discussed this briefly and agreed that it was beyond the scope of our content module. We plan to examine this more thoroughly in a future personalization module.