W3C home > Mailing lists > Public > public-silver@w3.org > October 2019

Re: the inportents of simplification

From: Léonie Watson <lwatson@tetralogical.com>
Date: Wed, 30 Oct 2019 15:31:11 +0000
To: "Hall, Charles (DET-MRM)" <Charles.Hall@mrm-mccann.com>, "lucy@accessaces.com" <lucy@accessaces.com>, Silver Task Force <public-silver@w3.org>
Message-ID: <7f90ade2-e352-af63-bb7f-150926fd91cc@tetralogical.com>
On 30/10/2019 13:30, Hall, Charles (DET-MRM) wrote:
> The W3C Process 2020 (continuous development) is one potential option 
> for Silver where document conventions like this could be iterated on – I 
> believe after Recommendation status – through an open process. I don’t 
> believe we have solved for the governance and change management of 
> guidelines yet.

The W3C Process governs the way specifications are produced at the W3C, 
but not the way the documents themselves are marked up. That is handled 
by the different publication processors used at W3C or the people 
editing the specification.

In the case of the ARIA specification, I believe it should be 
technically possible to change the multiple "Note" h5 headings to be 
more context specific, but I'm not sure it would be a good idea to do 
so. It would make the headings longer and harder to read in many cases.

Although the ARIA specification is large and complex, it does implement 
multiple ways of getting to the bit you're interested in:

* The heading structure is robust throughout the document. For example, 
in the section where all the roles are defined, each role is indicated 
with an h4, and any notes relating to that role are an h5. This is all 
preceeded with the expected h1, h2, h3 hierarchy.

* The table of contents links through to different sections, and 
although not down to the level of individual roles, it does link to the 
start of the "5.4 Definition of roles" section.

The one change I think could be made, is taking the word "role" out of 
parenthesis in the h4 headings. At the moment the heading is "note 
(role)", which means searching for "Note role" doesn't work.

I've opened an issue on the ARIA repository to suggest this:

This is the best place to file issues with the ARIA specification, 
whatever they may be. It's where all the people working on and 
contributing to the ARIA spec are paying most attention, and are most 
likely to respond.

Hope this helps.

> Thanks,
> *Charles Hall* // Senior UX Architect
> (he//him)
> charles.hall@mrm-mccann.com <mailto:charles.hall@mrm-mccann.com>
> W +
> M +
> 360 W Maple, Birmingham MI 48009
> mrm-mccann.com <https://www.mrm-mccann.com/>
> MRM//McCann
> Cannes Network of the Year
> Effie’s Most Creatively Effective Global Network 2018, 2019
> IPG Agency Inclusion Vanguard – Agency of the Year 2019
> *From: *lucia greco <lucy@accessaces.com>
> *Reply-To: *"lucy@accessaces.com" <lucy@accessaces.com>
> *Date: *Tuesday, October 29, 2019 at 4:02 PM
> *To: *Silver Task Force <public-silver@w3.org>
> *Subject: *[EXTERNAL] the inportents of simplification
> *Resent-From: *Silver Task Force <public-silver@w3.org>
> *Resent-Date: *Tuesday, October 29, 2019 at 4:02 PM
> hello every one:
>   i just had a experience that i thought i should share here as an 
> example of how we need to make  what we produce much more effective and 
> simple.
>   i was sent a link to the aria 1.1 spec specifically the information on 
> the role of note. well i gave up trying to read that page after 10 
> minuts of reading overly   complex text that talked about translation 
> and normative information. then i thought lets look through the heddings 
> and  found 4 h4 called note and i stopped counting after 5 h5 called 
> note. and frankly i still don't have any idea what the  document said 
> about the  role of note this stuff is to hard to read and we need to 
> make it more  discoverable for every one.  what was the   authors 
> thinking when they made so many headers whith the same text and why does 
> a page need so much background that you can't find the meat of the 
> thing. here is the link i was sent for  reference..
>   sorry i have not been as active here as i should but i felt this 
> needed to be said here as its key to what i think our work had as its goal.
> lucy
> https://www.w3.org/TR/wai-aria-1.1/#note 
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www..w3.org_TR_wai-2Daria-2D1.1_-23note&d=DwMFaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=FbsK8fvOGBHiAasJukQr6i2dv-WpJzmR-w48cl75l3c&m=laICy-sfIok4caNIMmwtl5v03IF942-KgSybrC08Mxo&s=4ZBcoGA2yfFVRlMwmsy6A4eO6kUQGHFsEqEWoWbxC5Q&e=>
> lucia Greco
> http://accessaces.com 
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__accessaces.com&d=DwMFaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=FbsK8fvOGBHiAasJukQr6i2dv-WpJzmR-w48cl75l3c&m=laICy-sfIok4caNIMmwtl5v03IF942-KgSybrC08Mxo&s=d7fWoYKePkogyzntR3XOUCQXmQhdUMD88TU4TQmKI1g&e=> 
> follow me on twitter @accessaces
> This message contains information which may be confidential and 
> privileged. Unless you are the intended recipient (or authorized to 
> receive this message for the intended recipient), you may not use, copy, 
> disseminate or disclose to anyone the message or any information 
> contained in the message. If you have received the message in error, 
> please advise the sender by reply e-mail, and delete the message. Thank 
> you very much.

Director @TetraLogical
Received on Wednesday, 30 October 2019 15:31:18 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:46 UTC