-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editorial changes for clarity and removing tool names #2587
Conversation
Edits intended to amend the current document so it lays out the goals and challenges without yet providing specific techniques AbstractThe abstract reflects a technical focus. Since we want a non-technical focus for this document, how about—
We could add that we will be sharing techniques and best practices—
1.1 Overview
The sentence is less discouraging without "try to" 1.2 The limits of fixed layout accessibility
2nd paragraph, first sentence. Should we make the epub issue the focus of the sentence?
Since we’re no longer putting code examples here, we should change the 3rd paragraph. And we want reading systems to up their game, too.
2.1 The page position problemMake it clear in the heading that we are addressing reading order
state the accessibility ideal
We don't want to lead keyboard users randomly around the page/screen, but what if there is a quirky order in which the author/illustrator intended the text to be read? This and the following sections are really helpful implementation information. Shall we move this to the future techniques and code examples document? |
Github allow me to comment only on changed sections, so here are my comments for unchanged section:
|
@gregoriopellegrino @sueneu I made some changes to the document, let me know what you think. |
For me: a big step forward! Some small things:
|
A few minor notes:
|
Also, you can link right to the level AA definition now that 2.2 is a recommendation: https://www.w3.org/TR/WCAG2/#cc1_AA (Alas, the url isn't working unless you strip the "2", which is not the url you'd want, but I've opened an issue about this in w3c/wcag#3515) |
As discussed in the last minute, I've made some editorial changes to the language in the document to clarify it's purpose. I've also removed any mentions of specific software/production tools.
Feel free to use this PR to make comments on the document.