- From: Sarah Horton <sarah.horton@gmail.com>
- Date: Sat, 24 Oct 2020 20:09:01 +0100
- To: Rachael Montgomery <rachael@accessiblecommunity.org>, Charles Hall <hallmediamobile@gmail.com>
- Cc: WCAG <w3c-wai-gl@w3.org>, Silver TF <public-silver@w3.org>
- Message-Id: <2043846E-D2E1-4AB2-A285-A4390BA06C42@gmail.com>
I agree with Charles about the term “user testing.” “User research” would be a better descriptor of studies and evaluations that involve people. Best, Sarah > On Oct 24, 2020, at 5:49 PM, Rachael Montgomery <rachael@accessiblecommunity.org> wrote: > > Charles, > > Can you provide more details and suggested corrections for your first point? > > Regarding user testing, the taskforce changed the term from usability testing to user testing to indicate a wide range of tests can be used including heuristic tests, formal usability testing, etc. > > I need to look further into the other points. > > Rachael > On Oct 24, 2020, 11:50 AM -0400, Charles Hall <hallmediamobile@gmail.com>, wrote: >> +1 >> >> I consent that there are no items that I am not ‘able to live with’. >> However, there are many that I would prefer to see edited. >> Apologies for missing deadlines from previous surveys, but here are a brief few: >> >> Use of certain disability language and named disabilities in the Abstract. >> Use of the term “fallback” to describe methods that are intended to be enhancements or forward looking. >> Use of the term “user testing” to describe usability testing. (We don’t test users. We test things through the participation of users) >> Some sections are understandably still blank, but some that are not have omissions, like E.1 references WCAG 2.0 and 2.2, but not 2.1. >> A select few instances of describing Functional Categories and Functional Needs, which I will address separately. >> >> Thanks, >> >> Charles Hall >> >> Senior Accessibility Designer >> Invited Expert, W3C AGWG & Silver TF >> Chair, W3C IDIW CG >> Member, Ferndale Accessibility & Inclusion Advisory Commission >> >>> On Oct 23, 2020, at 1:38 PM, Rachael Bradley Montgomery <rachael@accessiblecommunity.org <mailto:rachael@accessiblecommunity.org>> wrote: >>> >>> Call For Consensus — ends Friday October 30th at 2:00 pm Boston time. >>> >>> The Working Group and Silver Taskforce have discussed publishing W3C Accessibility Guidelines (WCAG) 3.0 as a First Public Working Draft (FPWD). >>> >>> The document is at: https://w3c.github.io/silver/guidelines/ <https://w3c.github.io/silver/guidelines/> >>> >>> Call minutes: >>> 1 September AGWG & Silver Meeting Minutes <https://www.w3.org/2020/09/01-ag-minutes.html> >>> 15 September AGWG & Silver Meeting Minutes <https://www.w3.org/2020/09/15-ag-minutes.html> >>> 6 October AGWG & Silver Meeting Minutes <https://www.w3.org/2020/10/06-ag-minutes.html> >>> 20 October AGWG & Silver Meeting Minutes <https://www.w3.org/2020/10/20-ag-minutes.html#item03> >>> Changes are viewable through the diffs at https://github.com/w3c/silver/commits/master/guidelines/index.html <https://github.com/w3c/silver/commits/master/guidelines/index.html> >>> >>> If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline. >>> >>> Kind regards, >>> >>> Rachael >>> >>> -- >>> Rachael Montgomery, PhD >>> Director, Accessible Community >>> rachael@accessiblecommunity.org <mailto:rachael@accessiblecommunity.org> >>> >>> "I will paint this day with laughter; >>> I will frame this night in song." >>> - Og Mandino >>> >>
Received on Saturday, 24 October 2020 19:09:21 UTC