Re: Make it easy to find the most important thing

Thank you for the excellent feedback. It makes sense to call out content as well as controls though I think we will have a more difficult time getting that through based on previous comments. Lets start there and then reassess based on new feedback.

With regards to Abi’s comments, I had interpreted the intent of this SC to be that important content (vs any content) is visible above the fold.  I am not sure that the following conveys that.

> > “content following repeated navigational elements must be visible
> > without scrolling in the main modalities of the content.”
I do believe that the wording above  conveys the need to ensure users are aware of content’s existence. That is also important and may be more easily  accepted as an SC because it does not require a tester to distinguish between important and unimportant content.

Do we want to keep that distinction in the Sc text and use this concept for part of the techniques?

Thoughts on which direction to go?

Again thank you all for your help working through this.

Regards

Rachael



On May 22, 2019, 4:11 AM -0400, Steve Lee <stevelee@w3.org>, wrote:
> I'm +1 to Abi's comments
>
> In general, I think we we still have a bit of ambiguity in our
> documentation about content vs behaviour (ie controls, navigation etc).
>
> This is largely historical, I guess. The web started off as documents
> only and the only behaviours where forms and links. But now of course
> web apps are very common as well with all sorts of behaviours made
> available via buttons and custom controls.
>
> We should be careful to use language that includes both static content
> and behaviours unless we mean to target only one or the other.
>
> What do other groups do to cover this?
>
> Steve
>
> On 22/05/2019 06:57, James A. wrote:
> > Hi Rachael
> >
> > I wasn’t involved in 2.1 so not party to all the details that were
> > discussed at that time. I think your proposals a good basis but I am
> > concerned they only mention controls not content more widely.
> >
> > I’m wondering if we could use the concept of main content as a
> > substitute for “above the fold” particularly as we have to support all
> > screen sizes and zoomed in to 300%
> >
> > Based on 2.4.1 this could be something like
> >
> > “content following repeated navigational elements must be visible
> > without scrolling in the main modalities of the content.”
> >
> > Or
> >
> > “Content at the beginning of main region landmarks must be visible
> > without scrolling in the main modalities of the content.”
> >
> > (Although that 2nd one may have to be a technique)
> >
> > Best wishes
> >
> > Abi
> >
> >
> >
> > Sent from my iPhone
> >
> > On 21 May 2019, at 19:08, Rachael Bradley Montgomery
> > <rachael@accessiblecommunity.org
> > <mailto:rachael@accessiblecommunity.org>> wrote:
> >
> > > Hello,
> > >
> > > I am working on the 2.2 SC text for "Make it easy to find the most
> > > important thing"
> > >
> > > I went back through the 2.1 feedback on this SC and believe there are
> > > a few different paths to take in wording. I am unfortunately teaching
> > > this Thursday so won't be on the call but I would appreciate your
> > > opinions on the best approach.
> > >
> > > The 2.1 text read "Critical features and important information are
> > > above the fold and are accentuated in the main modality of the content."
> > >
> > > There was feedback that it is difficult to determine a critical
> > > feature is, where the fold is, and what accentuated means. Below are a
> > > few suggestions for alternate wording that use existing definitions
> > > and approaches to try to clarify or remove these points.
> > >
> > > 1. Essential controls are prominent and visible without scrolling in
> > > the main modalities of the content.
> > > 2. Essential controls are visible without scrolling in the main
> > > modalities of the content.
> > > 3. Essential controls are prominent and visible without scrolling in
> > > a 1280 x 1024 css pixel viewport.
> > >
> > >
> > > Thoughts?
> > >
> > > Thank you,
> > >
> > > Rachael
> > >
> > > --
> > > Rachael Montgomery, PhD
> > > Director, Accessible Community
> > > rachael@accessiblecommunity.org <mailto:rachael@accessiblecommunity.org>
> > >
> > >
>