In Pega version 7.2.1 we have enabled the accessbility framework PegaWAI:07-10.
Currently, the progress bar has three steps. Any step that has not yet been complete or is not the current step, is inactive (visually) on screen.
When encountered using a screen reader(Jaws), the current step is announced as an active link and the others (yet to come) are read as text only e.g. reads 'link step 1 [name of screen]' then 'step two [name of screen] ' and 'step three [name of screen]’.
As this is the only method of conveying where the user is in the process, it would be confusing to a non-sighted user.
Therefore, the screen reader should read 'Current' (or similar) when announcing the step, you are on, and then 'Incomplete' along with the steps yet to be performed.
reads 'link step 1 of 3 - [name of screen] (current)' then 'step two of three - [name of screen] (incomplete)' and 'step three of three - [name of screen] (incomplete)'.
Thank you for this well crafted and clear post. You have a legitimate concern here. OOTB, the case stages have a tool tip which shows a redundant case stage name. You could try leveraging this extension point and make your own tooltip to meet your needs.
OOTB, the configuration looks like this.
You could modify the tooltip to achieve something like this. If this proof of concept works for you, you could in theory create a custom field value to concatenate the stage name with your own custom string, etc.
This is some good feedback and brings out some good concerns. Thanks for sharing this. Some points to consider.
A breadcrumb trail consists of a list of links to the parent pages of the current page in hierarchical order. Although we sometimes refer to tabbed screen flow as breadcrumbs, they are closer to being a wizard. Unfortunately, the ARIA authoring practices guide does not have any role taxonomy for a Wizard.
The Pega implementation also does not assign any semantic role to the "links" in the tabbed screen flow, other than the inherent "link"; and the 'tab' here is more in reference to an old UI look which, as seen in the image you posted, is no longer the UI! We attach an aria label to these links. But no other ARIA states and properties are set.
You may want to consider adding additional content in the screen flow step (assignment flow action) to identify the current step and remaining and previous step information.
Finally, the implementation of these links is somewhat dated (uses Rule-Obj-HTML type rules) and starts out in an available rule called "NestedTabbedNavigation7". It is possible for you to changes the "links" mechanism in a more suitable way to your specific needs (granted this requires considerable effort).