docs(cdk/stepper): change misleading documentation

The "Accessibility' section of the stepper docs was talking about the stepper having built-in accessibility treatment, even though it doesn't have any, because we don't have control over the component's markup.

These changes reword the section to make it more accurate.

Fixes #23044.

Author: crisbeto

src/cdk/stepper/stepper.md

@@ -57,11 +57,12 @@ resetting it will call `reset` on the underlying form control which clears the v
 - <kbd>SHIFT</kbd>+<kbd>TAB</kbd>: Focuses the previous tabbable element
 
 ### Accessibility
-The CDK stepper is treated as a tabbed view for accessibility purposes, so it is given
-`role="tablist"` by default. The header of step that can be clicked to select the step
-is given `role="tab"`, and the content that can be expanded upon selection is given
-`role="tabpanel"`. `aria-selected` attribute of step header and `aria-expanded` attribute of
-step content is automatically set based on step selection change.
-
-The stepper and each step should be given a meaningful label via `aria-label` or `aria-labelledby`.
-
+Apart from the built-in keyboard support, the stepper doesn't come with any accessibility
+treatment. When implementing your own component, it is recommended that the stepper is treated as
+a tabbed view for accessibility purposes by giving it a `role="tablist"`. The header of step that
+can be clicked to select the step should be given `role="tab"`, and the content that can be expanded
+upon selection should be given `role="tabpanel"`. Furthermore, the step header should have an
+`aria-selected` attribute that reflects its selected state and the associated content element should
+have `aria-expanded`.
+
+You can refer to the [Angular Material stepper](https://github.com/angular/components/tree/master/src/material/stepper) as an example of an accessible implementation.