W3C home > Mailing lists > Public > public-eo-plan@w3.org > January to March 2018

Fwd: Response Needed - "QuickRef" title update

From: Bakken, Brent <brent.bakken@pearson.com>
Date: Thu, 8 Mar 2018 16:10:41 -0600
Message-ID: <CAE6qf-Fk6B8HkC2fvyOzsGzVhS778L9wXDAutQ4tND2GHOyJ2Q@mail.gmail.com>
To: EO Planning <public-eo-plan@w3.org>
For the record




---------- Forwarded message ----------
From: Alastair Campbell <acampbell@nomensa.com>
Date: Thu, Mar 8, 2018 at 10:38 AM
Subject: Re: Response Needed - "QuickRef" title update
To: "Bakken, Brent" <brent.bakken@pearson.com>, AGWG Chairs <
group-ag-chairs@w3.org>
Cc: EOWG Chairs <team-eowg-chairs@w3.org>


HI Brent,



I’m the new co-chair, I checked in with Andrew and Josh and we’re happy
with the approach.



It doesn’t appear to impact the normative guidelines docs or anything in TR
space, and doesn’t appear controversial, so we’ll take an FYI approach with
the AG group.



Thanks for the heads up,



-Alastair





*From: *"Bakken, Brent"



Hi Josh and Andrew,



Recently EO planning team received an email reminding us of a confusion
issue that has been raised a few times in the past. The nickname "Quick
Reference," which is used by many when referring to the "How to Meet WCAG"
resource is not in the title or heading 1. Some are looking for the "Quick
Reference" and not realizing that they are on the correct page. Please see
proposal and links below for reference.



We would like confirmation from AGWG on approval of this proposal as soon
as possible so that we can update and/or close the issue.

Do you want to run this through CFC, Survey, or just an FYI. It is up to
you. EO has already surveyed for approval (affirmative results below).



*Please add to your tasks and circle back with us as soon as you can.*

Thanks,

Brent

-------------------



We all frequently talk about the "Quick Reference" or "QuickRef" but those
words have not been in the actual title and heading 1. We cannot change the
base title of "How to Meet WCAG 2". We propose adding (Quick Reference) to
the title and heading 1.

Current version: How To Meet WCAG 2.0 <https://urldefense.
proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_WCAG20_
quickref_&d=DwICaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=v-
L6X-ScaY5UKb-F-_zcuXdbPw2UYK_gaTG8R5d9h7U&m=0NtIJ9kYvDkOUmyCiwbUgw81Y58Fjo
NPKP52_BYsces&s=PmpfQwINrS8oNjltOJ-HzKywiv8eW0qtSxPTxDOFcE8&e=>

Proposed: How to Meet WCAG 2 (Quick Reference) <https://urldefense.
proofpoint.com/v2/url?u=https-3A__w3c.github.io_wai-2Dwcag-
2Dquickref_&d=DwICaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=v-
L6X-ScaY5UKb-F-_zcuXdbPw2UYK_gaTG8R5d9h7U&m=0NtIJ9kYvDkOUmyCiwbUgw81Y58Fjo
NPKP52_BYsces&s=aJybWBKxoijFdsM30ppidDix3FniWMJqLR7jb_eZWG8&e=>

GitHub Issue 151 for background and comments:  <https://urldefense.
proofpoint.com/v2/url?u=https-3A__github.com_w3c_wai-2Dwcag-
2Dquickref_issues_154&d=DwICaQ&c=0YLnzTkWOdJlub_y7qAx8Q&r=v-L6X-ScaY5UKb-F-_
zcuXdbPw2UYK_gaTG8R5d9h7U&m=0NtIJ9kYvDkOUmyCiwbUgw81Y58FjoNPKP52_BYsces&s=
ymN0403E9mlNJYiAAB_XJoz8lI79TaIu8uxdh-w3P_c&e=>

(EOWG survey results approval: <https://urldefense.
proofpoint.com/v2/url?u=https-3A__www.w3.org_2002_09_wbs_
35532_EO-2DWeekly-2D23-2DFeb-2D2018_results-23xq7&d=DwICaQ&
c=0YLnzTkWOdJlub_y7qAx8Q&r=v-L6X-ScaY5UKb-F-_zcuXdbPw2UYK_gaTG8R5d9h7U&m=
0NtIJ9kYvDkOUmyCiwbUgw81Y58FjoNPKP52_BYsces&s=FTnWjbB7jfUae0qgt1RfjEzny5kfhX
2cDAAafIjA46w&e=>)





*Brent A. Bakken*

Director, Accessibility Strategy & Education Services
Pearson

512 202 1087 <(512)%20202-1087>
brent.bakken@pearson.com

*Learn more at **pearson.com* <http://pearson.com>



[image: Pearson]
Received on Thursday, 8 March 2018 22:11:33 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 8 March 2018 22:11:34 UTC