- From: Steven Hoober <steven@4ourth.com>
- Date: Sat, 24 Jan 2026 10:15:02 -0600
- To: "Beasley, Leonard H" <BeasleyL1@aetna.com>
- Cc: Kevin White <kevin@w3.org>, WCAG <w3c-wai-gl@w3.org>, Julie Rawe <jrawe@understood.org>, "Toles, John" <jtoles7@gatech.edu>, John Kirkwood <kirkwood@citymouse.com>, "jeremy.katherman@deque.com" <jeremy.katherman@deque.com>, "McGee, Kimberly" <kimberly.mcgee@sap.com>, "Hall, Carrie" <carrie.hall@sap.com>, Ashley Firth <ashley@mrfirthy.me>
- Message-ID: <CA+3j-4SGv4beinDp0fpDabpUj0AAAHMnqhO9m--ru601FYK+Sg@mail.gmail.com>
Strong support for *‘our readers are developers, not designers.’ As a designer I disagree very strongly and am struck by the bias revealed by the comment. * For the short time I've been on a few different W3G groups, I have seen much the same and it *seems* to be just a reflection of the industry standard of assuming "devs" do everything, but ignores that there are designers, writers, a11y experts, much less many types of engineers at many levels. Agree that our audience needs to be wider, or at least tweaked per document and this content-oriented one is going to be for Content Designers/Writers first, all other cadres as plausible. *Steven Hoober* *President – Design * *4ourth Mobile* 5600 Russell Avenue Mission, Kansas 66202 United States +1 816 210 0455 steven@4ourth.com <http://goog_843203800/> www.4ourth.com <http://4ourth.com> @ shoobe01 On Fri, Jan 23, 2026 at 3:42 PM Beasley, Leonard H <BeasleyL1@aetna..com> wrote: > Hey Kevin, > > Re: IRC cheat sheet - thank you. I linked to it from our subgroup doc so > that we can find it faster. > > Re: WCAG visit analytics > This came up as we talked about definitions. We were wondering if there > was any way to learn more about our users and if that information would > help us craft definitions and requirements to better meet their needs. > > For example, would content writers or designers understand some of the > definitions as written? Would they know that they build on top of HTML or > CSS definitions contained in another document? Are we being so anchored in > 2.x that we aren’t able to think of definitions that help everyone? > > Personally, I have been in meetings where someone will say ‘our readers > are developers, not designers.’ As a designer I disagree very strongly and > am struck by the bias revealed by the comment. > > We’re curious about what we know about our users, and it could help us. > > Thank you for your reply to our minutes email. > > > -- > > *Len Beasley* > > > 918 630 5419 > Colorado (MT) > > > *From: *Kevin White <kevin@w3.org> > *Date: *Thursday, January 22, 2026 at 1:01 AM > *To: *Beasley, Leonard H <BeasleyL1@aetna.com> > *Cc: *WCAG <w3c-wai-gl@w3.org>, Julie Rawe <jrawe@understood.org>, Toles, > John <jtoles7@gatech.edu>, John Kirkwood <kirkwood@citymouse.com>, > jeremy.katherman@deque.com <jeremy.katherman@deque.com>, McGee, Kimberly < > kimberly.mcgee@sap.com>, Hall, Carrie <carrie.hall@sap.com>, Ashley Firth > <ashley@mrfirthy.me>, Steven Hoober <steven@4ourth.com> > *Subject: *[EXTERNAL] Re: Text and Wording Meeting Minutes Jan 14, Week 3 > > ***** External Email - Use Caution ***** > > ------------------------------ > Hi Len, > > On 21 Jan 2026, at 23:20, Beasley, Leonard H <BeasleyL1@aetna.com> wrote: > > - > > Question: Is there an IRC cheat sheet for scribing? (Yes, we just > need to find it.) > > > You can find lots of information in the links under the Zakim commands > <https://docs.google.com/document/d/1WkYBc_9PowZRcxp1ld13jkA2pHd-vvmeBf9sZzUDjJQ/edit?tab=t.0#heading=h.3rdcrjn> heading > in the Subgroup handbook. > > If you have any questions, please do just ping me. > > > > - > > Question: Are there any stats we're able to view? page views, > search terms etc. to help our understanding who's currently consuming? > (We’ll have to ask our chairs or W3C staff contacts about this.) > > > Possibly. It depends on what content you are considering. > > Thanks > > Kevin > > > NOTICE TO RECIPIENT OF INFORMATION: > > This e-mail may contain confidential or privileged information. If you > think you have received this e-mail in error, please advise the sender by > reply e-mail and then delete this e-mail immediately. > > This e-mail may also contain protected health information (PHI) with > information about sensitive medical conditions, including, but not limited > to, treatment for substance use disorders, behavioral health, HIV/AIDS, or > pregnancy. This type of information may be protected by various federal > and/or state laws which prohibit any further disclosure without the express > written consent of the person to whom it pertains or as otherwise permitted > by law. Any unauthorized further disclosure may be considered a violation > of federal and/or state law. A general authorization for the release of > medical or other information may NOT be sufficient consent for release of > this type of information. > > Thank you, Aetna >
Received on Saturday, 24 January 2026 16:26:11 UTC