Re: a suggestion for Personalization Semantics

> I would say that 1.3.1 already requires landmark regions in HTML
documents that have visually distinct parts of a page, but I understand
that others on the group would not hold that position.

As a robust Technique for meeting *some* of 1.3.1, the use of landmark
elements or aria-attributes is indeed recommended. However, since WCAG 2.0
was written before aria-regions or HTML5 landmark elements were
standardized (or supported by AT), we cannot retroactively say that they
are *REQUIRED*, nor can we fail content that does not use either form of
landmark determination.

   - Recommended? Yes
   - Encouraged? Beyond a doubt.
   - Required? No.

This Working Group has attempted to tackle this in the past, and the W3C
consensus position is that WCAG 2.0 does not mandate their use.

That said, the door remains open to introduce a new SC for WCAG 2.2 that
would close this gap, and that fact has been true since the onset of the
2.1 work. Not just a Failure Technique, an actual Success Criteria
requirement.

JF

On Fri, Jan 12, 2018 at 8:09 AM, David MacDonald <david100@sympatico.ca>
wrote:

> I would say that 1.3.1 already requires landmark regions in HTML documents
> that have visually distinct parts of a page, but I understand that others
> on the group would not hold that position.
>
> My reasoning is that the main region is represented visually and therefore
> should be programmatically identified. It is also accessibility supported
> and is reasonable to expect.
>
>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902 <(613)%20235-4902>
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd
>
> GitHub <https://github.com/DavidMacDonald>
>
> www.Can-Adapt.com <http://www.can-adapt.com/>
>
>
>
> *  Adapting the web to all users*
> *            Including those with disabilities*
>
> If you are not the intended recipient, please review our privacy policy
> <http://www.davidmacd.com/disclaimer.html>
>
> On Fri, Jan 12, 2018 at 7:57 AM, lisa.seeman <lisa.seeman@zoho.com> wrote:
>
>> he is asking for the regions to be in the  AA not AAA. As it is covered
>> by aria it seems easy to add them
>>
>> All the best
>>
>> Lisa Seeman
>>
>> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
>> <https://twitter.com/SeemanLisa>
>>
>>
>>
>>
>> ---- On Fri, 12 Jan 2018 13:39:25 +0200 *David
>> MacDonald<david100@sympatico.ca <david100@sympatico.ca>>* wrote ----
>>
>> Maybe I'm missing something but it appears to me what Martin is saying is
>> that TextHelp could leverage the <main> element or role="main" or perhaps
>> <article> element. I don't see anything in this email that indicates a need
>> for additional attributes...
>>
>> Cheers,
>> David MacDonald
>>
>>
>>
>> *Can**Adapt* *Solutions Inc.*
>>
>> Tel:  613.235.4902 <(613)%20235-4902>
>>
>> LinkedIn
>> <http://www.linkedin.com/in/davidmacdonald100>
>>
>> twitter.com/davidmacd
>>
>> GitHub <https://github.com/DavidMacDonald>
>>
>> http://www.can-adapt.com/
>>
>>
>>
>> *  Adapting the web to all users*
>> *            Including those with disabilities*
>>
>> If you are not the intended recipient, please review our privacy policy
>> <http://www.davidmacd.com/disclaimer.html>
>>
>> On Thu, Jan 11, 2018 at 4:17 AM, lisa.seeman <lisa.seeman@zoho.com>
>> wrote:
>>
>> Hi
>> This is some feedback from texthelp.
>> SHould I move it to an issue?
>>
>> All the best
>>
>> Lisa Seeman
>>
>> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
>> <https://twitter.com/SeemanLisa>
>>
>> ============ Forwarded message ============
>> From : Martin McKay<m.mckay@texthelp.com>
>> To : <shadi@w3.org>,"lisa.seeman"<lisa.seeman@zoho.com>
>> Date : Tue, 09 Jan 2018 16:27:58 +0200
>> Subject : a suggestion for Personalization Semantics
>> ============ Forwarded message ============
>>
>> Hi Shadi, Lisa,
>>
>> It was great to get a chance to discuss the proposal for Personalization
>> Semantics  in some detail today.
>> It may be an improvement to include "Main Content" as a UI element.
>>
>> Use case:
>> Imagine someone is in a Kindle Reader type application.
>> The entire UI is composed of
>>
>>    1. Next Page
>>    2. Previous Page
>>    3. Menu (to go to library etc)
>>    4. Main Content
>>
>> As a preference I may like my Main Content to have a certain font,
>> spacing etc. and may want to suppress the other UI.
>> If this was to be implemented as a WGAG 2 success criteria Texthelp would
>> implement support for the feature in Read & Write for Google (12 million
>> users)
>>
>> I am happy to hop on a skype call to discuss this for clarity if it helps.
>>
>> If you can indicate the likelihood of my proposed improvement, I can add
>> it as a project backlog item and move towards implementation.
>>
>> Best Wishes,
>> Martin
>> --
>> *Martin McKay*
>> CTO
>>
>> T: +44(0)28 9442 8105
>>
>> <https://www.facebook.com/Texthelpers>   <https://twitter.com/texthelp>
>> <https://www.linkedin.com/company/texthelp>
>> <https://plus.google.com/u/0/+Texthelp/posts>
>>
>> <http://www.texthelp.com/>
>>
>>
>>
>> Texthelp, Lucas Exchange, 1 Orchard Way
>> <https://maps.google.com/?q=1+Orchard+Way&entry=gmail&source=g>,
>> Greystone Road, Antrim, Northern Ireland, BT41 2RU
>>
>> --
>> Texthelp Ltd is a limited company registered in Belfast, N. Ireland with
>> registration number NI31186 having its registered office and principal
>> place of business at Lucas Exchange, 1 Orchard Way, Antrim, N. Ireland,
>> BT41 2RU
>> <https://maps.google.com/?q=1+Orchard+Way,+Antrim,+N.+Ireland,+BT41+2RU&entry=gmail&source=g>
>> .
>>
>>
>>
>>
>>
>>
>>
>>
>>
>


-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion