diff --git a/packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-testing.md b/packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-testing.md index 19e2054ae3..5186129be1 100644 --- a/packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-testing.md +++ b/packages/documentation-site/patternfly-docs/content/developer-resources/accessibility-testing.md @@ -104,7 +104,7 @@ These are some of the main areas we check for on the PatternFly team to ensure t Landmark regions should have labels when there is more than one type of landmark, and they are not the same (such as navigation, main, form, etc.). Section element shouldn’t be used unless it has a label.} id="general-criteria-8f" /> - Tables and table content is clearly described. WebAIM has additional guidance on this.} id="general-criteria-8g" /> + Tables and table content is clearly described. WebAIM has additional guidance on creating accessible tables.} id="general-criteria-8g" /> Aria provides descriptive details to screen reader users, without reiterating or overriding the text that is already there. If there is visible text then there doesn’t need to be an aria-label. } description={It’s important to understand that ARIA can only affect the semantics of an element; not the behavior. For example, while you can hide an element from screen readers with className="ws-code">aria-hidden=”true”, that does not change the focus behavior for that element.} id="general-criteria-8h" />