Re: Patterns and User Story Wording Structure Straw Poll

Prefer #2 as well, can live with 3.

On Thu, Feb 18, 2021 at 7:13 AM Kinney, Kris Anne <kakinney@ets.org> wrote:

> Prefer #2
>
>
>
> --
> Kris Anne Kinney, CPACC
>
> Accessibility Specialist
>
> 609-734-1466 <(609)%20734-1466>
>
>
>
> The only thing worse than being blind is having sight with no vision.  ~
> Helen Keller
>
>
>
> Have a request for an accessibility review?  Please submit an Accessibility
> Work Request
> <https://etsorg1.sharepoint.com/teams/rd/a11y/Lists/Accessiblity%20Work%20Requests/active.aspx> on
> SharePoint.
>
>
>
> *From: *Pascalides, Justine E <JPascalides@ETS.ORG>
> *Date: *Thursday, February 18, 2021 at 9:41 AM
> *To: *Rachael Bradley Montgomery <rachael@accessiblecommunity.org>, Lisa
> Seeman <lisa1seeman@gmail.com>
> *Cc: *public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
> *Subject: *RE: Patterns and User Story Wording Structure Straw Poll
>
> I also prefer #2.
>
>
>
> *From:* Rachael Bradley Montgomery <rachael@accessiblecommunity.org>
> *Sent:* Thursday, February 18, 2021 9:40 AM
> *To:* Lisa Seeman <lisa1seeman@gmail.com>
> *Cc:* public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
> *Subject:* Re: Patterns and User Story Wording Structure Straw Poll
>
>
>
> Hello,
>
>
>
> We didn't receive a lot of response on this and need to clear it up.
>
>
>
> For me I prefer #2 but can live with 3. I am concerned that #1 does
> violate screen reader best practices.
>
>
>
> Best regards,
>
>
>
> Rachael
>
>
>
> On Mon, Jan 11, 2021 at 7:57 AM Lisa Seeman <lisa1seeman@gmail.com> wrote:
>
> I find option 1. the clearest.
>
>
>
> Screen reader issues can be addressed using  aria-lable
>
> unfortunately the headings are often off the page view so they do not
> always give context
>
>
>
>
>
> On Fri, Jan 8, 2021 at 12:12 AM Rachael Bradley Montgomery <
> rachael@accessiblecommunity.org> wrote:
>
> Hello,
>
>
>
> An issue was raised that when reading the table of contents for Making
> Content Usable, the repetitive headings for patterns and user stories made
> reading more difficult than necessary.
>
>
>
> Today we decided that we should keep the structure of the headings in the
> table of contents and the document the same. Below are the options for ways
> we can present the headings for patterns and users stories. Please write
> back with which alternative you prefer or another alternative not listed
> here.
>
>
>
> 1 (current):  *User Story: Previous Steps *and *Pattern: Make Each Step
> Clear*
>
> 2: *Previous Steps (User Story)* and *Make Each Step Clear (Pattern)*
>
> 3: *Previous Steps - User Story* and *Make Each Step Clear - Pattern*
>
> 4. *Previous Steps* and *Make Each Step Clear*
>
>
>
> Thank you,
>
>
>
> Rachael
>
> --
>
> Rachael Montgomery, PhD
>
> Director, Accessible Community
>
> rachael@accessiblecommunity.org
>
>
>
> "I will paint this day with laughter;
>
> I will frame this night in song."
>
>  - Og Mandino
>
>
>
>
>
>
> --
>
> Rachael Montgomery, PhD
>
> Director, Accessible Community
>
> rachael@accessiblecommunity.org
>
>
>
> "I will paint this day with laughter;
>
> I will frame this night in song."
>
>  - Og Mandino
>
>
>
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
>
>
> Thank you for your compliance.
> ------------------------------
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
> Thank you for your compliance.
> ------------------------------
>