W3C home > Mailing lists > Public > public-silver@w3.org > March 2020

Suggestion: Use "Structure" rather than "Heading" for the Silver Guideline name

From: Newton, Brooks (TR Product) <Brooks.Newton@thomsonreuters.com>
Date: Tue, 24 Mar 2020 21:34:41 +0000
To: "jspellman@spellmanconsulting.com" <jspellman@spellmanconsulting.com>
CC: "public-silver@w3.org" <public-silver@w3.org>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <DM6PR03MB38993E3ACF092CBD88C32BA084F10@DM6PR03MB3899.namprd03.prod.outlook.com>
Hello Jeanne,

I've got a suggestion: Use "Structure" rather than "Heading" for the Silver Guideline name.
Thank you for presenting today on the call and for your ongoing work with the Silver Task Force. As you demonstrated the "Headings" Guideline example earlier on the call, an idea popped into my head. From my understanding of Silver, it sounds like:

  *   Silver Guidelines are intended to be normative (general and technology-neutral).
  *   Silver Methods used to test the Guidelines are intended to be informative (technology-specific).
I know a lot of folks are hoping that Silver will apply to a broad range of technologies, including content other than HTML-driven web pages.  For this reason, I think it would be a good idea to use technology-neutral language for the Silver Guidelines.
"Headings" is a term that's pretty closely associated with web pages and other types of digital documents. Instead of using "Headings" as a Guideline name, I wonder if the term "Structure" is more inclusive?  Based on your presentation, I think of the Silver Guidelines as:

  *   Naming general principles
  *   Supporting accessible user experiences
  *   Identifying user needs for people with disabilities
  *   Applying to a wide range of web-related contexts
So, for the proposed Guideline "Structure," Silver could have Methods such as "Headings" to help test whether the user need for structure is met through HTML-driven content.  The Guideline "Structure" would also encompass technology-specific testing Methods for other content types.  Methods for VR, for example, could help to test whether or not the user's need for structure is met by the content, markup and styling/presentation opportunities that are available through that technology.
Brooks

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Brooks Newton
Sr. Accessibility Specialist

Thomson Reuters
the answer company
This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain required legal entity disclosures can be accessed on our website: https://www.thomsonreuters.com/en/resources/disclosures.html
Received on Tuesday, 24 March 2020 21:54:55 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 24 March 2020 21:54:56 UTC