Changelog for document “Relationship Between
Mobile Web Best Practices 1.0 and Web Content Accessibility Guidelines”
Latest Public Working Draft at http://www.w3.org/TR/mwbp-wcag/.
This changelog refers to the Editor's Draft. The latest Editor's Draft is at http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/latest.
Changes suggested by Shawn in http://lists.w3.org/Archives/Public/w3c-wai-eo/2008JulSep/0002.html
- Change everything, nothing and something wording in each page to “These XXs are not related to XXXX” as appropriate.
- Remove date from WCAG 2.0 in References section.
- Change heading “Differences Between WCAG and MWBP” to “Priorities and Levels” and wording.
- Change wording of “How to Use This Document” as suggested.
- Change wording of “Incomplete draft” disclaimer on each subpage.
- In overview page, change “Appendix B: Glossary” to “Special Terms.”
- Remove wai-editors list as address for comments. Move comments material to seperate paragraph.
- In overview page, Status section, a paragraph briefly saying what changed since the last version, probably linking to the changelog, and specifically saying what we seek comments on in this version
- Take “1.0” off of “MWMP 1.0” in all instances.
- In WCAG 2.0 to MWBP 1.0, work through the not-evluated-yet list and either move BPs to everything list or (in several cases) create detail sections for them.
- Short handles in how-to-use table and list. Use consistent handles in navigation bar.
- Include note to explain why there's a table and a list of pages on Overview page.
- Remove table of contents and introduction section heading from “together” page (as it now only has one section).
- Put back “Relationship” in the Overview title.
- Add a subheading “Overview”
- Change “Contents” link in naigation to “Skip to content” and make consistent across pages. [recorded in http://www.w3.org/2008/06/27-eo-minutes.html#action03]
- Resolved duplicated listing of AUTO_REFRESH in WCAG 2.0 to MWBP by putting both in nothing section [recorded in http://www.w3.org/2008/06/27-eo-minutes.html#action05]
- Include neither/both row to "how to use this document" table. [recorded in http://www.w3.org/2008/06/27-eo-minutes.html#action02]
- Put back “Everything” section in the “MWBP to WCAG 2.0” document (was moved to the end of the document but I've now restored it to where it was). [recorded in http://www.w3.org/2008/06/27-eo-minutes.html#action06
- Change “Why No WCAG to MWBP Mapping Table?” to “Why No Mapping Table?”
- Include a disclaimer about links not being consistent. [recorded in http://www.w3.org/2008/06/27-eo-minutes.html#action04]
By Yeliz and Alan. See WAI Education & Outreach WG minutes for 2008/06/20.
- In navigation at top of page, add link to table of contents.
- Remove footer and copyright from individual pages other than Overview. Replace with horizontal rule.
- No added benefit: Remove this item from the glossary as it doesn't apply to these document now it's split from the how-helps document.
- Abstract: Changed the abstract to make sure that we used the term “overlap” and added a link to the WAI introduction page as suggested in the EO meeting [recorded in http://www.w3.org/2008/06/20-eo-minutes.html#action09 and http://www.w3.org/2008/06/20-eo-minutes.html#action02].
- Status of This Document: Shortened this a lot and highlighted the public-bpwg-comments@w3.org for comments. If there is a public EO list, I think it would be good to add that as well.
- Audience: Deleted this section. It was discussed in the EO meeting that that section could be added to the introduction document.
- TOC: Added HR before and after the TOC.
- How to Use This document: Shortened this section a lot and deleted the table as it was discussed in the meeting to try alternative organisations so when we agree on a structure, we can add it here. “Consider if the
table is necessary once the together document is taken out of the
bulleted list” [recorded in http://www.w3.org/2008/06/20-eo-minutes.html#action13]. Added restructured table.
- Scope: I have shortened the scope and changed it to address the comments from the EO meeting.
- Managing Overlapping Requirements: Changed this from "The problem of multiple overlapping requirements" to address the comments from the EO meeting. Also shortened this section. Action was “change the idea
from the problem of overlapping requirements to
managing/implementing overlapping requirements” [recorded in
http://www.w3.org/2008/06/20-eo-minutes.html#action14]
- Differences between WCAG and MWBP: changed this from "proirities" and also added information about WCAG 2.0 SC levels.
- Appendix A: References: changed this from "Related Documents of Interest" and organised the list of resources as references.
- Appendix B: Glossary: changed this from "Special meanings of terms used in this document"
- Appendix C: Acknowledgements: changed this from "acknowledgements".
- Change to multi-page document (was “suite”) [recorded in http://www.w3.org/2008/06/20-eo-minutes.html#action08]
- for the status,
add instructions/information for reviewers [recorded in http://www.w3.org/2008/06/20-eo-minutes.html#action03]
- in "scope" section, make it clear that this document is not replacing the other two main documents, it is a supporting document [recorded in http://www.w3.org/2008/06/20-eo-minutes.html#action07 and http://www.w3.org/2008/06/20-eo-minutes.html#action06]
- Move business case type information to EO introduction document and
here leave only the technical information [recorded in http://www.w3.org/2008/06/20-eo-minutes.html#action15]
- move up the link
to the introductory page, cut down the audience section from here
[recorded in http://www.w3.org/2008/06/20-eo-minutes.html#action04]
- Rewrite WCAG 2.0 & MWBP 1.0 together document to suggest looking at WCAG 2.0 first and then the "from WCAG 2.0 to MWBP 1.0" document[recorded in http://www.w3.org/2008/06/20-eo-minutes.html#action12]
Version of 19/06/2008
Actions postponed but not forgotten:
First version after splitting off the how-it-helps material into seperate document.
- [MWBP-WCAG10] Added box styling to priority lists, modifying CSS file.
- [MWBP-WCAG10] Under PAGE_SIZE_USABLE and PAGE_TITLE, removed emphasis on the keyword “aspect”.
- [MWBP-WCAG20] Global replace “How does it especially help users with disabilities” with “How does it enhance accessibility to users with disabilities”
- [MWBP-WCAG20] Under IMAGE_MAPS remove benefits and SC compliance, and add at top “It is not the intent of the BP to discourage the use of image maps.”
- [MWBP-WCAG20] Put explanation of “no added benefit” in glossary.
- [MWBP-WCAG20] Under FONTS, Change text to “Many users do not see fonts-related styling. For example, blind users, those who turn off stylesheets, or use text mode browsers. If information is conveyed by fonts, these users may have difficulty understanding the meaning of content”
- [MWBP-WCAG20] Move the tip “Avoid nesting a control inside a label element as this is not supported in an accessible way by most user agents” from CONTROL_POSITION to CONTROL_LABELLING.
- [All] Move repeating “Back to Best Practices list” link outside visual box.
- [MWBP-WCAG20], [WCAG20-MWBP] To all ocurrences of keywords “possibly” and “partially”, add link to definition.
- Move definitions of nothing, something, everything, to “Special Meanings of Terms Used in this Document”
- [MWBP-WCAG20] Under THEMATIC_CONSISTENCY, mark for deletion the text about alternative versions, as it is based on misunderstanding.
- [MWBP-WCAG20] Under TABLES_LAYOUT, drop mention of browsers with no table support,
- [MWBP-WCAG20] Delete from TABLES_ALTERNATIVES the idea that it might reduce accessibility for screen reader users, on suggestion from MWBP WG.
- [MWBP-WCAG20] include suggestions for accessibility benefits of URIS and VALID_MARKUP (refer to email of 28 Feb 2008 and email of 22 Feb 2008).
- [Overview] Include definition of the terms possibly and partially.
- [MWBP-WCAG20] and [WCAG20-MWBP], where there is a section heading “How does it especially help users with disabilities?” and “Does it give me WCAG 2.0 compliance?” (and vice-versa), change these to be bolded text at the start of the paragraph, closer to the structure of the sections on the BPs and SCs that follow.
- [MWBP-WCAG20] and others, change word order in “How does it help especially users with disabilities” to “” to “especially help”
- [MWBP-WCAG20], Put link to a definition of innate reading level. DONE. The term doesn't appear in the new draft of WCAG, so have used just “reading level” instead which is easier to understand. “WCAG success criterion 3.1.5 Reading Level is related but it concerns a different aspect of language comprehension. WCAG is concerned with a user's reading ability, while this BP is concerned with...”
- [MWBP-WCAG20], under IMAGE_MAPS, Clarify that the SCs do not apply.
- [MWBP-WCAG20], under NON-TEXT_ALTERNATIVES, in the longdesc tip, change “do rely on it.” to “do not rely on it.” (insert “not”).
- [MWBP-WCAG20], under OBJECTS_OR_SCRIPT in the “How does it help...” section, clarify that it is users with disabilities that may not use the technology and assistive technology that may not support it, rather than the general user and general user agent.
- [MWBP-WCAG20], under PAGE_TITLE, add tip about using front-loading.
First update after progressing to First Public Working draft.
- [MWBP-WCAG20], new links from “Does it give me compliance” paragraph back to lists of efforts (for example, “Refer to 3.2.5 Change on Request, coverage at level A.”).
- [MWBP-WCAG20], include WCAG compliance content of POP_UPS.
- [MWBP-WCAG20], include WCAG compliance content of SCROLLING.
- [MWBP-WCAG20], in “Aiming for Level A” and AA remove SCs that don't apply to that level.
This version became the 22 January 2008 Public Working Draft http://www.w3.org/TR/2008/ED-mwbp-wcag-20080122/
- Prepare document for transition to first public working draft, numerous minor changes.
- Add Zip and GZip archives, and links in overview header.
- Add patent policy for document owned by two working groups.
Version prior to transition to first public working draft.
- Remove version numbering
- Change to Working Draft in main heading, and stylesheet.
- Rewrite, simplify Abstract
- Include in all pages a disclaimer about gaps in the document.
- Remove “Suite of Documents” sections and put explanation in Introduction
- Rewrite “How to Use” section
- Add “Incomplete draft” explanation to document status section.
- Add paragraph to introduce separate WAI Shared Experiences document, in “The Problem of Multiple Overlapping Requirements” section and under Related Documents.
- Add comment to WCAG 1.0 to MWBP page, to explain why so many check points are in the no overlap list.
- Restructure document into multiple pages. Many changes not logged in this version.
- Update references to WCAG 2.0 to match new 11 December 2007 last call draft.
- Move section “Achieving usability for All” to within section on “How Barriers Experienced by Web Users with Disabilities Parallel those in the Mobile Context” and change title to “Testing with Users and Devices”.
- Add content and explanatory comment to “WCAG and Mobile Web Best Practices Together”, trying to work out what it might look like.
- Remove section “How People with Disabilities Use Mobile Devices for Web Access” as it has no content and would better be addressed elsewhere.
- Add cross-reference table to facilitate navigation between three recommendations, based on abstract concepts “Cross-reference”.
- Add cross-reference links from different sections to “Summary of Experience of Content Features by Users” section.
- Add Tip to [STRUCTURE] to cover semantic markup not explicitly mentioned in BP.
- Insert explanatory paragraph at start of “Mobile Web Best Practices and Accessibility” and “WCAG Compliance and the Mobile Web” sections.
- Change title of section from “How WCAG Compliance can Benefit All Mobile Web Users” to “WCAG Compliance and the Mobile Web”
- Change title of section from “How Mobile Web Best Practices can Benefit Users with Disabilities” to “Mobile Web Best Practices and Accessibility” to better reflect what it's really about.
- Split drilldown lists of WCAG 2.0 and 1.0 success criteria to give list of those that can be ignored, similar to that used for MWBP section. Some example entries included, others to be left until work progresses.
- Create new section “Extending from WCAG 2.0 to MWBP 1.0”.
- Create new section “Extending from WCAG 1.0 to MWBP 1.0”.
- Create new section “Extending from MWBP to WCAG 2.0”. Delete now redundant paragraph “To summarise, for WCAG 1.0, compliance with MWBP ensures that content already complies with checkpoints...”
- Create new section “Extending from MWBP to WCAG 1.0”. Delete now redundant paragraph “To summarise, for WCAG 1.0, compliance with MWBP ensures that content already complies with checkpoints...”
- Update BACKGROUND_IMAGE_READABILITY and COLOR_CONTRAST. Add reference to WCAG 2.0 contrast ratio, under WCAG 2.0 part and 1.0 part in COLOR_CONTRAST and link to it from BACKGROUND_IMAGE_READABILITY.
- Update SCROLLING with input from Miguel García
- Change text of first paragraph of introduction to make it less negative. Smooth the mention of special consideration of needs of users with disabilities.
- Move abstract to beginning of document, including text suggested by Charles in email of 29 November 2007.
- Move last paragraph of “Related Documents of Interest” (about WCAG 1.0 and 2.0) to Scope section. Update it to reflect new emphasis on WCAG 2.0.
- Add WAI Resources page link to “Related Documents of Interest” section. Also WAI Business Case link.
- “Relationship to other W3C Recommendations” changed to “Related Documents of Interest”
- Remove Terminology section. This was intended to clarify the difference between “checkpoint”, “success criterion”, “best practice” and the version-independent WCAG “provision”, but this is now clearer as the WCAG 1.0 and 2.0 sections are now more separate and are redundant (no coverage of both together in the same paragraph).
- Move “Longevity and Versioning” section to “Status of this Document” section and update to cover recent widening of scope to WCAG 2.0.
- In [PROVIDE_DEFAULTS], modify text of “How does it help especially users with disabilities?” to “While this BP is primarily concerned with the limitations of the input mechanism of the mobile device (for example, a small numeric keypad), it also helps users who have difficulty using their chosen input device.” Remove duplicated “This BP does not correspond to...” Refer to messages to MWI BPWG list for November 2007.
- In [AUTO_REFRESH] correct the assertion “it ensures that refresh is initiated only by user request.”
- Try using two paragraphs, “Does it give me WCAG 2.0 compliance?” and “Does it give me WCAG 1.0 compliance?” rather than a global “Does it give me WCAG compliance?” with both together.
- Add “Does it give me WCAG 2.0 compliance?” to [STRUCTURE]. Update STRUCTURE to cover WCAG 2.0 SC 1.3.1 Info and Relationships and 2.4.9 Section Headings. Add WCAG 1.0 mention of 6.1, “Organize documents so they may be read without style sheets”
- Remove version number from “Web Content Accessibility Guidelines 1.0” in top level heading.
- Swap sections “How Barriers Experienced by Web Users with Disabilities Parallel those in the Mobile Context” and “How People with Disabilities Use Mobile Devices for Web Access” to reflect importance. Update table of contents accordingly.
- Add placeholders for all WCAG 2.0 SCs AND WCAG 1.0 CPs, and drill-down lists of WCAG 2.0 SCs AND WCAG 1.0 CPs.
- Add title and class to links to best practices in the BP document, of form “Link to [BEST_PRACTICE] in Mobile Web Best Practices document”. Likewise for WCAG 2.0 SCs AND WCAG 1.0 CPs.
- Best Practices with no added accessibility benefit and no corresponding WCAG provision (those for which there's nothing to say) moved to a list at the beggining of the section. This creates a list of these BPs which are links to the MWBP document. This makes the following section more compact and allows the reader to see at a glance which and how many BPs are and are not related to accessibility.
- In the section on BPs, remove the text “Refer to [BEST_PRACTICE] to understand the Best Practice described in this section” and make the name of the BP a link in the section heading preceding it. This makes the text much more compact and the reader immediately starts with the “How does it help especially users with disabilities?:” making the meaning clearer. Also for WCAG 2.0 success criteria in corresponding section.
- Update contributing groups information in “Status of this Document” section to “This document was developed by the Mobile Web Best Practices Working Group and the Education & Outreach Working Group (EOWG) of the Web Accessibility Initiative (WAI).” Remove “Preliminary draft” paragraph. Add paragraph and link, “A record of updates and modifications to this document is available.”
- From mapping document provided by Henny, in message “WCAG 1.0, Mobile Web and Internationalisation Best Practices cross over” of 6 Nov 2007. Edits as described in Alan's reply of 14 Nov 2007.
- In section 5. “How WCAG Compliance can Benefit All Mobile Web Users,” under “How Does it Help Users in the Mobile Context?” remove references to WCAG version. Under “Does it give me MWBP 1.0 compliance?” remove references to WCAG version and change color contrast example to WCAG 2.0. Separate WCAG CP into separate sections, for 1.0 and 2.0. Include example WCAG SCs. Change font color to blue to distinguish level 4 headings from other bold text.
- 14 November 2007. Updating section “Does it give me
WCAG compliance?” to include WCAG 2.0. Update best practices mappings
to include WCAG 2.0, no changes to WCAG 1.0 explanations, only add 2.0 at
end.