- From: Alan Chuter <achuter@technosite.es>
- Date: Tue, 28 Apr 2009 09:32:22 +0200
- To: WAI-EO <w3c-wai-eo-request@w3.org>, MWI BPWG Public <public-bpwg@w3.org>
Suggested edits received from Gregg Vanderheiden, posted here for the record. Marked up in HTML. These have been included in the next draft. Begin forwarded message: > *From: *Gregg Vanderheiden <gv@trace.wisc.edu <mailto:gv@trace.wisc.edu>> > *Date: *April 21, 2009 10:40:27 PM CDT > *To: *shawn@w3.org <mailto:shawn@w3.org> > *Cc: *WCAG Editors <team-wcag-editors@w3.org > <mailto:team-wcag-editors@w3.org>> > *Subject: **Relationship between.....* > > Hi Shawn, > Very interesting > > here are some suggested edits. > > didn’t get through but sending these on before they get lost. > > > > /Gregg/ > ----------------------- > Gregg Vanderheiden Ph.D. > Director Trace R&D Center > Professor Industrial & Systems Engineering > and Biomedical Engineering > University of Wisconsin-Madison > > > > Summary of work required to make content that meets WCAG 2.0 also > meet MWBP > > Compliance with WCAG 2.0 helps go some way towards achieving > compliance with some of the MWBP. This section provides a summary of > these BPs. There are two possible levels of effort required, labelled > for simplicity with the keywords /nothing/, /something/ and /everything/. > > Note that coverage may depend on WCAG compliance level achieved and so > a BP may appear in “something” and “nothing” lists (for example, > LINK_TARGET_ID). > > To summarise, if your content already complies with WCAG 2.0, then in > order to achieve compliance with the MWBP, you need to do the following: > > *Nothing*: If a provision is labelled "*Nothing" *then content that > complies with WCAG 2.0 already complies with the provision so and no > further effort is necessary. The following list includes all of the > provisions that are marked '*Nothing*' is provided for completeness.( > Links in this section point to the relevant provisions. Recommendation. > > * AUTO_REFRESH <http://www.w3.org/TR/mobile-bp/#AUTO_REFRESH>, > covered *for content that meets level AAA* by 3.2.5 Change on > Request > <http://www.w3.org/TR/WCAG20/#consistent-behavior-no-extreme-changes-context>. > * FONTS <http://www.w3.org/TR/mobile-bp/#FONTS>, covered at > level A by 1.3.1 Info and Relationships > <http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic>. > * LINK_TARGET_ID <http://www.w3.org/TR/mobile-bp/#LINK_TARGET_ID>, > covered at level AAA by 2.4.9 Link Purpose (Link Only) > <http://www.w3.org/TR/WCAG20/#navigation-mechanisms-link>. > * NON-TEXT_ALTERNATIVES > <http://www.w3.org/TR/mobile-bp/#NON-TEXT_ALTERNATIVES>, covered > at level A by success criterion 1.1.1 Non-text Content” > <http://www.w3.org/TR/WCAG20/#text-equiv-all>. > * STYLE_SHEETS_SUPPORT > <http://www.w3.org/TR/mobile-bp/#STYLE_SHEETS_SUPPORT>, covered > at level A by success criterion 1.3.1 Info and Relationships > <http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic>. > * STYLE_SHEETS_USE > <http://www.w3.org/TR/mobile-bp/#STYLE_SHEETS_USE>, covered at > level A by success criterion 1.3.1 Info and Relationships > <http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic>. > * TAB_ORDER <http://www.w3.org/TR/mobile-bp/#TAB_ORDER>, covered > at level A by 2.4.3 Focus Order > <http://www.w3.org/TR/WCAG20/#navigation-mechanisms-focus-order>. > * USE_OF_COLOR <http://www.w3.org/TR/mobile-bp/#USE_OF_COLOR>, > covered at level A by success criterion 1.4.1 Use of Color > <http://www.w3.org/TR/WCAG20/#visual-audio-contrast-without-color>. > > *Something*: If a provision is labelled "*Something" *then more effort > of some kind is necessary to comply with the provision. All of the > provisions marked "Something" are include in the list below. Each > item in the list is a link that will take What is required is > explained in the following next section of this report. For each there > is a list of the provisions that may provide some compliance or are in > some way related. There is no direct correspondence between one > provision and another. In some cases, it may be necessary to make an > extra effort or to consider a more diverse range of user needs. In > these cases, the word “possibly” is used. In other cases scope may be > different, giving partial compliance. In these cases the word > “partially” is used. BP links in this section point to the detail > section > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#addressing> below; > SC links in this section point to WCAG 2.0. > > * BACKGROUND_IMAGE_READABILITY > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_BACKGROUND_IMAGE_READABILITY>, > possibly covered at level AA by 1.4.3 Contrast (Minimum) > <http://www.w3.org/TR/WCAG20/#visual-audio-contrast-contrast> and > at level AAA 1.4.6 Contrast (Enhanced) > <http://www.w3.org/TR/WCAG20/#visual-audio-contrast7> > * COLOR_CONTRAST > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_COLOR_CONTRAST>, > partially covered at level AA by success criterion 1.4.3 > Contrast (Minimum) > <http://www.w3.org/TR/WCAG20/#visual-audio-contrast-contrast> and > at level AAA 1.4.6 Contrast (Enhanced) > <http://www.w3.org/TR/WCAG20/#visual-audio-contrast7> > * CONTROL_LABELLING > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_CONTROL_LABELLING>, > possibly covered at level A by 1.3.1 Info and Relationships > <http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic>, 3.3.2 > Labels or Instructions > <http://www.w3.org/TR/WCAG20/#minimize-error-cues> and 4.1.2 > Name, Role, Value <http://www.w3.org/TR/WCAG20/#ensure-compat-rsv>. > * CONTROL_POSITION > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_CONTROL_POSITION>, > possibly covered at level A by 1.3.1 Info and Relationships > <http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic>. > * GRAPHICS_FOR_SPACING > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_GRAPHICS_FOR_SPACING>, > possibly covered at level A by 1.3.1 Info and Relationships > <http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic>. > * LINK_TARGET_ID > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_LINK_TARGET_ID>, > partially covered at level A by 2.4.4 Link Purpose (In Context) > <http://www.w3.org/TR/WCAG20/#navigation-mechanisms-refs>. > * MEASURES > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_MEASURES>, > possibly covered at level AA by 1.4.4 Resize text > <http://www.w3.org/TR/WCAG20/#visual-audio-contrast-scale>. > * NAVIGATION > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_NAVIGATION>, > partially covered at level AA by 3.2.3 Consistent Navigation > <http://www.w3.org/TR/WCAG20/#consistent-behavior-consistent-locations> and > at level AAA 2.4.10 Section Headings > <http://www.w3.org/TR/WCAG20/#navigation-mechanisms-headings>. > * NON-TEXT_ALTERNATIVES > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_NON-TEXT_ALTERNATIVES>, > partially covered at level AAA by 1.2.7 Full Text Alternative > <http://www.w3.org/TR/WCAG20/#media-equiv-text-doc> (but covered > already at that level by 1.1.1 Non-text Content > <http://www.w3.org/TR/WCAG20/#text-equiv-all>). > * OBJECTS_OR_SCRIPT > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_OBJECTS_OR_SCRIPT>, > partially covered at level A by 2.1.1 Keyboard > <http://www.w3.org/TR/WCAG20/#keyboard-operation-keyboard-operable> and > at level AAA by 2.1.3 Keyboard (No Exception) > <http://www.w3.org/TR/WCAG20/#keyboard-operation-all-funcs>. > * PAGE_TITLE > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#PAGE_TITLE>, > possibly covered at level A by 2.4.2 Page Titled > <http://www.w3.org/TR/WCAG20/#navigation-mechanisms-title>. > * POP_UPS > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_POP_UPS>, > partially covered at level A by 3.2.1 On Focus > <http://www.w3.org/TR/WCAG20/#consistent-behavior-receive-focus> and 3.2.2 > On Input > <http://www.w3.org/TR/WCAG20/#consistent-behavior-unpredictable-change> and > possibly at level AAA by 3.2.5 Change on Request > <http://www.w3.org/TR/WCAG20/#consistent-behavior-no-extreme-changes-context>. > * REDIRECTION > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_REDIRECTION>, > covered at level A by 2.2.1 Timing Adjustable > <http://www.w3.org/TR/WCAG20/#time-limits-required-behaviors> and > at level AAA by 2.2.4 Interruptions > <http://www.w3.org/TR/WCAG20/#time-limits-postponed> and 3.2.5 > Change on Request > <http://www.w3.org/TR/WCAG20/#consistent-behavior-no-extreme-changes-context>. > * STRUCTURE > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_STRUCTURE>, > possibly covered at level A by success criterion 1.3.1 Info and > Relationships > <http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic> and > at level AA by 2.4.6 Headings and Labels > <http://www.w3.org/TR/WCAG20/#navigation-mechanisms-descriptive> and > at level AAA by 2.4.10 Section Headings > <http://www.w3.org/TR/WCAG20/#navigation-mechanisms-headings>. > * VALID_MARKUP > <http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20090218/wcag20-mwbp.html#mwbp10_VALID_MARKUP>, > possibly covered at level A by 4.1.1 Parsing > <http://www.w3.org/TR/WCAG20/#ensure-compat-parses>. > > *Everything*: For all other BPs, WCAG 2.0 does not ensure compliance > and it will be necessary to do the work involved. These BPs are not > related to any WCAG 2.0 success criteria. > > > > > >
Received on Tuesday, 28 April 2009 07:35:08 UTC