- From: George Kerscher <kerscher@montana.com>
- Date: Fri, 3 Apr 2015 09:02:27 -0600
- To: "'Charles LaPierre'" <charlesl@benetech.org>, <public-dpub-accessibility@w3.org>
- Message-ID: <000f01d06e1f$34e04960$9ea0dc20$@montana.com>
Hi,I am trying: dial in 617/761-6200 pin 2742 and it says that it is restricted at this time. /George From: Charles LaPierre [mailto:charlesl@benetech.org] Sent: Thursday, April 02, 2015 8:08 AM To: public-dpub-accessibility@w3.org Subject: A11Y DPUB Meeting Tomorrow Hello everyone, for those who can make it our new meeting time is now Fridays at 8AM PDT, 11AM EDT, and (15:00 UTC). Tomorrow we will continue with going over the WCAG General Techniques and looking at all those that we have marked as questionable and decide if they are or are not relevant to Digital Publishing. FYI here is a record of the ones which we still have questions. We have already gone over the General Techniques that we marked as Not applicable to Digital Publishing. G178: Providing controls on the Web page that allow users to incrementally change the size of all text on the page up to 200 percent G181: Encoding user data as hidden or encrypted data in a re-authorization page G189: Providing a control near the beginning of the Web page that changes the link text G177: Providing suggested correction text G179: Ensuring that there is no loss of content or functionality when the text resizes and text containers do not change their width G133: Providing a checkbox on the first page of a multipart form that allows users to ask for longer session time limit or no session time limit G139: Creating a mechanism that allows users to jump to errors G143: Providing a text alternative that describes the purpose of the CAPTCHA G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality G155: Providing a checkbox in addition to a submit button G164: Providing a stated time within which an online request (or transaction) may be amended or canceled by the user after making the request If we finish those we can move onto WCAG A11Y DPUB HTML Techniques Here are the questionable items with these techniques H35: Providing text alternatives on applet elements ? Brijesh ? H84: Using a button with a select element to perform an action ? MiaL The functionality should be supported where necessary in interactive documents, but the technique itself may be too HTML-specific. H85: Using OPTGROUP to group OPTION elements inside a SELECT ? MiaL See above comment for H84 H89: Using the title attribute to provide context-sensitive help ? MiaL Not sure here, even in HTML, there are better-supported ways of doing this. Is this necessary/sufficient for DPUBs? H93: Ensuring that id attributes are unique on a Web page ? MiaL May be too HTMLL-specific H86: Providing text alternatives for ASCII art, emoticons, and leetspeak ?y MiaL Acknowledgment should be made for cases where emoticons or leet are being used as part of the text, when it is important that the user know which symbols are being used. H91: Using HTML form controls and links ?y MiaL DPUB-supported form control-types and links. Thanks. _______________________________ Charles LaPierre charlesl@benetech.org
Received on Friday, 3 April 2015 15:03:00 UTC