diff --git a/aria-practices.html b/aria-practices.html index 9cc668cee9..89744d19b4 100644 --- a/aria-practices.html +++ b/aria-practices.html @@ -577,16 +577,16 @@

Feed

The primary difference between a feed and other ARIA patterns that support loading data as users scroll, e.g., a grid, is that a feed is a structure, not a widget. This means assistive - technologies with a reading mode, such as screen readers will default to reading mode when + technologies with a reading mode, such as screen readers, will default to reading mode when interacting with feed content, making the feed pattern most useful for blocks of unstructured information that may contain links or other interactive elements.

- For example, a product page on a shopping site may have a related products section that - displays five products at a time and, as the user scrolls, loads more product suggestions into the DOM. - While a static design might include a next button for loading five more products, a dynamic implementation + For example, a product page on a shopping site has a related products section that + displays five product suggestions at a time. As the user scrolls, more suggestions are requested and loaded into the DOM. + While a static design might include a next button for loading five more product suggestions, a dynamic implementation that automatically loads data as needed simplifies the user - experience and reduces the inertia associated with viewing more than 5 suggestions. + experience and reduces the inertia of viewing more than the first five suggestions.

Unfortunately, when web pages load content dynamically based on scroll events, it @@ -654,8 +654,8 @@

Keyboard Interaction

Options for supporting nested feed navigation include: