Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

comment from Martin McKay from text help #720

Closed
lseeman opened this issue Jan 12, 2018 · 2 comments
Closed

comment from Martin McKay from text help #720

lseeman opened this issue Jan 12, 2018 · 2 comments

Comments

@lseeman
Copy link
Contributor

lseeman commented Jan 12, 2018

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
Next Page
Previous Page
Menu (to go to library etc)
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

Texthelp, Lucas Exchange, 1 Orchard Way, Greystone Road, Antrim, Northern Ireland, BT41 2RU

@awkawk
Copy link
Member

awkawk commented Jan 12, 2018

Thanks you for your comment. The deadline for comments has passed, but the Working Group will make efforts to consider your comment and any suggestions for improvements.

@awkawk
Copy link
Member

awkawk commented Jan 24, 2018

(Official WG Response)
Thank you for the comment. At this point, there is a strong likelihood that 1.3.4 will be in the WCAG 2.1 recommendation, but focused only on purposes for input elements.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants